AngeloA.78288 (Customer) asked a question.
We would like to disable access to certain applications if they are not used for 90 days, to automate least privilege. Is this achievable with a workflow?
@AngeloA.78288 (Customer) -- It depends on if there is an attribute holding this information that can be queried by API or not. If the answer is yes then Workflows can automate this use case. Otherwise, no.
In Okta, to the best of my knowledge most/all apps do not have a lastAccessed type attribute. What this means is you could potentially do a System Log look back. The System Log is queryable for the last 90 days. So something like this: eventType | Result | App ID | User ID
eventType eq "user.authentication.sso" and outcome.result eq "SUCCESS" and target.id eq "0oaj0yraqnVwWwFiG5d7" and target.id eq "0uaj0yrasxdDgZjAa5d7"
If the returned results are "not empty" then at least one hit was found within 90 days for that user. You could use something like the above to iterate all of the users in the environment that are assigned the application and remove/disable their access. This would be a "Baseline"
Your "Going forward" however would require you to create/update a custom attribute containing their last login (ISO 8601 format preferred) to that app (or those apps). Then you could create a scheduled flow that queries against the attribute looking for users that are outside of the time range.
So your use case is feasible. There just isn't a real "built-in" method to do it.
We use cookies to provide the best website experience and to help understand marketing efforts. We may also share data with ad partners to reach potential customers across the web. To learn more, visit our Privacy Policy. Click here for Your Privacy Choices. You may also opt out of this sharing by signaling your preference via GPC, applicable only to the browser signaling the opt-out.
More information
These cookies are necessary for the website to function and cannot be switched off in our systems. They are usually only set in response to actions made by you which amount to a request for services, such as setting your privacy preferences, logging in or filling in forms. You can set your browser to block or alert you about these cookies, but some parts of the site will not then work. These cookies do not store any personally identifiable information.
These cookies enable the website to provide enhanced functionality and personalisation. They may be set by us or by third party providers whose services we have added to our pages. If you do not allow these cookies then some or all of these services may not function properly.
These cookies allow us to count visits and traffic sources so we can measure and improve the performance of our site. They help us to know which pages are the most and least popular and see how visitors move around the site. All information these cookies collect is aggregated and therefore anonymous. If you do not allow these cookies we will not know when you have visited our site, and will not be able to monitor its performance.
These cookies may be set through our site by our advertising partners. They may be used by those companies to build a profile of your interests and show you relevant adverts on other sites. They do not store directly personal information, but are based on uniquely identifying your browser and internet device. If you do not allow these cookies, you will experience less targeted advertising.
Select All
We use cookies to provide the best website experience and to help understand marketing efforts. We may also share data with ad partners to reach potential customers across the web. To learn more, visit our Privacy Policy. Click here for Your Privacy Choices. You may also opt out of this sharing by signaling your preference via GPC, applicable only to the browser signaling the opt-out.
More information
These cookies are necessary for the website to function and cannot be switched off in our systems. They are usually only set in response to actions made by you which amount to a request for services, such as setting your privacy preferences, logging in or filling in forms. You can set your browser to block or alert you about these cookies, but some parts of the site will not then work. These cookies do not store any personally identifiable information.
These cookies enable the website to provide enhanced functionality and personalisation. They may be set by us or by third party providers whose services we have added to our pages. If you do not allow these cookies then some or all of these services may not function properly.
These cookies allow us to count visits and traffic sources so we can measure and improve the performance of our site. They help us to know which pages are the most and least popular and see how visitors move around the site. All information these cookies collect is aggregated and therefore anonymous. If you do not allow these cookies we will not know when you have visited our site, and will not be able to monitor its performance.
These cookies may be set through our site by our advertising partners. They may be used by those companies to build a profile of your interests and show you relevant adverts on other sites. They do not store directly personal information, but are based on uniquely identifying your browser and internet device. If you do not allow these cookies, you will experience less targeted advertising.
Select All
@AngeloA.78288 (Customer) -- It depends on if there is an attribute holding this information that can be queried by API or not. If the answer is yes then Workflows can automate this use case. Otherwise, no.
In Okta, to the best of my knowledge most/all apps do not have a lastAccessed type attribute. What this means is you could potentially do a System Log look back. The System Log is queryable for the last 90 days. So something like this: eventType | Result | App ID | User ID
eventType eq "user.authentication.sso" and outcome.result eq "SUCCESS" and target.id eq "0oaj0yraqnVwWwFiG5d7" and target.id eq "0uaj0yrasxdDgZjAa5d7"
If the returned results are "not empty" then at least one hit was found within 90 days for that user. You could use something like the above to iterate all of the users in the environment that are assigned the application and remove/disable their access. This would be a "Baseline"
Your "Going forward" however would require you to create/update a custom attribute containing their last login (ISO 8601 format preferred) to that app (or those apps). Then you could create a scheduled flow that queries against the attribute looking for users that are outside of the time range.
So your use case is feasible. There just isn't a real "built-in" method to do it.