05 Sep, 2013

1 commit

  • The heartbeat connection factory is now added prior to the
    authenticated cf
    This change was made based on comments from Matt in CR-2269:
    "Note that I've changed the factory stacking order. Beforehand the
    HBCF wrapped the authentication factory which was wrong, since the
    initial bind would be performed before the initial heartbeat."
    
    git-svn-id: https://svn.forgerock.org/openam/trunk@6516 0f4defcf-c51a-4c67-9f44-6fb5eba73c5d
    peter.major
     

17 Aug, 2013

1 commit


16 Aug, 2013

1 commit

  • Changed the LDAPURL class so it is now capable to also store the LDAP
    scheme if necessary. The DLCF implementation has been also adjusted to
    handle the scenario when configuration stores are configured with mixed
    LDAP/LDAPS servers.
    
    git-svn-id: https://svn.forgerock.org/openam/trunk@6301 0f4defcf-c51a-4c67-9f44-6fb5eba73c5d
    peter.major
     

08 Aug, 2013

2 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
    peter.major
     
  • 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
     

06 Jun, 2013

1 commit


29 Apr, 2013

1 commit