13 Aug, 2013
6 commits
-
git-svn-id: https://svn.forgerock.org/openam/trunk@6244 0f4defcf-c51a-4c67-9f44-6fb5eba73c5d
-
git-svn-id: https://svn.forgerock.org/openam/trunk@6243 0f4defcf-c51a-4c67-9f44-6fb5eba73c5d
-
git-svn-id: https://svn.forgerock.org/openam/trunk@6237 0f4defcf-c51a-4c67-9f44-6fb5eba73c5d
-
git-svn-id: https://svn.forgerock.org/openam/trunk@6236 0f4defcf-c51a-4c67-9f44-6fb5eba73c5d
-
git-svn-id: https://svn.forgerock.org/openam/trunk@6235 0f4defcf-c51a-4c67-9f44-6fb5eba73c5d
-
…le in the last executed auth module git-svn-id: https://svn.forgerock.org/openam/trunk@6217 0f4defcf-c51a-4c67-9f44-6fb5eba73c5d
12 Aug, 2013
3 commits
-
git-svn-id: https://svn.forgerock.org/openam/trunk@6216 0f4defcf-c51a-4c67-9f44-6fb5eba73c5d
-
… added during evaluation git-svn-id: https://svn.forgerock.org/openam/trunk@6213 0f4defcf-c51a-4c67-9f44-6fb5eba73c5d
-
git-svn-id: https://svn.forgerock.org/openam/trunk@6212 0f4defcf-c51a-4c67-9f44-6fb5eba73c5d
10 Aug, 2013
1 commit
-
git-svn-id: https://svn.forgerock.org/openam/trunk@6205 0f4defcf-c51a-4c67-9f44-6fb5eba73c5d
09 Aug, 2013
3 commits
-
git-svn-id: https://svn.forgerock.org/openam/trunk@6201 0f4defcf-c51a-4c67-9f44-6fb5eba73c5d
-
git-svn-id: https://svn.forgerock.org/openam/trunk@6195 0f4defcf-c51a-4c67-9f44-6fb5eba73c5d
-
git-svn-id: https://svn.forgerock.org/openam/trunk@6190 0f4defcf-c51a-4c67-9f44-6fb5eba73c5d
08 Aug, 2013
8 commits
-
* Refactored LDAP module to use DJ SDK failover mechanism * Fixed initialization problems with AD * Implemented HBCF git-svn-id: https://svn.forgerock.org/openam/trunk@6188 0f4defcf-c51a-4c67-9f44-6fb5eba73c5d
-
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. git-svn-id: https://svn.forgerock.org/openam/trunk@6187 0f4defcf-c51a-4c67-9f44-6fb5eba73c5d
-
…ion' is not documented; CR-2120 git-svn-id: https://svn.forgerock.org/openam/trunk@6183 0f4defcf-c51a-4c67-9f44-6fb5eba73c5d
-
git-svn-id: https://svn.forgerock.org/openam/trunk@6179 0f4defcf-c51a-4c67-9f44-6fb5eba73c5d
-
git-svn-id: https://svn.forgerock.org/openam/trunk@6177 0f4defcf-c51a-4c67-9f44-6fb5eba73c5d
-
By throwing a ServletException in Servlet#init we prevent the continuation of the init process and essentually the application deployment will fail as well. git-svn-id: https://svn.forgerock.org/openam/trunk@6173 0f4defcf-c51a-4c67-9f44-6fb5eba73c5d
-
FailureID wasn't set when showing error=true templates for a given error state. git-svn-id: https://svn.forgerock.org/openam/trunk@6172 0f4defcf-c51a-4c67-9f44-6fb5eba73c5d
-
Adding the brand new client parameter to authenticate, so remote clients can send the IP address of the user for the sake of audit logs. git-svn-id: https://svn.forgerock.org/openam/trunk@6171 0f4defcf-c51a-4c67-9f44-6fb5eba73c5d
07 Aug, 2013
4 commits
-
git-svn-id: https://svn.forgerock.org/openam/trunk@6165 0f4defcf-c51a-4c67-9f44-6fb5eba73c5d
-
git-svn-id: https://svn.forgerock.org/openam/trunk@6161 0f4defcf-c51a-4c67-9f44-6fb5eba73c5d
-
git-svn-id: https://svn.forgerock.org/openam/trunk@6155 0f4defcf-c51a-4c67-9f44-6fb5eba73c5d
-
git-svn-id: https://svn.forgerock.org/openam/trunk@6154 0f4defcf-c51a-4c67-9f44-6fb5eba73c5d
06 Aug, 2013
9 commits
-
…y headers being injected by the agent. git-svn-id: https://svn.forgerock.org/openam/trunk@6152 0f4defcf-c51a-4c67-9f44-6fb5eba73c5d
-
…dmin-guide/index.html#authn-from-browser ) https://bugster.forgerock.org/jira/browse/AME-2070 http://sources.forgerock.org/cru/CR-2104 git-svn-id: https://svn.forgerock.org/openam/trunk@6150 0f4defcf-c51a-4c67-9f44-6fb5eba73c5d
-
Changing lockout error code git-svn-id: https://svn.forgerock.org/openam/trunk@6146 0f4defcf-c51a-4c67-9f44-6fb5eba73c5d
-
Adding missing i18n keys to amAuthAD.properties git-svn-id: https://svn.forgerock.org/openam/trunk@6145 0f4defcf-c51a-4c67-9f44-6fb5eba73c5d
-
git-svn-id: https://svn.forgerock.org/openam/trunk@6143 0f4defcf-c51a-4c67-9f44-6fb5eba73c5d
-
…json/serverinfo/cookieDomains anonymously git-svn-id: https://svn.forgerock.org/openam/trunk@6141 0f4defcf-c51a-4c67-9f44-6fb5eba73c5d
-
git-svn-id: https://svn.forgerock.org/openam/trunk@6139 0f4defcf-c51a-4c67-9f44-6fb5eba73c5d
-
git-svn-id: https://svn.forgerock.org/openam/trunk@6138 0f4defcf-c51a-4c67-9f44-6fb5eba73c5d
-
…t be replaced during the filtering process of the maven build. git-svn-id: https://svn.forgerock.org/openam/trunk@6137 0f4defcf-c51a-4c67-9f44-6fb5eba73c5d
05 Aug, 2013
6 commits
-
git-svn-id: https://svn.forgerock.org/openam/trunk@6136 0f4defcf-c51a-4c67-9f44-6fb5eba73c5d
-
git-svn-id: https://svn.forgerock.org/openam/trunk@6134 0f4defcf-c51a-4c67-9f44-6fb5eba73c5d
-
git-svn-id: https://svn.forgerock.org/openam/trunk@6130 0f4defcf-c51a-4c67-9f44-6fb5eba73c5d
-
git-svn-id: https://svn.forgerock.org/openam/trunk@6129 0f4defcf-c51a-4c67-9f44-6fb5eba73c5d
-
git-svn-id: https://svn.forgerock.org/openam/trunk@6128 0f4defcf-c51a-4c67-9f44-6fb5eba73c5d
-
…s to avoid being replaced incorrectly during maven build process. git-svn-id: https://svn.forgerock.org/openam/trunk@6125 0f4defcf-c51a-4c67-9f44-6fb5eba73c5d