19 Mar, 2014

2 commits


17 Mar, 2014

1 commit


14 Feb, 2014

1 commit


12 Dec, 2013

1 commit


19 Nov, 2013

1 commit


23 Sep, 2013

2 commits


09 Aug, 2013

1 commit


18 Jul, 2013

1 commit


17 Jul, 2013

1 commit


11 Jun, 2013

1 commit


17 May, 2013

1 commit


30 Apr, 2013

1 commit


17 Apr, 2013

1 commit


19 Mar, 2013

1 commit


18 Mar, 2013

1 commit


08 Mar, 2013

1 commit


07 Mar, 2013

2 commits


22 Feb, 2013

1 commit


31 Jan, 2013

1 commit


23 Jan, 2013

1 commit


22 Jan, 2013

2 commits


17 Jan, 2013

1 commit


15 Jan, 2013

1 commit


08 Jan, 2013

1 commit


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
     

14 Dec, 2012

1 commit


13 Dec, 2012

2 commits


11 Dec, 2012

2 commits


09 Dec, 2012

1 commit


08 Dec, 2012

2 commits

  • Also included is an update to most recent changes to policy.js, fixing issue discovered with workflow testing.
    
    git-svn-id: https://svn.forgerock.org/openidm/trunk@1740 d98387aa-ee2c-4292-a9e6-504d2a719fd3
    jake.feasel
     
  • http://sources.forgerock.org/cru/CR-1057
    
    Calls to patch were failing now that validation is properly being applied to patch calls. The failure was due to the fact that the whole object was being validated, and some properties in the object were requiring reauth. So even if you were not changing a property which required reauth, the reauth validation rule was being raised. This fixed the problem by not raising the failure if the value being evaluated is the same as the current value for the object. 
    
    https://bugster.forgerock.org/jira/browse/OPENIDM-1011
    
    git-svn-id: https://svn.forgerock.org/openidm/trunk@1739 d98387aa-ee2c-4292-a9e6-504d2a719fd3
    jake.feasel
     

07 Dec, 2012

3 commits