If you have an app that uses a standalone, remote UAF FIDO client, then you must also update facets.uaf. Most Digipass S3 customers use embedded FIDO clients from the App SDK, so they can skip this step.
Note that you must perform this step, if required, after you add your app in the Admin Console. A remote UAF FIDO client relies on this file for the list of mobile apps and URLs that are authorized to access it.
facets.uaf is tenant-specific, so make sure you are editing the right file. facets.uaf for the default tenant is located at https://<server_host>/facets/facets.uaf. For other tenants, you can access this file from the web with the following path: https://<server_host>/facets/<tenant_id>/facets.uaf
1. Login as a user and, if needed, switch to the correct tenant in the Admin Console. Find the URL to access facets.uaf in the UAF property APP ID which you can view in Configuration > Authentication Methods > FIDO UAF.
For example:
/usr/share/tomcat/webapps/facets/facets.uaf
2. Edit the facets.uaf file for the affected tenant on the publicly accessible hosting server. Create a new line for each trusted facet. This example facets.uaf adds the highlighted facet ID string “android:apk-key-hash:Bc9rEk16GTEpN3bbD+4zV/H3Msk” as the final ID in the list.
{
"trustedFacets": [
{
"version": {
"major": 1,
"minor": 0
},
"ids": [
"ios:bundle-id:com.noknok.ios.tutorialappplus",
"ios:bundle-id:com.noknok.ios.sampleapp",
"android:apk-key-hash:lXHH7DSBcDnOS1RQ1Sd95KaitYA",
"android:apk-key-hash:SvYZ4Sgas9T2+6DpNj566iscuns",
"android:apk-key-hash:Bc9rEk16GTEpN3bbD+4zV/H3Msk"
]
}
]
}About the Facets Web App
The Facets Web App interacts with remote FIDO UAF clients to provide facets.uaf files. Remote FIDO clients rely on facets.uaf for the list of mobile and web apps that are authorized to access it. Facets Web App is installed during API Server installation. You never directly use this app.
For Facets Web App to work properly, you need to assign the URL to facets.uaf as the value for the App ID. See section Assigning the App ID.