> For the complete documentation index, see [llms.txt](https://resmocom.gitbook.io/product/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://resmocom.gitbook.io/product/integrations/okta-integration.md). # Okta Integration ## Resmo + Okta Integration Fundamentals ![](/files/GIUtUk2zwPx6xwMjM6mD) Resmo continuously enhances your Okta asset visibility, security, and compliance. ### What does Resmo offer to Okta users? * Collect and monitor all Okta resources in one place, near real-time. * Query your Okta groups, users, policies, applications, rules, and more. * Perform automated audits for security and compliance. * Set up rule notifications based on Okta resource configurations. * Mitigate risks and remediate incidents faster ### How does the integration work? Once you sign up for Resmo, you can easily integrate your account with Okta using an API token and Okta Domain. Resmo uses API to do the initial polling and collect existing resources. Then, we receive resource changes and updates in real-time by regular polling. {% embed url="" %} {% hint style="info" %} **Tip:** Use [Audit Logs](/product/audit-logs/audit-logs.md) for comprehensive monitoring of all Okta activities and system events. {% endhint %} ### Common queries and rules * List application groups * See group rules that assign users to group * Identify inactive user factors * See application user count * Find policy rule count per policy * See applications with inactive status * Find policies updated in the last seven days ### Integration Walkthrough #### How to Install 1. Log in to your Resmo account and navigate to Integrations>Okta. 2. Click the Add Integration button from the opening modal. 3. On a new tab, sign in to your Okta organization as a user with administrator privileges. * In Okta, API tokens have the same permissions as the user who creates them, and if the user permissions change, the API token permissions also change. It is, therefore, good practice to create a service account to use when you create API tokens so that you can assign the token the specific privilege level needed. * For integrating with Resmo, either Read Only Administrator or Super Administrator must be used. If Read Only Administrator is used, Resmo will not reach the following resources: * Okta Support Setting * Features * Access Policies and Profile Enrollment Policies are provided by Okta Identity Engine. Resmo will check if the policy type is available in your account. Otherwise, they will not be collected. 4. Access the API page: In the Admin Console, select API from the Security menu and then select the Tokens tab. Click Create Token. ![](/files/5j53dEhCsRiXeJkZldlM) 5. Copy the created API key. ![](/files/KtgqtNkxORulQYf0V79Z) 6. Enter the copied API token on the integration screen’s API token field. ![](/files/QYDlFd2Tn1ayErWLaFCY) 7. Enter your Okta Domain on the integration screen’s Okta domain field. 8. Hit the create button, and you are ready to run queries. #### How to Uninstall 1. Go to Integrations>Okta. 2. Navigate to the Connected Integrations tab on the opening modal and select the account you want to remove. 3. There are two paths you may take: * To temporarily pause the integration, click the Disable button. * To permanently remove it, click Delete. ![](/files/Pdfv8LzYaK6oarOkNaOu) --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://resmocom.gitbook.io/product/integrations/okta-integration.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.