FIDO Pre-reg with PingOne

Integration Guide

• Introduction
  • Pre-enrollment Options
• How it Works
  • Process Flow
  • Customer Environment
  • FIDO Connector
  • PingOne AIC Journeys APIs
  • FIDO Pre-reg API
  • Security Features
    • PingOne PingID/AIC Access
    • Pre-enrolled Credentials
    • PIN Provisioning
    • Transport Encryption
• Integration Procedure
  • API Versions
  • Prerequisites
  • Integration Steps
• Configuring PingOne PingID
  • FIDO Policy Authentication
  • Enabling On-Behalf of Registration
    • Creating an Application
    • Granting Role to Worker App
    • Enabling the Worker App
• Configuring PingOne AIC
  • Adding a Secrets Variable
  • Creating a Registration Journey
  • Creating an Authentication Journey
  • Enabling On-behalf of Registration
• Configuring Microsoft Entra ID
  • Registering Apps
    • FIDO Connector
    • FIDO Pre-reg Test Client
• Deploying to Azure
  • Creating an API Token
  • Creating a Resource Group
  • Creating a Custom Role
  • Assigning the Custom Role
  • Verifying Custom Role Assignment
  • Deploying the ARM Template
  • Configuring Container App Permissions
  • Authorizing Logic App Office 365 Usage
  • Configuring Environment Variables
• Testing the Deployment
  • Troubleshooting
    • Where to Start?
    • Verifying Shipment Status in Storage Browser
    • Verifying Delivery Status of YubiKey PIN
    • Checking FIDO Connector Logs
• Requesting Credentials and Shipments
  • Initial Authentication
• Managing Credentials and Shipments
  • Credential Requests
  • Shipment Requests
• Post-deployment Operations
  • Common Environment Variables
  • PingOne PingID/Ping AIC Variables
  • Configuring Key Vault and Storage Permissions
  • Rotating API Tokens
  • Rotating Application Client Secrets
  • Changing Microsoft 365 Email Account
  • Resending PIN Email
• API Reference
• Release Notes - FIDO Connector
• Copyright
  • Trademarks
  • Disclaimer
  • Contact Information
  • Getting Help
  • Feedback
  • Document Updated