---
title: "Enabling FIDO2"
slug: "dpo-android-app-sdk-enable-fido2"
updated: 2026-10-27T19:40:13Z
published: 2026-10-27T19:40:13Z
canonical: "docs.onespan.com/dpo-android-app-sdk-enable-fido2"
---
> ## Documentation Index
> Fetch the complete documentation index at: https://docs.onespan.com/llms.txt
> Use this file to discover all available pages before exploring further.
# Enabling FIDO2
The information in this Section is specific to native FIDO2. At this time, FIDO2 multi-device passkey support requires a device running Android 9+. See [https://passkeys.dev/device-support/](https://passkeys.dev/device-support/) for current platform compatibility information.
If you want to allow users to seamlessly share FIDO2 credentials across your website and your Android application, the website owner must declare associations with apps in an assetlinks.json file. See [https://evaluation93.noknoktest.com:8443/.well-known/assetlinks.json](https://cdn.document360.io/038f59a7-abd0-4c14-9de7-3434d28b49fd/Images/Documentation/assetlinks.json?sv=2026-02-06&spr=https&st=2026-10-29T01%3A38%3A30Z&se=2026-10-29T02%3A38%3A30Z&sr=c&sp=r&sig=yOKViBTJ%2Fz6aFU8P7xOaoawAkz1y1t8wz%2FPoTFkwd30%3D) for an example.
The steps to create assetlinks.json are described below. For more information, refer to Google’s documentation about setting up interoperability with your website at [https://developers.google.com/identity/fido/android/native-apps](https://developers.google.com/identity/fido/android/native-apps).
1. Create a directory named .well-known under the website root.
2. Add a json file assetlinks.json to the .well-known directory with the mobile application configurations.
1. Make sure the file is accessible from a public network, in other words, crawlable from Google and is served with HTTP header Content_Type: application/json.
2. The file should be accessible without any 301 or 302 redirects.
3. Add configuration details in the assetlinks.json file. For example, to set up the Tutorial App mobile browser integration via FIDO2, add the following:
```json
[{
"relation": ["delegate_permission/common.handle_all_urls"],
"target": {
"namespace": "android_app",
"package_name": "com.noknok.android.tutorialappplus",
"sha256_cert_fingerprints": ["F1:C0:35:0C:F3:54:42:60:21:4B:56:6B:B6:6A:39:18:62:58:01:24:62:61:41:FA:BE:9F:CE:3C:1A:68:28:88"]
}
}]
```
When customizing your own app, replace the "com.noknok.android.tutorialappplus" package name with your own package name. You must also provide sha256 fingerprints of your app signing certificates in the "sha256_cert_fingerprints" array. You can provide more than one fingerprint, for example, one fingerprint each for debug and production builds.
1. Create a directory named WEB-INF under the .well-known directory, then create a file named web.xml that has the following configuration:
```xml
.wellknown
json
application/json
```
1. assetlinks.json needs to be accessible using HTTPs and port 443. You might need to add a connector to your server.xml file in /conf as follows:
```xml
```
As of January 2023, Android's FIDO2 implementation works without taking the additional steps mentioned in [Google's Documentation](https://developers.google.com/identity/fido/android/native-apps).