An Azure service that provides hosted, universal storage for Azure app configurations.
WIF still requires client secret
I set up WIF (GCP -> Azure authentication) with a federated credential, enabled “Allow public client flows”, and are using urn:ietf:params:oauth:grant-type:jwt-bearer, but Azure AD still requires a client_secret.
Here's the Correlation ID: 079b7a59-1d58-4467-bf44-e4ece63ce5ed and Trace ID: 'e034c167-9fb3-4afc-9b15-c9cf7e161200' from the latest error.
Can you please check for the application in question (gcp-azure-connector, or ID 5e042850-28d3-4f19-b4de-6b9936c08041) on why it still requires client_secret for WIF auth?
e.g. internal tenant policies, permission logs, or propagation issues that might be blocking WIF from working without client secret
Azure App Configuration
1 answer
Sort by: Most helpful
-
Deleted
This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.
5 deleted comments
Comments have been turned off. Learn more