Skip to content
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] AzureArcManagedIdentitySource looking for WWW-Authenticate response header while agent returns Www-Authenticate #884

Closed
blancqua opened this issue Dec 4, 2024 · 2 comments · Fixed by #885
Labels
Bug Something isn't working, needs an investigation and a fix confidential-client For issues related to confidential client apps P2 Normal priority items, should be done after P1

Comments

@blancqua
Copy link
Contributor

blancqua commented Dec 4, 2024

Library version used

1.17.2

Java version

21

Scenario

Other - please specify

Is this a new or an existing app?

This is a new app or experiment

Issue description and reproduction steps

I am trying to log in my application running on an Azure Arc enabled Ubuntu 24.04 server. In the class AzureArcManagedIdentitySource, there is a check for existence of the WWW-Authenticate header. However, my agent returns the header without capitals: Www-Authenticate (see image).

image

I see the code used to check for Www-Authenticate but this changed with this commit: 68bba51

Relevant code snippets

No response

Expected behavior

I expect my application to log in via the Azure Arc Managed Identity.

Identity provider

Microsoft Entra ID (Work and School accounts and Personal Microsoft accounts)

Regression

1.15.0

Solution and workarounds

I assume best option would be to make the check case-insensitive...

@blancqua blancqua added needs attention Automatically used when an issue is created through an issue template untriaged Automatically used when an issue is created through an issue template labels Dec 4, 2024
@blancqua
Copy link
Contributor Author

blancqua commented Dec 4, 2024

#885

@bgavrilMS bgavrilMS added Bug Something isn't working, needs an investigation and a fix P2 Normal priority items, should be done after P1 confidential-client For issues related to confidential client apps and removed needs attention Automatically used when an issue is created through an issue template untriaged Automatically used when an issue is created through an issue template labels Dec 5, 2024
@Avery-Dunn
Copy link
Collaborator

The fix for this was released as part of 1.18.0, thanks again for making the fix!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug Something isn't working, needs an investigation and a fix confidential-client For issues related to confidential client apps P2 Normal priority items, should be done after P1
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants