<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
0D54z00008tarQHCAYOkta Classic EngineUniversal DirectoryAnswered2023-07-12T23:28:48.000Z2023-03-09T20:10:50.000Z2023-03-10T18:37:50.000Z
  • User16594883467582706479 (Customer Support Online Experience)

    Hi, @JackC.72213 (Customer)​ 

     

    Thank you for posting on our Community page!

     

    Can you clarify if the request is made by an Admin, an app, or an end-user?

     

    https://developer.okta.com/docs/reference/api/myaccount/#update-my-user-profile and https://developer.okta.com/docs/reference/api/users/#update-current-user-s-profile would be the two guides to follow for end-users

     

    If app/admin is making the request, check their permissions.

    If end-user, make sure you use the right scopes/endpoints that were designed for use by end-users.

     

    Furthermore, I would advise to leverage the Okta Developer forums for this type of questions and take advantage of their expertise.

    https://devforum.okta.com/

     

    Thank you for reaching out to our Community and have a great day!

     

    _____________________________________________________________________________

    Community members help others by clicking Like or Select as Best on responses. Try it today.

    _____________________________________________________________________________

    Expand Post
  • JackC.72213 (Customer)

    This turned out to be a simple misconfiguration. The scope was granted in Okta but wasn't being requested on the client side so the token did not have the scope needed to perform the action.

This question is closed.
Loading
Application scope / custom attributes.