...
Plugin | Plugin ID | Module(s) | Depends On | Authentication Flow ID | Latest Version | Bug Reporting |
---|---|---|---|---|---|---|
WebAuthn Authentication Plugin | net.shibboleth.idp.plugin.authn.webauthn | idp.authn.WebAuthn | authn/WebAuthn | 0.9.0-RCRC2 |
Installation of Pre-release Plugin
...
File | Description |
---|---|
| Properties file for configuration the plugin |
| XML file for configuration of new beans for the plugin |
| The authentication view |
| A username view for passwordless authentication |
| The FIDO2 credential registration view |
| A username view for the registration view |
| Additional styling for the WebAuthn views |
| Javascript library that wraps the WebAuthn API for encoding binary data |
| Additional Javascript to support functions on the WebAuthn views |
...
Video
...
Description
...
Register and use a new FIDO2 credential. Use Password and DuoOIDC MFA to authenticate (for the first time) to the registration page
...
Try usernameless login with no registered credentials (although some exist in the Chrome password manager). Then, register a new credential and use it as a passkey in a usernameless flow.
...
Overview of Configuration Steps
Add the relyingPartyId to conf/authn/webauthn.properties
Add the relyingPartyName to conf/authn/webauthn.properties
Decide how the flow should be used.
Configure the MFA flow to use the WebAuthn authentication method
Add the MFA flow to the
idp.authn.flows
property in conf/authn/authn.properties.
Think about which Authentication Context Class (Supported Principals) the flow should expose
Register a FIDO2 credential through the registration admin flow
Show your administrator how to remove user credentials
Configure your auditing requirements.
Anchor | ||||
---|---|---|---|---|
|
The IdP acts as a WebAuthn Relying Party when initiating the Web Authentication API to register and authenticate users. The identity of the Relying Party (IdP) must be configured in conf/authn/webauthn.properties.
The relyingPartyId: A valid domain string. Set to the IdP’s origin’s effective domain. FIDO2 credentials are scoped to, and can only be used for, a relying party. It does not include a scheme or port (as a normal origin would). Credentials are scoped to the Relying Party ID.
Note, ‘localhost’ can be used for testing.
The relyingPartyName: a human-palatable identifier for the relying party. Used for display purposes.
Optional allowPortOrigin: If true, any port is allowed for the given origin.
Optional allowOriginSubdomain: If true, any subdomain (of any depth) is allowed for the given origin.
Optional allowOrigins: Comma-separated set of origins to allow in responses from an authenticator for this Relying Party. If not set, the Relying Party ID is used (assuming the https scheme and the default port). Note, unlike the Relying Party ID, this includes the scheme and port.
Expand | ||
---|---|---|
| ||
|