Skip to main content

Applications

Structure

NameTypePurposeInfo
namestringThe name of your App⚠️ this data will be displayed in emails
descriptionstringDescription of the purpopse of your app💡 won't be displayed to end-users
application_typeintegerThe techgnology which consume this App (ex: Angular)
application_logo_urlstringThe logo for your App
allowed_scopesstring arrayThe complete list of scope that could be required for end-user actionsIf you start a sign process from your app with a scope outside your app allowed_scopes you won't reach the end of the process
scope_descriptionsArray of ScopeDescriptionThe complete list of scope that could be required for end-user actionsIf you start a sign process from your app with a scope outside your app allowed_scopes you won't reach the end of the process
allowed_redirect_urlsArray of string URLList of URLs that can be use to redirect from CryptrBe precise
allowed_web_urlsArray of string URLList of URLs that can request CryptrBe precise
allowed_logout_urlsArray of string URLList of URLs that be part of Cryptr end logout processBe precise
allowed_origin_corsArray of string URLList of URLs that can request Cryptr for CORS policiesBe precise
id_token_expirationintegerDuration of ID Token validity
meta_dataList of MetaData

Precise Allowed URLs

Base of OAuth authentication processes is to known who are all interacting entities. That's why we must know which URLs are allowed for your use !

Scope Description

A scope description is there to explain why you request this scope to the end-user This description is localized to ensure translations depending on end-user locale.

We suggest to pre precise in your description to give end-user good understanding of the asked scope

Example

{
"email": {
"en": "Send you emails",
"fr": "Pouvoir vous adresser des emails"
},
"profile": {
"en": "Access to your profile",
"fr": "Accéder à votre profil utilisateur"
}
}