org.forgerock / org.forgerock.openam

25 Mar, 2014

1 commit

21 Mar, 2014

1 commit

07 Mar, 2014

2 commits

25 Feb, 2014

2 commits

24 Feb, 2014

1 commit

19 Feb, 2014

1 commit

18 Feb, 2014

3 commits

12 Feb, 2014

2 commits

06 Feb, 2014

2 commits

03 Oct, 2013

1 commit

25 Sep, 2013

1 commit

04 Sep, 2013

1 commit

15 Aug, 2013

2 commits

  • 433de877   Integrating AME-2372 branch part III: ... Browse Dir » 
    * Removing obsolete code
* Moving lockhart to console
* Separating out configurator and upgrade tool from openam-core
* Moving LDIF files to their correct location
* Removing unnecessary files
* Fixing component builds after removing openam-locale
* Updates based on review comments

git-svn-id: https://svn.forgerock.org/openam/trunk@6286 0f4defcf-c51a-4c67-9f44-6fb5eba73c5d
    peter.major
     
  • 2684d91a   Integrating AME-2372 branch part I: ... Browse Dir » 
    * Use commons-lang 2 consistently, and remove commons-lang3
* Remove JMQ/JMS dependencies
* Removing backport-util-concurrent
* Aligning license headers
* Moving amadmtools to openam-core for now (it may be extracted in the
future, when all the CLI tools have their own modules)
* Consolidating POMs

git-svn-id: https://svn.forgerock.org/openam/trunk@6284 0f4defcf-c51a-4c67-9f44-6fb5eba73c5d
    peter.major
     

08 Aug, 2013

1 commit

  • a6ff71f6   Integrating AME-1809 / AME-2156 branch ... Browse Dir » 
    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
    peter.major
     

29 May, 2013

1 commit

  • f755dddf   AME-804: (CR-1483) Implement new token storage format ... Browse Dir » 
    AME-259: (CR-1751) CTSv2 scale to 2000 sessions/sec

Upgraded the Core Token Services to v2 with a more generalised token storage format. This cover all Core Token Service areas including Sessions, SAML Tokens and OAuth Tokens. New LDAP schema is included which fits into the previous schema. Performance testing of implementation finds its performance to be acceptable with the possibility of further tuning later.

git-svn-id: https://svn.forgerock.org/openam/trunk@5405 0f4defcf-c51a-4c67-9f44-6fb5eba73c5d
    rwapshott
     

21 May, 2013

1 commit

03 May, 2013

1 commit

02 Feb, 2013

1 commit

01 Feb, 2013

1 commit

29 Jan, 2013

1 commit

12 Dec, 2012

4 commits

11 Dec, 2012

1 commit

18 Nov, 2012

1 commit

16 Nov, 2012

1 commit

09 Nov, 2012

1 commit

07 Nov, 2012

1 commit

05 Nov, 2012

1 commit

01 Nov, 2012

1 commit

  • 9f0cf9ae   Fix for OPENAM-1649 - review: CR-712 ... Browse Dir » 
    Due to changes to schemata, you need to:
* cd openam-shared && mvn clean install
* cd openam-schema && mvn clean install
and only then can you actually run the full build

git-svn-id: https://svn.forgerock.org/openam/trunk@3513 0f4defcf-c51a-4c67-9f44-6fb5eba73c5d
    peter.major
     

16 Oct, 2012

1 commit

15 Sep, 2012

1 commit