FAQ: Rogue Accounts Report Planned End of Life (EOL)
Okta Classic Engine
Insights and Reporting
Okta Identity Engine
Administration

Content

This article has extended details covering the end-of-life for the Rogue Accounts Report feature.
 

Why is this feature being removed?

Okta is removing this feature due to very low usage, high maintenance costs, and the availability of custom solutions based on existing Okta APIs.


What happens to existing reports?

There is no impact on existing reports because customers download the report after creating one. Okta does not provide a link to the downloaded report in the UI, nor does It have access to the report already downloaded by the customer.


What alternative solutions are available?

In order to minimize end-user disruption, affected customers can use the following two approaches:


PowerShell scripts written by Okta’s PS/BD teams

  • Okta provides a PowerShell module with a number of handy commands to pull data from the Okta org. 

  1. This module can be found in mbegan / Okta-PSModule Public.
  2. There are already some example scripts mentioned in the mbegan / Okta-Scripts, which use the Okta-PSModule.
  3. If there are any questions, please ask using the GitHub link via an issue.
  • To fetch the list of users assigned to an app, one has to use the oktaGetUsersbyAppID command.

    • This command uses the same Apps API which Okta Support team was using earlier. For more information, please check the Applications documentation. The nice thing is that the command already takes pagination and rate limits into account. So, no need to run the command N times and create N different output files!

  • Now, the oktaGetUsersbyAppID command will produce the output as a set of PowerShell objects. To convert these objects to a CSV, one can use the PowerShell native cmdlet called export-csv. 

  1. Take the data and store it in a hash that makes sense, then kick it to the export-csv command.
  2. Since Okta's JSON object for an app or appUser is a little complex, it will not naturally export in an easy-to-read format. So, one just needs to figure out which fields were of interest, stuff them into a collection, and feed that collection to the export-csv.



Okta Apps API + custom code

Affected customers can use the Apps API to fetch the list of users assigned to an app in Okta. They can then write some custom code to find the list of users assigned to the app in the app itself. This will help the customer gather the data required to identify any discrepancies.

Recommended content

No recommended content found...