Encap (Section)#

Path: /profiles/profile{id, type}/settings/authentication-service/authenticators/authenticator{id}/encap

The settings for an Encap authentication provider

Parameters#

NameTypeRequiredDefaultDescription
account-managerleafrefrequiredThe Account Manager is responsible for credentials and accounts. Depending on whether you pick an account manager that support registration, the html-form will support creating accounts and managing the accounts
client-idstringrequiredThe ID of the authentication service Encap client
application-idstringoptionalencapThe application ID of the Encap mobile application being used
api-keystringoptionalThe API key to be used (only applicable when using the public Encap test server)
encap-server-urlurirequiredThe URL to where the Encap webservice is located (e.g., https://demo.encapsecurity.com/pt)
allow-registration-during-loginbooleanoptionaltrueWhether or not users should be able to add a new device during the login process
show-info-before-registrationbooleanoptionaltrueWhether or not the information page should be shown before the registration page
client-key-idleafrefrequiredThe key ID of the private key that will be used when signing messages sent to the Encap server
authentication-app-download-uriurioptionalThe URL where users may download the mobile authentication application
context-titlestringoptionalA title message that is sent to the encap server when starting authentication
context-contentstringoptionalA context body that is sent to the encap server when starting authentication, as text/plain
context-content-typestringoptionaltext/plainThe content type of the context-content
max-allowed-attemptsuint16optional3The maximum number of authentication attempts that is allowed to be sent during one session. When this value is set to 0, there is no maximum attempts enforced.
device-expirationuint32optionalSet a device expiration in seconds from the time the device is activated, if not set devices never expire. If this is set, it is not possible to override in the template.
auto-login-enabledbooleanoptionalfalseWhen active a login will be automatically performed after a successful registration

Subsections#

NameTypeDescription
non-interactive-registration SectionEnables the possibility to activate a new device without user interaction. This can be used when the app also serves as an OpenID Connect client.

Was this helpful?

New Documentation Site Available!


Check out our new docs at curity.io/docs/identity-server/