azure-saas
azure-saas copied to clipboard
Azure
run.sh fails to authenticate
When running the "run.sh" script the script fails after logging into the Azure tenent
Login to Azure
Log into you Azure tenant Setting account subscription to ""
You are logged in to tenant: ""
Critical error
Initilization failed cp: cannot stat '/asdk/src/Saas.Identity/Saas.IdentityProvider/deployment/config/certificate-policy.json': No such file or directory
Configuration Validation
Validating Initial Configuration Settings... All required initial configuration settings exist.
Cleaning up
Starting cleaning up...
Deleting locally stored service principal credentials. Deleting service principal credentials using user 'null' No known service principal to delete. Service principal credentials have been removed locally and in Azure AD. User context for null have been deleted. User context for null have been deleted. Clean up has completed.
Backup to Azure Blob Storage
Backing up logs in '/asdk/src/Saas.Identity/Saas.IdentityProvider/deployment/log/2023-10-20--17-47-03' to Azure Blob Storage 'null/null'. ERROR: Operation returned an invalid status 'Server failed to authenticate the request. Please refer to the information in the www-authenticate header.' ErrorCode:InvalidAuthenticationInfo
Deployment script completion
Identity Foundation deployed with errors. Sometimes this is due to an error happening with the Azure Resource Manager. Try running the script once more to see if it continues past the point of failure.
Looks like you're not logged into a tenant. I just tested the install and it worked, so nothing seems to be broken at the moment.
I have exact same issue I logged into my tenant / subscription and do multiple az logins and the issue still persist. @1iveowl you made any progress on this ?
This should now have been addressed by #253.
Can you confirm, @nbelingheri?
Hi @nbelingheri , checked the PR https://github.com/Azure/azure-saas/pull/253 Which version of AZ cli can be used to get this fix I am using AZ cli version 2.61.0 but still facing the issue Can u pls guide on this resolution
Hi @nbelingheri , I got the root cause for my scenario. It is resolved with the help of below documentation, thanks