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
{{ message }}
This repository has been archived by the owner on May 3, 2024. It is now read-only.
- [ ] 1-1) Sign-in with Azure AD - [ ] 1-2) Sign-in with Azure AD B2C - [ ] 2-1) Acquire a Token and call Microsoft Graph - [X] 3-1) Protect and call a web API on Azure AD - [ ] 3-2) Protect and call a web API on Azure AD B2C - [ ] 4-1) Deploy to Azure Storage and App Service - [ ] 4-2) Deploy to Azure Static App Service - [ ] 5-1) Call a web API using App Roles - [ ] 5-2) Call a web API using Security Groups - [ ] 6-1) Call Microsoft Graph using on-behalf-of flow - [ ] 6-3) Call a web API using Conditional Access Auth Context - [ ] 6-4) Sign-in with Hybrid SPA flow
You need only follow the instructions. Just don't use any existing registrations that you already created because you probably already own them. When trying to add a permission in Step 7 of "Register the client app (msal-react-spa)" . The list under "My APIs" is BLANK.
Any log messages given by the failure
n/a
Expected/desired behavior
When trying to add permissions to the "msal-react-spa", the "My APIs" list should contain "msal-node-api" application.
Library version
n/a
Browser and version
Chrome, Edge, Firefox, Safari? Chrome, but doesn't matter in this case.
Mention any other details that might be useful
The fix is to go to the "msal-node-api" application and add yourself as an owner of that api registration. Afterwards, in the "msal-react-spa" the list of "My APIs" will contain the "msal-node-api" application.
The text was updated successfully, but these errors were encountered:
Issue
This issue is for the sample
This issue is for a
Minimal steps to reproduce
Any log messages given by the failure
Expected/desired behavior
Library version
Browser and version
Mention any other details that might be useful
The text was updated successfully, but these errors were encountered: