Solved the problem myself and I would be proud except it was a ridiculous mistake. I was using the Client Secret Name instead of the Client Secret Value…I’ve setup so much of these I wasn’t even catching the mistake. Must be tired…but maybe this will help someone else.
Related topics
| Topic | Replies | Views | Activity | |
|---|---|---|---|---|
| AzureAD OIDC Configuration | 10 | 17998 | December 4, 2020 | |
| Cannot Connect Keycloack with Azure AD as identity provider | 3 | 7168 | June 22, 2021 | |
| Azure IdP sometimes doesn't work (failed to make identity provider oauth callback) | 1 | 915 | March 23, 2023 | |
| [HELP] Azure AD Identity Provider – “Unexpected error when authenticating” + “No access_token from server” | 0 | 261 | June 17, 2025 | |
| Keycloak 26 + Azure AD B2C Integration – “No access_token from server” error | 1 | 133 | December 22, 2025 |