Thanks for this great testing library. A real time saver for local development/testing.
I have a case where I use the mock server for local development and I need the user email. Since there is no way to set it via login (where it would be the most convenient), I figured we could add the ability to provide email as username.
The current behavior will remain unchanged, except when an email is provided, then we set it as the user email, and derive the username, given/family names from it.
For example, let's assume one provides an email in the username field of the login form with the following format:
firstname.lastname@somewhere.com
Then it will result in the following claims being set:
If the login user name is not an email, the provided value will be stored as is everywhere, except for email and given name, which won't be set (current behavior).
If you like the idea, feel free to adapt to your liking.
Thanks for this great testing library. A real time saver for local development/testing.
I have a case where I use the mock server for local development and I need the user email. Since there is no way to set it via login (where it would be the most convenient), I figured we could add the ability to provide email as username.
The current behavior will remain unchanged, except when an email is provided, then we set it as the user email, and derive the username, given/family names from it.
For example, let's assume one provides an email in the username field of the login form with the following format:
Then it will result in the following claims being set:
If the login user name is not an email, the provided value will be stored as is everywhere, except for email and given name, which won't be set (current behavior).
If you like the idea, feel free to adapt to your liking.