compared with
Current by Thor Henning Hetland
on Oct 31, 2020 21:56.

Key
This line was removed.
This word was removed. This word was added.
This line was added.

Changes (2)

View Page History
|| Version || Main changes || Comment(s) ||
| 2.0-alpha-16 | High-Availability/cluster configuration (SSOLoginWebApp and SecurityTokenService) | see documentation ([Whydah AWS ELB and Apache HA config]) \\ ([Whydah hazelcast STS configuration]) |
| 2.0-alpha-15 | consistent trailing slash on all URI paths in property files |Clients: Must update properties files locally. |
| 2.0-alpha-14 | Refactoring: Consistent naming of terms in tokens and UAWA naming cleanup | [ApplicationToken diff|https://wiki.cantara.no/pages/diffpages.action?pageId=38437471&originalId=38963284] \\ [UserToken diff|https://wiki.cantara.no/pages/diffpages.action?pageId=37388753&originalId=38963281] |
| 2.0-alpha-13 | DEFCON security awareness skeleton implemented | [DEFCON concept background|http://2014.javazone.no/presentation.html?id=b7ab616e] |
| 2.0-alpha-12 | SecurityTokenService internal structure refactoring, hazelcast in STS\\upgraded apacheds to 2.0m16 | [Embedded config|https://github.com/altran/Whydah-SecurityTokenService/blob/master/src/main/resources/hazelcast.xml] |
| 2.0-alpha-11 | Refactoring: snake_case in public API to minimize misunderstandings | [API diff|https://wiki.altrancloud.com/pages/diffpages.action?pageId=33915690&originalId=38963189] |
| 2.0-alpha-10 | internal naming convension refactoring | |
| 2.0-alpha-9 | refactoring: SecurityTokenService , from /token to /user in public API | |
| 2.0-alpha-8 | Application ID and secret implementation | |
| 2.0-alpha-4 | NetIQ redirect verification filter | [Property example|https://github.com/altran/Whydah-SSOLoginWebApp/blob/master/src/main/resources/ssologinwebapp.PROD.properties] |
| 2.0-alpha-3 | ticket => userticket refactoring | |
| 2.0-alpha-2 | New UserAdminWebApp application | |
* Latest stable release: *Whydah 2.5*

A bug fix release follows a stable release, when necessary. Bug fix releases add a sequence number to the product release number. Thus, the first bug fix release for Whydah *2.0* will be version *2.0.1*, then *2.0.2*, as necessary. A bug fix release replaces the previous stable release.

Bug fix releases are follow-ons to stable releases. Bug fix versions automatically start at stability *"rc"*, reflecting the fact that only localized bug fixes are expected to be included in such a release. Once all desired bug fixes are in place, a stability vote (to "stable") is followed by a release vote.


h3. Releases

* [Whydah 2.6 - Release Log] (Oct 2020)
* [Whydah 2.5 - Release Log] (August 2018)
* [Whydah 2.4 - Release Log] (December 2017)
* [Whydah 2.3 - Release Log] (September 2017
* [Whydah 2.2 - Release Log] (April 2017)
* [Whydah 2.1 - Release Log] (December 2015)
* [Whydah 2.0 - Release Log] (October 2014)

-----
{section}
{column}

h3. Preview Versions

* [Whydah 2.* - Release log]


* *alpha* versions are not stable; the represent functionality in flux; classes and methods may be renamed or otherwise refactored between releases.
* *beta* versions occur once main functionality is complete; they exist to fix bugs in both old and new functionality, and fill any gaps in functionality.
* *rc* versions are "release candidates"; the functionality should be solid; the point of a release candidate is to get wide exposure to the new codebase to ensure that the final release is free of bugs.

{column}
{column}

h3. Planned releases

* [Whydah 2.7 - Release Log] (November 2020+)
* [Whydah 3.0 - Encrypted tokens and high security applications]
* [Whydah 4.0 - DEFCON and handling installations under attack]

{column}
{section}