You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I’m trying to figure out the best, maintainable way to obtain and store an Azure AD access token so that developers can request it once and reuse it across multiple .http files or requests.
We’re using the standard v2.0 token endpoint: POST https://login.microsoftonline.com/{{tenantId}}/oauth2/v2.0/token
What is the recommended approach for:
requesting the token once,
securely storing/caching it (e.g., environment variables, scripts, httpyac hooks), and
reusing it across different requests without manually copying it every time?
Looking for best practices for development scenarios.
Thanks!
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
I’m trying to figure out the best, maintainable way to obtain and store an Azure AD access token so that developers can request it once and reuse it across multiple .http files or requests.
We’re using the standard v2.0 token endpoint:
POST https://login.microsoftonline.com/{{tenantId}}/oauth2/v2.0/tokenWhat is the recommended approach for:
requesting the token once,
securely storing/caching it (e.g., environment variables, scripts, httpyac hooks), and
reusing it across different requests without manually copying it every time?
Looking for best practices for development scenarios.
Thanks!
All reactions