<iframe src="https://www.googletagmanager.com/ns.html?id=GTM-M74D8PB" height="0" width="0" style="display:none;visibility:hidden">
Loading
Skip to NavigationSkip to Main Content
0D54z00006z2hmWCAQOkta Classic EngineAdministrationAnswered2025-04-22T09:00:20.000Z2021-05-26T16:04:58.000Z2021-05-30T11:00:56.000Z

iv35t (iv35t) asked a question.

Okta logs saving my name as actor instead of the authenticated user's name

When accessing the logs created from any action using the Okta API, the logs are showing my name as actor instead of the authenticated user's name. I'm assuming this is because I created the API Token.

Is there a way to change this behavior?

What happens if my user is no longer in the system?


AishwaryaM.78833 likes this.
  • User15905896560008893663 (Vendor Management)

    Hi Jormary,

     

    You are correct. The reason you see your name is because the actions are done via your API token. You could create a super admin with a different name and reauthenticate the application using that user, generating a new token. Then the username will be the system admin.

    As for the second question, when a user is removed, his tokens are removed as well.

    Expand Post
  • ydce6 (ydce6)

    We create service accounts for every key as if you do it n term all break

    then you can name the svc account to be obvious and audit it on the reg in ad.

    also suggest rarely using a superadmin as an api as thats a god key you are likely giving another app admin

    tgat means if they mess ip your okta is jacked

    remember least privilege!! 🙂

    they key keeps the access the user has so create svc account with what it needs and api admin, log in as that user get key remover api admin access then give key to user.

    join Facebook okta help tips and tricks for a growing community

    Expand Post
This question is closed.
Loading
Okta logs saving my name as actor instead of the authenticated user's name