For AI agents: a documentation index is available at the root level at /llms.txt and /llms-full.txt. Append /llms.txt to any URL for a page-level index, or .md for the markdown version of any page.
Logo
DeveloperAcademyCommunityStatus
  • Service Management
    • Overview
    • Concierge & Ticketing Capabilities Overview
    • Forms
    • Forms - Integration Specific Guides
    • Live Agent Chat / Handoff
    • Triage
    • Approval Mirroring
    • Ticket Interception
    • Generic Ticketing Integration: Ticket Gateway
  • Administration
    • MyMoveworks
    • Organization Information
    • Roles and Permissions
    • MyMoveworks SSO
  • Moveworks Setup
    • Accessing Moveworks Setup
    • First-Time Login via Magic Link
    • Moveworks Setup Modules
    • Moveworks Setup: Module How To Guides
    • Plugin Management
    • Monitor Alerts
    • Audit Logs
    • DSL Fields Defaults
    • Data Crawling View
    • API Playground
    • Setup Homepage
    • Troubleshooting Hub
    • Security and Privacy Settings
    • Configuration Delete
    • Advanced Config Editor
    • Identity configuration
    • Onboarding Stage
  • Security
    • Security
    • Hyperlink & Button Expiry
    • Attachment Handling
    • Moveworks Subprocessors
  • Provision Management
    • Overview
    • Access Software
    • Access Groups
    • Access Account
  • Access Requirements
    • Overview
    • Update Set Modules
    • Ticketing Systems & ITSMs Access
    • Identity and Access Management Systems Access
    • Multi-Factor Authentication (MFA) Systems Access
      • Duo Access Requirements
      • PingID MFA Access Requirements
    • Knowledge Access Requirements
    • Email Distribution List Systems Access
    • Facilities Management Access
    • Live Agent Chat Access
    • HR Information System Access
    • Expense Management Access
    • Calendar Management Access
  • Core Platform
    • User Identity
    • Moveworks On-Prem Agent
    • Approvals Engine
    • Entity Catalog
    • Configuration Languages
    • Moveworks Data Objects
    • SIEM
  • Employee Experience Insights
    • Overview
    • Breaking Down the Dashboard
    • Understanding Industry Benchmarks
    • Apps & Services
    • Impact Module
    • EXI Common Use Cases
    • Configure EXI
    • Ticket Backpolling
  • Knowledge Studio
    • Overview
    • Knowledge Studio Configuration
    • AI Powered Recommendations
    • Inspecting & Verifying Sources
    • Publishing Articles
    • Creating Knowledge Articles
    • Resolving IT Tickets Guidance
DeveloperAcademyCommunityStatus
On this page
  • Ping ID Identity Access Needs
  • Why do we need access to your PingID instance?
Access RequirementsMulti-Factor Authentication (MFA) Systems Access

PingID MFA Access Requirements

||View as Markdown|
Was this page helpful?
Edit this page
Previous

Chat Access Requirements

Next
Built with

Ping ID Identity Access Needs

Why do we need access to your PingID instance?

The Moveworks service interacts with your PingID instance to help employees associate their PingID with their mobile device so they can approve or reject authentication requests. Our services also help them create a bypass code to log in when their device is unavailable. Specifically, Moveworks takes the following actions in your PingID instance:

  • Retrieves user details from PingID based on their email addresses.
  • Creates PingID activation URLs for employees to reset the pairing between their existing PingID factor and set up a new factor.

Note: Configuring this access will only grant permissions to perform PingID MFA related operations and not any PingOne related operations.

  1. Log into Ping One Portal at https://admin.pingone.com/web-portal/login.
  2. On the top navigation bar, click on Setup and then select PingID and navigate to the Client Integration Section.
  3. To generate a new PingID properties file, click on + Generate and then click Save. Name this entry “Moveworks PingID Integration”. A new entry will be added to the Properties file list showing the new PingID Properties file.
    Note: if you have already generated three PingID Properties files, skip to the next step.
  4. In the Client Integration Section, you will need to download the PingID.properties file by clicking on Download under the Integrate with PingFederate and Other Clients sub section.
  5. Securely send your Moveworks Customer Success representative the properties file as shown below.