This looks like the same unresolved post from Vincent Doux on this forum as well.
When we create a request for a new account to create a user in a CUA child client, - and the user already exists in the CUA master - we find that the password fed back by CUP via its email that has the password link in it, is not the one as it was created by CUA in the respective child client.
Ergo, the user can not log on with the password provided by CUP.
CUP's provisioning message is OK, the user is properly created in the child client but the the password given by email from CUP doesn't allow to connect user on to the child client.
As a contra-test: When creating the user directly from CUA manually the password is however working corrrectly on the child client.
Does someone know how to have the correct password (CUA) in the CUP email notification or how to solve this?
Both Java and CUA master and Child Client are on 5.3 SP 6. I checked OSS note 1168508