How can we help?

FIDO2 Support with Ping

Usii Bilal - VS Support
Usii Bilal - VS Support
  • Updated

Introduction

From version 6.11 of vSEC:CMS it is possible to manage and issue any supported FIDO2 credential and push the FIDO2 credential to Ping IdP.

vseccms-fido architecture - white.png

In this article we will describe how you can set this up for use within vSEC:CMS. 

Important
FIDO2 credentials typically use HID interface for communicating with the device. If attempting to use/manage the FIDO2 credential over an RDP connection then this will not be possible as USB forwarding of HID supported devices is not possible out of the box. Therefore, when managing such credentials with vSEC:CMS you need to do this directly on a host where the device is attached to.
Important
It is required to install the RSDM service on any client where self-service FIDO2 operations are to be allowed. The RSDM service will allow for administration operations to be performed when issuing a FIDO2 credential or setting/changing the FIDO PIN.
Untitled.png 

Configure Ping Connector

Navigate to Options - Connections and select FIDO2 (IdP) if it exist, otherwise click Add and add FIDO2 (IdP)

Click Add and enter a name for the template and select Ping Identity IdP from the Type drop-down list. 

In the Host Parameters section enter the Directory (tenant) ID, Application (client) ID, Client Secret, Rest API Auth Endpoint and Rest API Endpoint applicable to your Ping setup. 

In the Relying Party section for the Name enter the human-palatable name of the relaying party. The Id should be a valid domain string identifying the WebAuthn relying party on whose behalf a given registration or authentication ceremony is being performed. The Origin should match the endpoint the user is provided to access the signing service, as is the case in a standard WebAuthn service. The Icon URL is an optional field for the URL of the relaying party icon.

Click Save to save the settings and complete this step.

Untitled.png

Configure Credential Template

It will be required to perform the next steps from a client which has the vSEC:CMS Admin application installed (see the article Install Admin Application on how to set this up if you don't have this setup already).

Navigate to Templates - Card Templates and click Add. Click the Edit link beside General.

Enter a template name and click the Detect button. Make sure that you have the token attached and selected from the reader drop-down list and click Ok. You should see something similar to below. 

Untitled.png

Leave all other settings as is and click Ok.

Untitled.png

In the Issue Card section enable Assign user ID  and select the user directory that you wish to use from the drop-down list.

In the FIDO2 Options section click the Manage button. Click Add. Enter a name and select the Ping connector created earlier for the IdP.

Enable Requires Resident Key if your IdP is configured to support this feature. 

Select either Use Default Password or Password defined by Operator. If you use Use Default Password then the defined password in Default Password for User will be used when adding the user to Ping. Otherwise the operator issuing the FIDO2 credential will be prompted to create a password for the user who will be created at the Ping.

You can configure how the authenticator name will be shown in the IdP (if the IdP supports this), either use default or enter a custom name in the Token Name field in the Token Display Name section.

In the FIDO2 PIN section enable the Enable FIDO2 PIN option in order to be able to use the FIDO credential.

Click Save to complete the configuration.

Untitled.png

Enable the FIDO2 Enrollment checkbox and select the template you want to use from the drop-down list.

Leave all other settings as is and click Ok to save and close.

Untitled.png

Click the Edit link for Initiate Card and enable Update Credentials at FIDO2 IdP. This will push the public key credential for the user to IDaaS setting the FIDO2 PIN on the credential.

Untitled.png

Click the Edit link for Revoke Card and enable Update Credentials at FIDO2 IdP. This will update the IdP when the authenticator is revoked. Additionally, enable Force FIDO2 Authenticator data deletion at IdP which will remove the authenticator at the IdP when the credential is revoked.

Untitled.png

Click Ok so save and close the configuration for the template.

Issue FIDO2 Credential

The FIDO2 credential can be issued either using the vSEC:CMS Admin or Agent applications. For either of these application refer to these articles Install Admin Application and Install Agent Application for instructions on how to set these up. 

In this guide we will use the Agent Application.

Navigate to the Life Cycle tab and with a FIDO2 credential attached select the Issued oval along with the template from the available drop-down list and click Execute.

Untitled.png

This will trigger the issuance flow. You will be prompted to select a user from your directory who the token will be issued to.

vSEC:CMS will check if the selected user has an account on Ping (vSEC:CMS will request Ping to add an account if one does not exist), and it will then generate the FIDO2 credential and publish the public key for the user to Ping. The user will be prompted to touch their credential during issuance so important to follow the on-screen prompts during this flow.

At the end of the issuance the token will be Issued. You can activate the token by selecting Active and setting a FIDO2 PIN that can then be used by the end used.

Alternatively, the end user can set the FIDO2 PIN using the vSEC:CMS User application. The vSEC:CMS User application needs to be online and connected to the backend vSEC:CMS service to perform setting a FIDO2 PIN.

Untitled.png Now the user, for example, can try to login to their Ping account. 

From the vSEC:CMS Admin console you can see details about the managed credential from Repository - Smart Cards by selecting a credential and clicking the Details button.

Untitled.png

If you then need to revoke the credential, for whatever reason, the credential will be revoked on the IdP. For example, from the Life Cycle tab search for a user who you wish to revoke and you can then verify that the FIDO2 credential is revoked on the IdP by trying to log in with the credential.