...
| Table of Contents |
|---|
1 - Single Sign On
1.1 Metadata endpoint
1.1.1 Expose metadata endpoint
| Status | ||||||||
|---|---|---|---|---|---|---|---|---|
|
The application metadata endpoint is publicly available for Maestrano. See SDK-free Integration#freeIntegration-1-MetadataEndpointtrueRedRequired
1.2 Initial Single Sign On
1.
...
2.1 Company creation
| Status | ||||||||
|---|---|---|---|---|---|---|---|---|
|
Given a new user triggers the SSO and the group_id does not match any existing Company, a new Company is created using the Company name and group_id reference
1.
...
2.2 User creation with known Company
| Status | ||||||||
|---|---|---|---|---|---|---|---|---|
|
Given a new user triggers the SSO and the group_id matches a Company group_id, a User is created using the first name, last name and user_id reference and is associated to the existing Company
1.
...
2.3 User creation with unknown Company
| Status | ||||||||
|---|---|---|---|---|---|---|---|---|
|
Given a new user triggers the SSO and the group_id does not match any Company group_id, a Company is created as per 1.1.1 and a User is created using the first name, last name and user_id reference and is associated to the created Company
1.
...
3 Subsequent Single Sign On
1.
...
3.1 User with user_id matching an existing account
| Status | ||||||||
|---|---|---|---|---|---|---|---|---|
|
Given an existing user triggers the SSO and the user_id is know, the User is authenticated and logged into its account
1.
...
4 User migration
1.
...
4.1 User email matching - Applicable if user email is unique
| Status | ||||||
|---|---|---|---|---|---|---|
|
Given a new user triggers the SSO and the user_id is not known but the user email is, the user_id is linked to the user record. This means the User is already existing in your system and has subscribed to Maestrano service in order to link his account.
2 - Account management and Billing
2.1 Service subscription
2.1.1 Set up application billing on account creation
| Status | ||||||||
|---|---|---|---|---|---|---|---|---|
|
Given a cancellation notification is sent to the Group Webhook, the subscription to your service should be cancelled as per your T&Cs.
Note that you can put in place some mechanism to contact the users to reconnect your service or use it out of the Maestrano context. In this case you will need to handle the billing directly with the customer.
2.2 Subscription cancellation notification
2.2.1 Cancel subscription or access on group cancellation notification
| Status | ||||||||
|---|---|---|---|---|---|---|---|---|
|
Given a cancellation notification is sent to the Group Webhook, the subscription to your service should be cancelled as per your T&Cs.
Note that you can put in place some mechanism to contact the users to reconnect your service or use it out of the Maestrano context. In this case you will need to handle the billing directly with the customer.
2.2.1 Cancel user access on user cancellation notification
| Status | ||||||
|---|---|---|---|---|---|---|
|
Given a cancellation notification is sent to the Group User Webhook, the user access should be blocked if applicable.
This applies if the application pricing is based on the number of users, in this case as a user has been removed from the system, pricing should be updated accordingly
3 - Connec! data-sharing
...
When a notification is received from Connec! and the ID of the entity is known, the matching record is updated in the application
4 - Multi-tenant integration