Skip to main content

Identity Provider

To organize multifactor authentication and single sign-on to web applications (Web Single Sign-On), the Identity Provider (IDP) module is used. For integration with target solutions, this module supports the following protocols:

  • SAML 2.0 (Security Assertion Markup Language)
  • OIDC 1.0 (OpenID Connect)
  • OAuth 2.0

This guarantees compatibility with a wide range of commercial systems. Using IDP relieves the user of the need to memorize multiple credentials: only one set of credentials is required to access all integrated systems. Authentication is performed centrally on the Identity Provider side.

IDP is implemented in the format of a web application and is deployed in the customer infrastructure. During the access gaining process, the target application redirects the user to the IDP page for authentication; if it is successful, the user is redirected back to the target application with the Authenticated attribute, where their session is opened.

Install and configure Identity Provider

Authentication technologies​

IDP supports the following user authentication technologies:

  • the domain password
  • OATH one-time passwords: TOTP and HOTP
  • one-time codes sent by SMS and email
  • one-time codes and push notifications in the Telegram messenger
  • one-time codes and push notifications in the Axidian Key mobile application

Where it can be used​

Both corporate on-premise applications (such as solutions from SAP, Citrix, and others) and cloud services such as Office 365, Salesforce, Slack, Google Workspace (formerly G Suite), and others can be included in the WebSSO and MFA perimeter.

The integration is performed on the server side, which makes it possible to use the MFA and WebSSO approach on any device with a browser: a PC, a smartphone, or a tablet.