Digipass S3 is now DigipassONE. This section is currently being updated to reflect our new name.

Configuring a Web App

  • Updated on Apr 23, 2026
  • Published on Apr 3, 2026
  • 2 minute(s) read
Prev Next

Use the Admin Console to configure your browser-based web app.

Step 1. Switch to the desired tenant and navigate to Configuration > Apps.

The Apps page appears. Find your app in the list and either click its name or the (edit) icon at the end of its row. If your app is not in the list yet, click the blue Add App button, select the Browser radio button to choose your platform and click Add. The App page appears.


Step 2. Enter the app’s package name in Package Name/URL. This name cannot be changed later. Also enter the App Name which is used for display purposes here in the Admin Console.

Step 3. If you want your web app to use the FIDO2 protocol, make sure that you have already completed the FIDO2 Configuration on the Server. Note that web apps do not support the FIDO UAF protocol at this time.

  1. Determine the Facet ID for Your Web App. The facet ID for your web app is the web origin of the app’s home page. The web origin is written as a URI, https://example.com. A web origin is defined by the scheme (protocol), host (domain), and port of the URL used to access it. The facet ID must contain the RP ID. See FIDO2: RP IDs and Facet IDs for an explanation of this requirement.

  2. Check FIDO2/WebAuthn so the FIDO2 Facet ID textbox appears.

    Usually, you can enter the facet ID for Package Name/URL and FIDO2 Facet ID. However, the value for these fields must be different if you need to differentiate among your web apps as described in Uniquely Name Apps with the Same Web Origin in the Developer Guide for Web. In this situation, in Package Name/URL enter the app name that you assigned using AppSDKInfo.setAppName().

Step 4. You can assign an Adaptive Ruleset that this app uses. Select the ruleset's name from the Adaptive Ruleset dropdown. For more information, see Configure Adaptive Rulesets.

Step 5. If your app uses OOB authentication, you can set this up now. Refer to Configuring Out-of-band Authentication.

Step 6. If the package name changed, enter the previous package name into Old Package Names. If the package name changed multiple times, enter all previous package names separated by commas.

The Auth Server uses the package name to uniquely identify an app. The server uses Old Package Names to consolidate what would otherwise be duplicate information for the app.

Step 7. Save your changes. Verify that the facet ID was added correctly to the server database by performing a client registration operation using the protocols that you configured. If the application facet ID was not correctly added to the database, user registration fails with error 4402.