If you’ve seen a demonstration of Okta Identity Governance (OIG) Access Requests, you have probably seen the machine learning (AI) capability when requesting access in Slack or Microsoft Teams. You ask for access to something, and the AI will try to determine the best request type to present. It learns over time, so that terms the business uses are readily translated to terms that IT uses.
Did you know that capability is also available in the Web user interface for OIG Access Requests? No? Read on.
If leveraging the OIG Access Requests WebUI, you are presented with a tiled view of request types (accesses you can request) on the App Catalog page.
At the top of the App Catalog page is a search box that will leverage the AI capabilities in the same way the the Slack/Microsoft Teams do (in-fact all three interfaces are using the same capability provided by Access Requests, its not something baked into each interface). Note that the search box under the App Catalog heading will just search through titles, not use the AI engine.
Typing something like “I need access to <blah>” will trigger the AI. It will evaluate whatever you type into the field, so you could type in just the name of the access you think you want.
In the example above it has presented the “Carpark Access (Until a Date)” request as it’s the one I use most often when demonstrating OIG. But I also have the pull-down list of all request types available to me.
Typing a string into the Search requestTypes field above the list will reduce the list to those matching what I type.
In this case typing “Carpark” will reduce the list to those with “Carpark” in the title. If you have used the Slack/Microsoft Teams integration you will see it’s the same user experience.
This mechanism makes it a lot easier to find a request when you have many requests exposed in the WebUI, particularly if a naming standard has been applied to request types.