When setup script is run the settings not defined in the linux/win32.config file are generated for you. These settings typically involve UIDs, passwords and other secrets.

If you are using our APIs which are authenticated with an OAuth2 access token we suggest you add the client IDs of the related OAuth2 applications into your linux/win32.config file if they do not yet exist there.

Setting Description Location to find the current value Example

sso-api.uuid

SSO API client ID used as a scope in the access token request

SSO Management UI:
System → SSO API → Applications → SSO API OAuth2 2.0 ID

or ubiloginEntityID of dn: cn=SSO API,ou=SSO API,ou=System,<suffix> in ldap/secrets.ldif

sso-api.uuid = 923f002b-2cb7-4318-92a8-1f43c92c38ed

totp.uuid

TOTP API client ID used as a scope in the access token request

SSO Management UI:
System → TOTP API → Applications → TOTP API OAuth2 2.0 ID

or ubiloginEntityID of dn: cn=TOTP API,ou=TOTP API,ou=System,<suffix> in ldap/secrets.ldif

totp.uuid =
2387675c-dd6b-4d30-9b5b-1c0b43a946e9

accounting.client.uuid

Accounting Service API client ID used as a scope in the access token request

SSO Management UI:
System → Accounting → Applications → Accounting OAuth2 2.0 ID

or ubiloginEntityID of dn: cn=Accounting,ou=Accounting,ou=System,<suffix> in ldap/secrets.ldif

accounting.client.uuid =
5e591b36-4a86-4d3d-9247-70adfb77cc8e

Browser not supported