<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
0D54z0000AE5VvPCQVOkta Classic EngineAPI Access ManagementAnswered2024-08-13T22:30:52.000Z2024-08-12T22:35:23.000Z2024-08-13T22:30:52.000Z

PrathameshP.29233 (CDK Global) asked a question.

Alternative to cookie based users/me API

Hello OKTA Community,

 

We are aiming to replace Okta users/me API call that relies on Okta domain cookie 'sid' and hence looking for an alternative API that we can use using Bearer (access) token. 

We went through the documentation (https://developer.okta.com/docs/reference/api/users/*get-user) but all mentioned APIs either need SSWS token or sid cookie, and that is not desirable in the design.  

 

We are specifically looking for these values in the API response -

 

a custom attribute in user profile)

last login date

 

Can you please suggest an API or alternative approach for this use case? 


  • User17157611498146715886 (Customer Support Online Community and Social Care)

    Hi @PrathameshP.29233 (CDK Global)​ , thank you for contacting Okta Community!

    I've reviewed our documentation for something relevant. It looks like your question is more appropriate for our dedicated Okta Developer Forum. I advise reaching out via devforum.okta.com  as they will have more insight into this topic. 

     

    While we'll do our best to answer your questions here, this medium is more inclined towards Okta's core products and features (non-developer work).

     

    Regards. 

    --

    Help others in the community by liking or hitting Select as Best if this response helped you.

     

     

    Expand Post
This question is closed.
Loading
Alternative to cookie based users/me API