06 Dec, 2013

1 commit


11 Oct, 2013

1 commit


08 Oct, 2013

1 commit


03 Oct, 2013

1 commit


25 Sep, 2013

2 commits


04 Sep, 2013

1 commit


17 Aug, 2013

1 commit


15 Aug, 2013

3 commits

  • * 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
     
  • * Moving resources to their correct locations
    
    git-svn-id: https://svn.forgerock.org/openam/trunk@6285 0f4defcf-c51a-4c67-9f44-6fb5eba73c5d
    peter.major
     
  • * 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
     

12 Aug, 2013

1 commit


08 Aug, 2013

1 commit

  • 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
     

07 Aug, 2013

1 commit


06 Aug, 2013

1 commit


28 Jul, 2013

1 commit

  • Updated the property XML, so Local Site Properties button no longer throws
    error.
    
    git-svn-id: https://svn.forgerock.org/openam/trunk@6034 0f4defcf-c51a-4c67-9f44-6fb5eba73c5d
    peter.major
     

20 Jun, 2013

1 commit


14 Jun, 2013

1 commit


23 May, 2013

1 commit


28 Mar, 2013

1 commit


19 Mar, 2013

1 commit


18 Mar, 2013

2 commits


01 Feb, 2013

1 commit


31 Jan, 2013

1 commit

  • * Introduced SupportedAPITaglet and SupportedAllApiTaglet in order to
    prevent JavaDoc warnings
    * Created required package-info.java files for packages that are part of
    the public API
    * Updated pom.xml to refer to all the packages involved in the JavaDoc
    generation
    * Minor updates to Java classes to resolve JavaDoc warnings/errors
    
    git-svn-id: https://svn.forgerock.org/openam/trunk@4169 0f4defcf-c51a-4c67-9f44-6fb5eba73c5d
    peter.major
     

30 Jan, 2013

1 commit


29 Jan, 2013

1 commit


28 Jan, 2013

1 commit


17 Dec, 2012

1 commit


13 Dec, 2012

1 commit


12 Dec, 2012

5 commits


11 Dec, 2012

2 commits


08 Dec, 2012

1 commit

  • Fix for upgrade problems:
    * missing serverdefaults due to Maven migration
    * changes made to amSession.xml weren't picked up by upgrade system
    
    git-svn-id: https://svn.forgerock.org/openam/trunk@3832 0f4defcf-c51a-4c67-9f44-6fb5eba73c5d
    peter.major
     

07 Dec, 2012

2 commits