OPENAM-9142 Email service schema is not updated properly after upgrade
boot.json AME-12359 checkstyle
AME-11323 apply feedback from Neil and Peter upgrade keystore location, support multiple hosts for config store
AME-11876 - Add schema upgrade helper for the dashboard service
OPENAM-8510 Introduce minimum value configurable for SAML2 cache cleanup interval
OPENAM-9328 Ensure version properties are updated correctly
OPENAM-9149 Update i18nKeys in OIDC auth module service
OPENAM-9150 Remove device print service during upgrade
OPENAM-7577 pushing new self service out into its own service
Upgrade step
AME-9113 disable new audit during upgrade
AME-8505 Removal of legacy sts code
AME-8466 upgrade step to bring existing self service inline with new config
AME-7053 CR-7126, AME-7055 CR-7180, AME-7054 CR-7199 move Device Id (Match) scripts to scripting service and introduce global default scripts
AME-6725 CR-6909, AME-6759 CR-6910, AME-6879 CR-7004 move scripted auth modules to new scripting service
AME-5153 CR-5377 Make changes to various upgrade steps and helpers to merge schema changes between 11.0.0 and 12.0.0
OPENAM-4784 CR-5114 Added RS256 to the "ID Token Signing Algorithms supported" list on the OAuth2 Provider page and the implementation for RSA signing.
AME-5050 CR-4943 Hide deprecated Global Policy Config
AME-4197, CR-4221 - Added upgrade ability for new services and upgrade for new REST API version
CR-1164 - OPENAM-1978 Loggin Level available options should be ordered in descending order not alphabetical
Integrating AME-1809 / AME-2156 branch This merge also includes changes for: * short reports were always generated when clicking on an actionlink, even though the report isn't actually displayed. * Implementation of OPENAM-1630 SAML2 metadata signatures are now compliant with the specification. Within this change two new realm level option has been introduced: metadataSigningKey metadataSigningKeyPass These will tell OpenAM which private key to use for signing the SAML2 metadata. In case the SAML entity is remote, OpenAM will try to maintain the original XML signature (if present), otherwise it will be signed with the configured key. * Fixing minor bug with configurator in case the system is already upgraded. The problem was that the request for upgrade.htm resulted in a redirect which has been automatically followed, so the final response code was 200, and that confused the configurator. * Fix for OPENAM-2710 * Fix for OPENAM-2064 Dashboard service has been extracted to a separate LDIF file and the schema is now available for all supported data store types.
Fix for AME-202 - review: CR-802