Updated Spring Security Update in 1.1.10 (markdown)
parent
e68fb7d1d5
commit
924c64c6d7
|
@ -1,6 +1,4 @@
|
|||
## Why update?
|
||||
|
||||
While we try to avoid major library changes in patch releases, one of our upstream libraries, Spring Security OAuth, has pushed an important release that depends directly on newer versions of Spring and Spring Security, two other major underlying libraries. The Spring version dependency is now a new major version, `4.0`, which we have decided is too much of a jump for a patch release. We have masked out this dependency for now and will instead wait for the `1.2` development branch of MITREid Connect to switch to (see #657). Some testing has been done on running our libraries against Spring 4.0 and while success has been reported, we do not want to force all of our developers to move to a new major revision. The Spring Security release is more minor, from `3.1.4` to `3.2.3`, and it should cause only minor headaches for existing developers on the 1.1 series of releases. As such, we have decided to **update to Spring Security ``3.2.3``** effective in MITREid Connect release `1.1.10`.
|
||||
We have decided to **update to Spring Security ``3.2.3``** effective in MITREid Connect release `1.2.0`.
|
||||
|
||||
The core project has been updated (see #656) but if you're building a custom server or client there are some things you'll need to do to make things work again.
|
||||
|
||||
|
|
Loading…
Reference in New Issue