Page Comparison

By default we consider that the domain managing user identification is the same as your application host (see above host parameter).
If you have a dedicated domain managing user identification and therefore responsible for the single sign-on handshake (e.g: https://idp.my-app.com) then you can specify it here.

This is the path in your application that allows users to initiate the Single Sign-On handshake.
Upon reaching this endpoint your application will automatically create a SSO request and redirect the user to Maestrano. Maestrano will then authenticate and authorize the user.

This is your application path to the SAML endpoint that allows users to finalize SSO authentication.
During the 'consume' action your application sets users (and associated group) up and/or log them in.

Maestrano will issue a DELETE request to the following paths to notify you of any service cancellation (group deletion) or any user being removed from a group.

(Only for applications hosted on Maestrano.)
The endpoint to trigger when the application is started.
This should be used as a hook to retrieve updates from Connec!™ whils the application was idle.

This is the path of your application where notifications (created/updated entities) will be POSTed to.
You should have a controller matching this path handling the update of your internal entities based on the Connec!™ entities you receive