-
Notifications
You must be signed in to change notification settings - Fork 2k
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
[BUG] Cannot configure "azure" authorization client #30354
Comments
Hi @sgraca thank you for reaching out to us via this GitHub issue. Someone from the Azure Spring team will follow up with you shortly. |
Thanks @joshfree for helping triage it and @chenrujun could you help to take a look? |
Hi, @sgraca Thanks for reaching out. I can't reproduce the problem by this sample.
No. For Enum type. Could you please debug your code, and check the actual value of |
Hi @chenrujun Thanks for looking into this. This might be related to the Spring version then. I'm using Spring Boot 2.7.1 with Spring Security 5.7.2. In this version The instance that is obtained from the configuration properties is not the same as the one defined as the constant in the class itself as it's created by calling the constructor with the value specified in the configuration. The values are the same and |
Thanks! |
Describe the bug
In Spring Boot Starter for Azure, when the application is configured as
web_application_and_resource_server
it's not possible to configure scopes forazure
authorization client.Exception or Stack Trace
To Reproduce
Include following dependencies in a Spring Boot application:
Create a minimal application
Add configuration properties in
application.yml
Code Snippet
Given in the previous section.
Expected behavior
Application starts without errors.
Setup (please complete the following information):
Additional context
The issue seems to be caused by invalid value comparison in this line where the
grantType
property is compared by reference instead of usingequals
.Information Checklist
Kindly make sure that you have added all the following information above and checkoff the required fields otherwise we will treat the issuer as an incomplete report
The text was updated successfully, but these errors were encountered: