24 Jun, 2014

4 commits

  • Used debugger to diagnose differences in encrypted password storage in JDK6 vs JDK7. Found that in JDK6, the encrpyted password is stored as 
    {"$crypto":{"value":{"data":"p2tiUCLFv71KNiEuRJQtyg==","cipher":"AES/CBC/PKCS5Padding","iv":"U0fF/6kKYfjtQQC8/l1c4Q==","key":"openidm-sym-default"},"type":"x-simple-encryption"}}
    
    whist in JDK7 it is stored as 
    {"$crypto":{"type":"x-simple-encryption","value":{"data":"p2tiUCLFv71KNiEuRJQtyg==","cipher":"AES/CBC/PKCS5Padding","iv":"U0fF/6kKYfjtQQC8/l1c4Q==","key":"openidm-sym-default"}}}
    
    Because key ordering is not predictable, we cannot use endsWith("\"}}") as part of the test.  Changed to }} as this matches the "{\"$crypto\":{" startsWith test.
    
    
    git-svn-id: https://svn.forgerock.org/openidm/trunk@3445 d98387aa-ee2c-4292-a9e6-504d2a719fd3
    brmiller
     
  • git-svn-id: https://svn.forgerock.org/openidm/trunk@3443 d98387aa-ee2c-4292-a9e6-504d2a719fd3
    Lana
     
  • git-svn-id: https://svn.forgerock.org/openidm/trunk@3442 d98387aa-ee2c-4292-a9e6-504d2a719fd3
    Lana
     
  • git-svn-id: https://svn.forgerock.org/openidm/trunk@3441 d98387aa-ee2c-4292-a9e6-504d2a719fd3
    jason
     

23 Jun, 2014

5 commits


22 Jun, 2014

1 commit


20 Jun, 2014

5 commits


19 Jun, 2014

5 commits


18 Jun, 2014

17 commits


17 Jun, 2014

3 commits

  • Disabling MANAGED_USER auth module for several samples, in favor of PASSTHROUGH to system/ldap/account
    
    Just toggled a boolean config value; no review necessary. Rationale for change:
    
    Previously, we attempted to authenticate using MANAGED_USER first, followed by a few others and then 
    finally PASSTHROUGH. The reason it was first created it this way was so that if there was a fully-
    populated managed/user entry, it would not need to query the remote system. This works fine if you 
    are syncing passwords between managed/user and the remote backend, but as mentioned in OPENIDM-1953, 
    that isn't always the case. To compound this problem, there is also the new function around role 
    calculation; this is per-auth module, and so if you want to calculate roles for a given user you would 
    need to do it for both MANAGED_USER and PASSTHROUGH, if they were both enabled. This redundancy is 
    annoying and a likely source of confusion. So, this change is to just disable the MANAGED_USER auth 
    module, and always use the PASSTHROUGH config.
    
    git-svn-id: https://svn.forgerock.org/openidm/trunk@3404 d98387aa-ee2c-4292-a9e6-504d2a719fd3
    jake.feasel
     
  • git-svn-id: https://svn.forgerock.org/openidm/trunk@3403 d98387aa-ee2c-4292-a9e6-504d2a719fd3
    jake.feasel
     
  • CR-3766 (First draft of an upgrade chapter for OpenIDM 3.0)
    
    git-svn-id: https://svn.forgerock.org/openidm/trunk@3402 d98387aa-ee2c-4292-a9e6-504d2a719fd3
    Lana