Page Comparison

...

The metadata endpoint should return a JSON document describing your configuration. Note that the call initiated by Maestrano to retrieve your metadata is authenticated via HTTP Basic authentication using your own API credentials (shared secret).

Warning
The

...

fields

...

listed below are listed in Snake case. As our SDKs respect languages conventions, fields' names may vary from an SDK to another (e.g.: Java SDK). Please, refer to your SDK documentation for the exact names to use.

your choice

Field	Type	Required for OpenID SSO	Required for SAML SSO	Change with the tenant and the environment	Defaults fields	Description
environment	string	-	-	Yes (with the env. only)	-	The environment of the platform your are integrated to; accepted values: - "test" (for the sandbox) - "uat" - "production"
app.host	string	Yes	Yes	Yes (with the env. only)	-	Your application host For UAT and Production environments, it must be a publicly resolvable URL (you cannot use "http://localhost:3000" for instance)
api.id	string	Yes	Yes	Yes	-	The id of your app It corresponds to the App ID on your Maestrano App Provider API Dashboard We will provide you the correct value for other tenants than Maestrano
api.host	string	Yes	Yes	Yes	if "environment" is set: value for Maestrano tenant	The platform host We will provide you the correct value for other tenants than Maestrano
sso.idm	string	-	-	-	same as config.app.host	Your Identity Domain Manager
sso.init_path	string	- Yes	Yes	your choice This value can be changed on a per-tenant basis	-	Your application path that allows users to initiate the Single Sign-On handshake We will provide you the correct value for other tenants than Maestrano. 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 and send him back to your application.
sso.consume_path	string	-	Yes	your choiceThis value can be changed on a per-tenant basis	-	Your application path to the SAML endpoint that allows users to finalize SSO authentication During the 'consume' action your application sets users and group up and/or log them in.
sso.idp	string	Yes	Yes	Yes	if "environment" is set: value for Maestrano tenant	The platform host We will provide you the correct value for other tenants than Maestrano
sso.x509_fingerprint	string	-	Yes	Yes	only if "environment" is set: value for Maestrano tenant	We will provide you the correct value for other tenants than Maestrano
sso.x509_certificate	string	-	Yes	Yes	if "environment" is set: value for Maestrano tenant	We will provide you the correct value for other tenants than Maestrano
connec.host	string	Yes	Yes	Yes	if "environment" is set: value for Maestrano tenant	The Connec! endpoint used to fetch data from We will provide you the correct value for other tenants than Maestrano
webhook.account.groupgroups_path	string	Yes	Yes	your choiceThis value can be changed on a per-tenant basis	-	Your application path where a notification will be posted when an instance of your application is deleted
webhook.account.group_users_path	string	Yes	Yes		This value can be changed on a per-tenant basis	-	Your application path where a notification will be posted when a user is removed from an instance of your application
webhook.connec.notifications_path	string	Yes	Yes	your choiceThis value can be changed on a per-tenant basis	-	Your application path where notifications (created/updated entities) will be POSTed to
wenhookwebhook.connec.subscriptions	hash keys: predefined entities values: boolean	Yes	Yes	No	false for all entities	The list of entities (organizations, people, invoices etc.) for which you want to be notified upon creation/update in Connec!™

...

Versions Compared

Old Version 18

New Version Current

Key