Open lucadv opened 5 years ago
@lucadv - It sounds like the issue here is that you are unable to confirm the user in Cognito without the username, which at this point in time your custom service does not have. Is this correct?
If so, can you please provide a little more detail explaining how a custom code will solve this problem?
Thanks.
Hi @haverchuck thanks for replying. So we are in the process of developing a new authentication adapter for our identity service. We have an endpoint for registration confirmation which accept 2 parameters: directoryName and registrationCode.
With the current authentication process, we create a user resource and a registration resource directly linked to the user. We then send the registrationCode to the user, and that code plus the directoryName is enough for us to lookup the user (...in order to set the status to CONFIRMED).
We would like, if possible, to not alter the confirm registration endpoint and force the user to pass an username. It's not a big deal to be honest, but if we could create a custom verification code that we can then associate to a user through a registration resource, that would be great. Thanks in advance.
@lucadv Ok, I'll mark this as a feature request for now. Thanks.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
I'm developing a new Cognito adapter for my identity service. As part of our registration flow we require users to provide the domain (userpool id in cognito) and the verification code and with that we can retrieve the user which we need to confirm.
In order to confirm a user in Cognito though, we need to know the username which at the moment we don't require in the endpoint.
I'd like to know if we can generate a custom verification code to send to the user (instead of the one AWS generates for us), so that we can lookup the user just by domain and verification code.