07 Mar, 2013

1 commit

  • git-svn-id: https://svn.forgerock.org/openidm/trunk@2026 d98387aa-ee2c-4292-a9e6-504d2a719fd3
    gael
     

04 Mar, 2013

1 commit


01 Mar, 2013

1 commit


25 Feb, 2013

2 commits


22 Feb, 2013

3 commits


21 Feb, 2013

1 commit


18 Feb, 2013

1 commit


13 Feb, 2013

1 commit


07 Feb, 2013

1 commit


05 Feb, 2013

1 commit


31 Jan, 2013

2 commits


24 Jan, 2013

1 commit


23 Jan, 2013

1 commit


22 Jan, 2013

3 commits


17 Jan, 2013

1 commit


15 Jan, 2013

2 commits


09 Jan, 2013

1 commit


08 Jan, 2013

2 commits


04 Jan, 2013

1 commit

  • … try using add when replace fails
    
    These changes allow for the possibility of a non-existent password property on the managed/user object as a valid state.  This could arise when, for example, a record was create via recon from a source system which doesn't expose a cleartext password.  Code changes to policy and onCreate script to make this more sensible, and within the UI code to do an "add"-type of patch rather than a "replace" patch (which would fail, since the property doesn't exist).
    
    git-svn-id: https://svn.forgerock.org/openidm/trunk@1864 d98387aa-ee2c-4292-a9e6-504d2a719fd3
    jake.feasel
     

18 Dec, 2012

2 commits


17 Dec, 2012

2 commits


15 Dec, 2012

1 commit


14 Dec, 2012

2 commits


13 Dec, 2012

5 commits


12 Dec, 2012

1 commit