Applications

Structure

Name	Type	Purpose	Info
name	string	The name of your App	⚠️ this data will be displayed in emails
description	string	Description of the purpopse of your app	💡 won't be displayed to end-users
application_type	integer	The techgnology which consume this App (ex: Angular)
application_logo_url	string	The logo for your App
allowed_scopes	string array	The complete list of scope that could be required for end-user actions	If 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_descriptions	Array of ScopeDescription	The complete list of scope that could be required for end-user actions	If 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_urls	Array of string URL	List of URLs that can be use to redirect from Cryptr	Be precise
allowed_web_urls	Array of string URL	List of URLs that can request Cryptr	Be precise
allowed_logout_urls	Array of string URL	List of URLs that be part of Cryptr end logout process	Be precise
allowed_origin_cors	Array of string URL	List of URLs that can request Cryptr for CORS policies	Be precise
id_token_expiration	integer	Duration of ID Token validity
meta_data	List 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"
  }
}