Open Misaka-L opened 1 month ago
I think currently there's a workaround for your use case.
You can still use either username or email as the sign-up identifier, and then after user registration and redirecting to your app, you can check if the user has both username and email fulfilled. If not, redirecting to a landing page in your app to ask the user to fulfill the missing information.
I think currently there's a workaround for your use case.
You can still use either username or email as the sign-up identifier, and then after user registration and redirecting to your app, you can check if the user has both username and email fulfilled. If not, redirecting to a landing page in your app to ask the user to fulfill the missing information.
This is the workaround I use currently.
I created a WebHook which invoke after user created/updated, and check is the user have both username and nickname.
This issue is stale because it has been open for 30 days with no activity. Remove stale label or comment or this will be closed in 5 days.
What problem did you meet?
In our case, our system needs users to have a valid username and email to work properly. But logto can only require users to set their email or require users to their username.
Describe what you'd like Logto to have
Support multiple sign-up identifier, for example: user must set their username and email during registration​.