OIG Access Requests

This page is for articles relating to the new Okta Identity Governance (OIG) Access Requests function.

OIG Access Requests Overview

Access Requests is the component of OIG that came from the atSpoke acquisition. As it is a new function with some unique capabilities, it makes sense to consolidate all OIG Access Requests articles here.

The following figure shows how Access Requests works in the wider Okta Identity Governance ecosystem.

OIG Architectural Overview

Access Requests integrates with the Okta Identity Cloud (Okta) to retrieve users, groups and application lists, and also it runs actions in workflows that will update (or retrieve) objects in Okta Universal Directory (e.g. add user to group, assign user to application).

Access Requests can also integrate with ITSM tools like ServiceNow and Jira to log tickets.

Users (including access request reviewers, such as managers, and administrators) may interface directly with Access Requests through the user interface, or via a chat bot in Slack/Teams. In the wider Okta picture, all of these could be SSO’d to from the Okta Dashboard.


OIG Access Requests Posts

The following articles are specific to OIG Access Requests.

Okta Identity Governance and/or Service Now – Architectural Patterns

Most organisations have some ITSM or service request tool, and ServiceNow is the most common. So it’s understandable that any conversation about Okta Identity Governance, particularly access requests, will involve comparison with ServiceNow or integration patterns for both products. How do you approach an access request solution? Which product is going to meet your needs…

Logging a ServiceNow Request via Workflows from OIG Access Requests

A common ask for Okta Identity Governance is to be able to log at ticket in a service desk tool, like ServiceNow, for manual provisioning activities after following an approval process in Access Requests. This article explores one approach to this using OIG Access Request events in the Okta System Log, Event Hooks and Okta…

OIG Access Requests – Public or Private?

If you have looked at Okta Identity Governance Access Requests, you will know that a request will contain the history of the activity, such as the questions asked and answered, approval steps performed and actions taken. Did you know that a request, with all this information, can be Public or Private? Did you know that…

OIG Access Requests – Clearing “Stuck” Requests

When working with Okta Identity Governance (OIG) Access Requests, you may find a request in a “stuck” state, where you can’t complete a step or the request doesn’t automatically close when done. Perhaps you’re testing a new Request Type and missed a step or have something misconfigured when you tested it. As an administrator you…

OIG Access Requests – Where Do I Assign Teams?

A common concern from a new Okta Identity Governance (OIG) Access Requests deployment is “I can’t see the Application or Group list when building a Request Type”. The most common cause is the assignment of Teams. Teams are the access control mechanism built into OIG Access Requests. They control who can create and own Request…

OIG Access Requests – Understanding User Grouping

Understanding user grouping mechanisms in the Okta Identity Governance (OIG) Access Requests mechanism is important to building and running access request flows. It can be confusing and this article aims to address the confusion. Note that OIG Access Requests is the old atSpoke product. The term “Okta” in this article refers to the Okta Identity…

Loading…

Something went wrong. Please refresh the page and/or try again.