Class SecUserTableWriteCallback

java.lang.Object
de.businesscode.bcdui.binding.write.WriteProcessingCallback
de.businesscode.bcdui.subjectsettings.SecUserTableWriteCallback

public class SecUserTableWriteCallback extends WriteProcessingCallback
To enable this class, add it as WriteProcessing/Callbacks/Callback/@class to bcd_sec_user BindingSet When writing to bcd_src_user we apply special handling: 1. Real column names of password and salt are not available in the BindingSet, so we set them here (for this one Wrq instance only, the value in BindingSet itself is not touched) Defaults are 'password' and 'password_salt', can be overwritten in web.xml in shiro as realmBcdJdbc.bcdSecUserPasswordColumnName/.bcdSecUserPasswordSaltColumnName 2. Password column writing is allowed only if a) the current user has the right given in PARAM_NAME_PERMISSION, which defaults to DEFAULT_PERMISSION, empty means everybody can write, or b) the old password is also given in an wrs:M and it matches the one currently found in database 3. If BindingItem password_salt is available in the BindingSet, we want the password salted On write we take the plain text pwd, hash it with salt and store both values. We may need to add the salt column before, if it is not present in the Wrq to the header and each row 4. If password BindingItem is not in the Wrq, or password is empty or equals NO_PW_GIVEN_VALUE, we remove the column
  • Field Details

  • Constructor Details

    • SecUserTableWriteCallback

      public SecUserTableWriteCallback()
  • Method Details