I have implemented the wso2is-6.1.0 as a key manager to wso2am-4.3.0 and I have implemented an authentication policy where the user gets locked on creation by setting it up in identity-mgt.properties.

# If account verification is not enabled, following property will decide where user must be lock or not after user is created 
Authentication.Policy.Account.Lock.On.Creation=true
Authentication.Policy.Account.Lock.Time=0
Authentication.Policy.Account.Lock.On.Failure=true
Authentication.Policy.Account.Lock.On.Failure.Max.Attempts=3

Additionally it could be observed that the user does not get locked on creation with the following configuration in the deployment.toml.

[event.default_listener.identity_mgt]
priority= "50"
enable = false

[event.default_listener.governance_identity_mgt]
priority= "95"
enable = true

But if I set the event.default_listener.identity_mgt enable to true, the user gets locked on creation but is not unlocked properly using the carbon console. It says user profile updated successfully, but the account locked checkbox remains the same when the profile is viewed again.

What is the correct configuration that needs to be setup in order to lock user account on creation and also to unlock the same user using the carbon console?
Thanks in advance.