-
Notifications
You must be signed in to change notification settings - Fork 136
Description
Before filing this issue, please ensure you're using the latest CLI by running swa --version
and comparing to the latest version on npm.
Are you accessing the CLI from the default port :4280
?
- No, I am using a different port number (
--port
) and accessing the CLI from that port - Yes, I am accessing the CLI from port
:4280
Make sure you are accessing the URL printed in the console when running
swa start
!
ℹ️ NOTE: Make sure to enable debug logs when running any swa
commands using --verbose=silly
Describe the bug
When using Entra ID (AAD) for SWA custom authentication, you must specify the format https://login.microsoftonline.com/<TENANT_ID>/v2.0
as openIdIssuer
.
However, as far as I have tested, the SWA CLI emulation does not work correctly unless you specify the format https://login.microsoftonline.com/<TENANT_ID>/oauth2/v2.0
.
I think it is necessary to make the format of the openIdIssuer
accepted by the SWA CLI consistent with that of SWA Cloud.
To Reproduce
Steps to reproduce the behavior:
- Go to '...'
- Type in command 'swa ...'
- Click on '...'
- Scroll down to '...'
- See error
Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):
- OS: [e.g. iOS]
- Version [e.g. 22]
Additional context
Add any other context about the problem here.