Error: Not found: Resource not found: {redacted} (AppLink)
jboyle-ld opened this issue · 10 comments
Hello,
I'm receiving the following error when attempting to "export apps" using Rockstar:
"Error: Not found: Resource not found: {redacted} (AppLink)"
I have not been able to find the AppLink ID specified, either in the page source of the Applications page in the Okta admin UI, or when listing all Apps via the API.
GET {{url}}/api/v1/apps, does not return any errors.
If you can help track down this issue I would appreciate it.
Best,
J
I get this error, too. It's not a rockstar error. The Okta API itself is returning it.
You can open the Chrome dev tools to see more info in the Console and Network tabs.
GET {{url}}/api/v1/apps, does not return any errors
If you have more than 1 page of apps (more than 20 apps), you'd need to paginate through all the pages. You can easily do this in rockstar using the API Explorer by clicking Next repeatedly, or Postman, or any other tool.
Thanks for the explanation! I feel like I did this in a previous environment (hundreds of apps) without issue, but my memory might be failing me.
According to this Okta support article, the number of results for the apps endpoint can be increased to a maximum of 200 with the "limit" variable. I've done that via postman and its throwing the same error so it looks like I'll have to reach out to Okta support to figure out why that is.
In the meantime, is there a way to export the results to csv, or at least concat the paginated results to a single json file, from the Rockstar API explorer?
copy/paste from the results table into Excel, you can try setting the url to /api/v1/apps?limit=200
but i think you're still going to get the same error.
i'd recommend opening a case with Okta Support and see if they can either fix your data or the API.
if they find/fix something, please respond here to help others.
Will do, thanks!
this might help, too /api/v1/apps?limit=200&filter=status eq "ACTIVE"
Okta support is still puzzling over our particular issue which appears to be specific to our tenant. In the interim, your solution does work to provide the results we need. Thanks for the recommendation!
Hey Gabriel,
Just solved the issue right now, there was a corrupt application configuration in our environment that was finally identified by Okta engineering, deleting it resolved the error. I'll close this issue out, thanks again for your help.
Best
J
I'm glad it worked. Can you provide any info (w/o details), on how they found/deleted it? They just looked in the log? It was an inactive app, right?
Yep, it was an inactive app. The api call was returning an error that contained an app link id and it looks like they were able to correlate that app link id (al.strLinkID) with an app instance name (ai.instance) by running a sql query. Once they were able to provide the name of the app, I was able to delete it manually from the admin console (we had several dozen inactive apps so it wasn't clear which was the culprit without that info).
It's also worth noting that the app instance was clearly corrupted, the tabs weren't rendering properly and actions like clicking on the assignments tab even threw an embedded 404 error before the page froze completely, but clicking on "Delete" worked and then I was able to make the same api call without issue.