Set up my SSO Authentication (Version 4.x and above)

Apty supports Single Sign-On(SSO) authentication which allows a user to access multiple applications with one set of login credentials.

Apty supports 2 types of SSO Authentication:

• OAuth 2.0
• SAML 2.0

Enabling the SSO Authentication is a two step process:

Step1: Accessing the SSO Config

Step2: Configuring the SSO Authentication

• Configuring OAuth 2.0
• Configuring SAML 2.0

Step1: Accessing the SSO Config

1.  Login to the Admin Portal.

2.  Click System Settings in the left panel.

3.  In the System Settings page, click the SSO Config tab.

4.  Check the SSO Config box to enable SSO configuration for your system.

Step2: Configuring the SSO Authentication

Configuring OAuth 2.0

OAuth 2.0 is an authorization protocol designed to allow users to give access to their resources hosted by a service provider, without giving away credentials. OAuth 2 offers authentication flows for mobile, desktop, and web applications.

To set up OAuth 2.0 in Apty,

1.  Select OAuth 2.0 from the SSO CONFIG dropdown.

2.  Provide the following details required to configure OAuth 2.0:

• HOST_NAME: Apty URI where the application is deployed. SSO config Hostname should match with the present hostname. For example, https://companyname.apty.io
• APP_SCOPES: Requesting for the required details in success response from the Identity Provider. For example, openid, profile, offline_access, name, given_name, created_at, etc. For details refer to this source.
• CLIENT ID / CLIENT SECRET: Enable retrieval and revocation of OAuth 2.0 access tokens by providing app ID and app password.
• AUTH URL: String path to request an authorization code. Default to /oauth/authorize. 
• TOKEN URL: String path to request an access token from Identity Provider. Default to /oauth/token. 
• EMAIL_KEY: JSON key of the Authorization Success Response through which the Authorized User Email can be accessed.

3.  Click Save.

Configuring SAML 2.0

SAML SSO works by transferring the user’s identity from one place (the identity provider) to another (the service provider). This is done through an exchange of digitally signed XML documents. For example, a user is logged into a system that acts as an identity provider. The user wants to log in to a remote application, such as a support or accounting application (the service provider). The following happens:

• The user accesses the remote application using a link on an intranet, a bookmark, or similar, and the application loads.
• The application identifies the user’s origin (by application subdomain, user IP address, or similar) and redirects the user back to the identity provider, asking for authentication. This is the authentication request.
• The user either has an existing active browser session with the identity provider or establishes one by logging into the identity provider.
• The identity provider builds the authentication response in the form of an XML document containing the user’s username or email address, signs it using an X.509 certificate, and posts this information to the service provider.
• The service provider, which already knows the identity provider and has a certificate fingerprint, retrieves the authentication response and validates it using the certificate fingerprint.
• The identity of the user is established and the user is provided with app access.

To set up SAML 2.0 in Apty,

1.  Select SAML 2.0 from the SSO CONFIG dropdown.

2.  Provide the following details required to configure OAuth 2.0:

• HOST_NAME: It is the Apty URL where the application is deployed. For example, https://companyname.apty.io.
• ENTRY_POINT: It is the Identity Provider URI where the user will be redirected for authentication. 
• EMAIL_KEY: It is the JSON key of the Authorization Success Response through which the Authorized User Email can be accessed.

3.  Click Save.