bdba21c Oct 28, 2018
2 contributors

Users who have contributed to this file

@cainlevy @shashankmehra
47 lines (34 sloc) 2.26 KB


AuthN takes care of account data (username, password) and leaves the remaining user profile data to your application. This means that signup is a two-step process. If that inspires you to create a two-step user flow, that could be nice! But you can also create a traditional one-step signup process that submits with two API calls.




  1. Create a form that collects a user's preferred username (email?) and password.
  2. Additionally collect other fields like name, newsletter subscriptions, as needed.
  3. Validate everything, especially your account fields.
  4. Submit the username (email?) and password to AuthN.
  5. If AuthN creates an account, the user will be logged in without a user profile.
  6. Submit the remaining details to your application.

NOTE: If a user succeeds in creating an account (step 5) but fails to create a user (step 7) then your frontend needs a plan for how to rerun step 6 while preserving the result of step 5. Validating the data client-side (step 3) is important because it will significantly reduce the odds of this happening.

NOTE: If you are using emails as username (by setting USERNAME_IS_EMAIL to true) and you need the email for user profile as well then consider using either authn or your application as the source of truth. You can either:

  • Use authn as the source of truth and use Get Account API to get the user's email when creating the user profile.
  • Use your application as the source of truth and use the Update Account API to update the email in authn when creating the user profile.


  1. Validate and save the user's AuthN account_id along with your other user profile fields.

Related Guides