5.9.6. U2F Token Config¶
You need to configure the AppId of the privacyIDEA server. The AppId is define in the FIDO specification 1.
The AppId is the URL of your privacyIDEA and used to find or create the right key pair on the U2F device. The AppId must correspond the the URL that is used to call the privacyIDEA server.
The AppId must not contain any trailing slashes!
If specifying the AppId as the FQDN you will only be able to authenticate at the privacyIDEA server itself or at any application in a sub directory on the privacyIDEA server. This is OK, if you are running a SAML IdP on the same server.
But if you also want to use the U2F token with other applications, you need to specify the AppId like this:
pi-url is the path, if you are running the privacyIDEA instance in a sub folder.
/ttype/u2f is the endpoint that returns a trusted facets list. Trusted facets are other hosts in the domain example.com. You need to define a policy that contains a list of the other hosts (u2f_facets).
For more information on AppId and trusted facets see 1.
For further details and for information how to add U2F to your application you can see the code documentation at U2F Token.
You can use a U2F token on privacyIDEA and other hosts in the same Domain. To do so you need to do the following steps:
Configure the AppId to reflect your privacyIDEA server:
Add the path /ttype/u2f is crucial. Otherwise privacyIDEA will not return the trusted facets.
Define a policy with the list of trusted facets. (see u2f_facets). Add the FQDNs of the hosts to the policy:
saml.your-network.com otherapp.your-network.com vpn.your-network.com
The privacyIDEA plugin for simpleSAMLphp supports U2F with privacyIDEA starting with version 2.8.
Now register a U2F token on https://pi.your-network.com. Due to the trusted facets you will also be able to use this U2F token on the other hosts.
Now got to https://saml.your-network.com and you will be able to authenticate with the very U2F token without any further registering.