On-board a native application

Introduction

This guide describes how to use the Verify administration UI to on-board a native application which will use Adaptive Access.

Pre-requisites

You must have a native web application access policy. This is required in order to create an application definition which is configured for policy-based authentication. See Adaptive Access Policy for Native applications.

Your must have a custom application definition for your application. The following minimum configuration is required in the Sign-On tab:

ParameterValue
Sign-on MethodOpenID Connect 1.0
Grant typesContext-based authorization
JWT Bearer
Access policiesUncheck "Use Default Policy"
Select a native custom application policy.
Apply access policy to API grant typesJWT Bearer
Context-based authorization

For more detailed information about each field, see Configuring single sign-on in the OpenID Connect provider.

Enable Adaptive Sign-on

  1. Navigate to the Adaptive sign-on tab.
  2. Enter an Allowed domain. An allowed domain enables the Adaptive access session collection and detection for a given sub-domain. For example sub.domain.com, *.domain.com.
  3. Click Add domain + if you wish to add additional domains.
  4. Click Generate. This will take up to 30 minutes to complete.

📘

Allowed domains are important

When using Adaptive access for native applications, Adaptive access will only run on webpages matching the allowed domains entered when on-boarding the application.

You can navigate away from Adaptive sign-on tab and check on the generate progress at a later stage.

Adaptive Sign-OnAdaptive Sign-On

Adaptive Sign-On


What’s Next

Now that your application is on-boarded you can start instrumenting your application. The generated snippet host / snippet ID enables you to make calls to the adaptive web SDK.

Did this page help you?