This is a hybrid persistence processor to store confirmation codes in either Registry or in the JDBC stores as configured. When loading the persisted codes for validation purposes, this will check in both the places. But the priority will be given as configured.
This will provide an smoother migration from Registry to JDBC without loosing any codes and vice versa.
WSO2 Identity Server 5.7.0
Follow below steps to use this log appender.
- Build the project.
mvn clean install
- Copy the JAR file into <IS_HOME>/repository/components/lib directory.
- Open the file <IS_HOME>/repository/conf/identity/identity-mgt.properties file in a text editor and change
the recovery data processor's value as below.
Identity.Mgt.User.Recovery.Data.Store=org.wso2.carbon.identity.extended.recovery.store.HybridUserRecoveryDataStore
- Add the below line to the same file.
Identity.Mgt.User.Recovery.Data.Store.isJDBCPrioritized=true
(This will give priority to JDBC when storing/loading the confirmation codes. - Restart the server.
- Set the
Identity.Mgt.User.Recovery.Data.Store.isJDBCPrioritized=false
. - DO NOT change the
Identity.Mgt.User.Recovery.Data.Store=org.wso2.carbon.identity.extended.recovery.store.HybridUserRecoveryDataStore
. Leave it as hybrid processor. - Restart the server.
- Registry -
/_system/config/repository/components/org.wso2.carbon.identity.mgt/data
registry path. - JDBC -
IDN_IDENTITY_META_DATA
table.
- Add below lines to the
<IS_HOME>/repository/conf/log4j.properties
file. - Restart the server.
- Note that the codes are hashed using
SHA256
as a security precaution.