17 Jun, 2015

1 commit


14 May, 2015

1 commit


13 Apr, 2015

1 commit


01 Apr, 2015

1 commit


12 Mar, 2015

1 commit

  • …icense plugin in order to generate an automated report to track Open Source licenses
    Intermediate Git commits:
    - Wrong license for the com.sun.web.ui dependency
    - Switch to the latest version of Forgerock Parent to test the license merge (Maven license plugin)
    - Git svn rebase, new properties files and new license in existing properties files
    - Switch to the new Forgerock Parent version (1.2.8)
    
    git-svn-id: https://svn.forgerock.org/openam/trunk@12969 0f4defcf-c51a-4c67-9f44-6fb5eba73c5d
    b.lavit
     

11 Mar, 2015

1 commit


23 Jan, 2015

1 commit


26 Nov, 2014

1 commit


30 Sep, 2014

1 commit


23 Sep, 2014

1 commit


01 Aug, 2014

1 commit


03 Jul, 2014

1 commit


02 Jul, 2014

2 commits


20 Mar, 2014

1 commit

  • Implemented better handling for the case when the user cannot be found,
    this change should also ensure that getFullyQualifiedName returns with
    null if the identity cannot be found, so the lookup result can be properly
    cached in AMIdentity.
    
    git-svn-id: https://svn.forgerock.org/openam/trunk@8431 0f4defcf-c51a-4c67-9f44-6fb5eba73c5d
    peter.major
     

26 Feb, 2014

2 commits

  • Modified the error case handling for the authenticate method: now it always
    uses the username in the InvalidPasswordException (instead of user DN), so
    account lockout can work as expected.
    
    git-svn-id: https://svn.forgerock.org/openam/trunk@8232 0f4defcf-c51a-4c67-9f44-6fb5eba73c5d
    peter.major
     
  • Modified the IdRepo setting handling to pre 11 state:
    * auth-naming-attr is only used when performing authentication to find the
    user
    * users-search-attr is now used everywhere else to find the user
    * There was also a bug in the search method: it wasn't returning the search
    attribute's value, instead it always returned the RDN's value.
    
    git-svn-id: https://svn.forgerock.org/openam/trunk@8230 0f4defcf-c51a-4c67-9f44-6fb5eba73c5d
    peter.major
     

10 Jan, 2014

3 commits


08 Jan, 2014

1 commit


14 Dec, 2013

2 commits


09 Dec, 2013

1 commit


01 Nov, 2013

1 commit


03 Oct, 2013

1 commit


30 Sep, 2013

1 commit


27 Sep, 2013

2 commits

  • The code now handles the case when there is no filtered roles retrieved.
    New unit tests has been introduced to improve the coverage around DSEE
    roles and filteredroles.
    
    git-svn-id: https://svn.forgerock.org/openam/trunk@6679 0f4defcf-c51a-4c67-9f44-6fb5eba73c5d
    peter.major
     
  • Revisited the HBCF defaults from 1 minute to 10 seconds
    
    git-svn-id: https://svn.forgerock.org/openam/trunk@6678 0f4defcf-c51a-4c67-9f44-6fb5eba73c5d
    peter.major
     

05 Sep, 2013

2 commits


04 Sep, 2013

1 commit


22 Aug, 2013

1 commit


17 Aug, 2013

1 commit

  • This one turned out to be an issue with the modifyRoleMembership
    implementation: instead of modifying the user entries to have the nsRoleDN
    attribute, it was incorrectly setting the member DNs on the role entry.
    New tests have been incorporated to cover this scenario.
    
    git-svn-id: https://svn.forgerock.org/openam/trunk@6308 0f4defcf-c51a-4c67-9f44-6fb5eba73c5d
    peter.major
     

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
     

28 Jul, 2013

1 commit


06 Jun, 2013

1 commit