You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
If you are interested in working on this issue or have submitted a pull request, please leave a comment
Service Used
Metadata Service's loginEndpoint
API Versions Used
2022-09-01
Description
In the usssec Azure cloud, the loginEndpoint in the response from /metadata/endpoints?api-version=2022-09-01 includes a trailing slash that the SDK and tests do not expect. This causes sdk/auth's ClientSecretAuthorizer and ClientCertificateAuthorizer to use a double-slash after appending their own leading slash for the required endpoint. Thus the terraform provider can not successfully log in with OIDC.
#1148 is a potential solution: by using the standard library's url.JoinPath, the SDK will clean unexpected double slashes and use a correct URL irrespective of the structure of the loginEndpoint.
References
No response
The text was updated successfully, but these errors were encountered:
Is there an existing issue for this?
Community Note
Service Used
Metadata Service's loginEndpoint
API Versions Used
2022-09-01
Description
In the
usssec
Azure cloud, theloginEndpoint
in the response from/metadata/endpoints?api-version=2022-09-01
includes a trailing slash that the SDK and tests do not expect. This causes sdk/auth'sClientSecretAuthorizer
andClientCertificateAuthorizer
to use a double-slash after appending their own leading slash for the required endpoint. Thus the terraform provider can not successfully log in with OIDC.#1148 is a potential solution: by using the standard library's
url.JoinPath
, the SDK will clean unexpected double slashes and use a correct URL irrespective of the structure of theloginEndpoint
.References
No response
The text was updated successfully, but these errors were encountered: