Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »


When integrating with Maestrano, in order to ensure the best possible experience for your users, it is good practice to setup single sign on and single billing.
This article gives you the different scenarios to test in order to make sure that everything is working properly.

1 - Single Sign-On

The 6 following scenarios describe how single sign-on should work:

  1. When a user launches your application for the first time from the Maestrano dashboard on their company, it creates a new user account in your application, using the user and company details
  2. When the same user launches your application the following times from Maestrano (same user, same company, same app instance), it redirects them to the existing account already created in your application
  3. When a user launches your application from a second company on Maestrano (same user, second company), it creates a new user account in a new company in your application
  4. When a new user launches your application for the first time from an existing company, it creates a new user in an existing company in your application.
  5. When one of your existing users creates an account on Maestrano and launches your application from their dashboard, you should ask the user to be redirected to their account.
  6. When a user deletes your application on Maestrano, you should stop sending bills/invoices and stop fetching/sending data for this account to Maestrano.
  • No labels