16 Sep, 2011

2 commits


15 Sep, 2011

2 commits


14 Sep, 2011

3 commits


13 Sep, 2011

1 commit


12 Sep, 2011

5 commits


09 Sep, 2011

7 commits


08 Sep, 2011

2 commits


07 Sep, 2011

1 commit


06 Sep, 2011

2 commits

  • Implement connection pooling, load-balancing, and fail-over support. Enable first set of unit tests.
    
    git-svn-id: https://svn.forgerock.org/opendj/trunk@7230 41b1ffd8-f28e-4786-ab96-9950f0a78031
    matthew
     
  • There are now several new params in the web.xml file to specify:
    - A DN and Password to provide default authentication between the DSML gateway and the LDAP server.
    - whether to use SSL (on LDAPS port) or StartTLS (against LDAP port)
    - whether TLS server certificate must be blindly trust.
    - Or the truststore and password to trust it
    
    All combinations tested with GlassFish 3.1 as the container, OpenDJ 2.5-SNAPSHOT as the LDAP server.
    
    
    git-svn-id: https://svn.forgerock.org/opendj/trunk@7229 41b1ffd8-f28e-4786-ab96-9950f0a78031
    ludo
     

02 Sep, 2011

1 commit


01 Sep, 2011

2 commits


31 Aug, 2011

1 commit


30 Aug, 2011

3 commits


29 Aug, 2011

1 commit


26 Aug, 2011

3 commits


25 Aug, 2011

1 commit


24 Aug, 2011

1 commit

  • …g filter of the form "(changeNumber>=xxxx)" where xxxx<firstChangeNumber.
    
    Matt pointed to the incriminated piece of code, which didn't consider that specific case.
    
    We should add some test for this, but since it involves purging, delays, I recommend to add that in functional test, not unit test.
    
    git-svn-id: https://svn.forgerock.org/opendj/trunk@7200 41b1ffd8-f28e-4786-ab96-9950f0a78031
    ludo
     

18 Aug, 2011

1 commit

  • Refactor PasswordPolicy implementation so that we now have a common parent type, "AuthenticatioPolicy", which will act as a common entry point for all authentication policies. In particular, password policies can be thought of as a specific type of authentication policy: one where authentication and the user's credentials are managed locally. PTA can be thought of as a non-local authentication policy: the password is managed by a third party.
    
    With this change we still only have one type of authentication policy and no attempt has been made to refactor code which uses it. More specifically, code such as the local backend WFE just type-casts the authentication policy to a password policy.
    
    Another implication of this change is that sub-entry based password policies now automatically inherit run-time changes made to the default password policy, whereas before a server restart was required.
    
    
    git-svn-id: https://svn.forgerock.org/opendj/trunk@7192 41b1ffd8-f28e-4786-ab96-9950f0a78031
    matthew
     

06 Aug, 2011

1 commit