Testing Single Sign-On and Single Billing integration


When integrating with Maestrano, it is good practice to setup single sign on and single billing.
Here are listed the different scenarios to test in order to make sure that everything is working properly.

1 - Single Sign-On

Single sign on allows user to have a unique account for both application and Maestrano. Please, make sure that the 6 following scenarios are validated in order to ensure a seamless experience to the users :

  1. When a user launches SSO enabled application for the first time from the Maestrano dashboard on their company, it creates a new user account in the application, using user's and company details
  2. When the same user launches same application the following times from Maestrano (same user, same company, same app instance), it redirects them to the existing account already created in the application
  3. When a user launches SSO enabled application from a second company on Maestrano (same user, second company), it creates a new user account in a new company in the application
  4. When a new user(invited by admin of company) launches SSO enabled application for the first time from an existing company, it creates a new user in an existing company of the application.
  5. When one of existing users of application creates an account on Maestrano and launches the application for the first time from their dashboard, Application should ask user if he wish to be redirected to existing account.
  6. When a user deletes application(from dashboard) on Maestrano, application should stop fetching/sending data for this account to Maestrano.


If you have any issues, you can refer to our article explaining how the SSO process works with Maestrano, containing examples of code in different languages: SSO Process

2 - Single Billing

The following scenarios, if validated, will ensure that users will receive a unique bill for each application they use on the Maestrano platform.

  1. In case the application has a free trial(can we checked in developer platform), when a new user subscribes to it, no bill is pushed to Maestrano before the end of free trial period.
  2. When a user subscribes to the application with a billing plan, a bill is sent to Maestrano for this organization and the user will be invoiced every month. Bill could be either monthly or recurring. It depends on the app provider.
  3. A new bill is sent to Maestrano for this organization every time the user should be invoiced
  4. When a user changes its billing plan on the application, the old bill is deleted from Maestrano and a new bill is created. User can either be charged based on new plan or pro-rata billing.
  5. Bill amounts are updated the month after.
  6. When the last (or unique) user of a company deletes the application on Maestrano, bill is deleted from Maestrano
  7. No new bill is sent to Maestrano

Again, you can refer to this article: Single Billing, in case of trouble.