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
      • Active Directory & OpenLDAP Access Requirements
      • Microsoft 365 Access Requirements
      • Okta Access Requirements
      • OneLogin Access Requirements
    • Multi-Factor Authentication (MFA) Systems Access
    • 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
  • Why do we need access to your OneLogin instance?
  • Service Account Needed:
  • What is the account used for:
Access RequirementsIdentity and Access Management Systems Access

OneLogin Access Requirements

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

Multi-Factor Authentication (MFA) Systems Access

Next
Built with

Why do we need access to your OneLogin instance?

The Moveworks service interacts with your OneLogin instance to carry out one or more of the following:

  • fulfill employees’ software provisioning requests;
  • identify employees; and
  • help employees reset passwords, unlock locked accounts, help employees reset their multi-factor authentication, and warn employees when their password is about to expire.

Note that not all Moveworks+OneLogin deployments handle all of the tasks mentioned above, and is dependent on customer-specific discovery.

Service Account Needed:

A service account allows the Moveworks service to fulfill provisioning requests by adding users to roles in OneLogin. Create the API credential pair (client ID & client secret) and share with your Moveworks Customer Success team. This account must have the Manage Users permission in OneLogin.

https://developers.onelogin.com/api-docs/1/getting-started/working-with-api-credentials

Share the account credentials with your Moveworks Customer Success Team.

What is the account used for:

  • This account is used for the bot to be able to add users to OneLogin roles for Application Provisioning, identifying user attributes, and MFA Reset Functionality.