-
Notifications
You must be signed in to change notification settings - Fork 301
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
SaaS Permissions API deployment script run.sh fails with errors #257
Comments
Thank you @ScottStefanich. Will try and see if we can repo this. I did test the install a week ago w/o running in to this issue. Only change since then is Azure CLI 2.55 -> 2.56. |
Did you try and install the Amin Service API before installing the Permissions API? I looks like the error has to do with the script not being able to download the output deployment parameters from an earlier deployment. |
Running the SaaS.Admin deployment script results in the same two errors (MSAL token cache and Identity Bicep deployment output parameters). |
The deployment named 'IdentityFoundationDeployment' successfully completed. The deployment Output has the following parameters,
@1iveowl, can you confirm the SaaS Administration Service API deployment script attempts to retrieve these parameters? |
I want to report this other error. but first few observation notes:
The solution for this, was replacing |
I restarted the procedure with a new Entra ID tenant and updated the following,
The Identity Provider deployment script completed without errors on the first try. The Permissions API deployment script encountered the same error,
|
I successfully deployed Identity Foundation Services and m attempting to run the SaaS Permissions API deployment script.
Running the script fails with the following results,
I tried logging into the Azure CLI with
az login --use-device-code
and setting the subscription withaz account set -s subscriptionId
.I'm using Windows 11, WSL 2, Azure CLI 2.56.0, and GitHub CLI 2.41.0.
The text was updated successfully, but these errors were encountered: