Siddhi
Siddhi
When Global AAD is unavailable, it will cause timeout issue with AAD authentication of native cloud.
Adding Bogdan's comment from the Incident This is a good point. There are 2 issues here: 1. If instance discovery fails with error except "invalid_instance", MSAL should ignore it 2....
When Global AAD is unavailable, it will cause timeout issue with AAD authentication of native cloud.
This issue is fixed and the fix should be available in the next msal4j release.
When Global AAD is unavailable, it will cause timeout issue with AAD authentication of native cloud.
Released version 1.13.6 of the library to take care of this. Please reopen this if the issue persists.
@henrik-me can this issue be closed since we are not planning to add ROPC to confidential clients?
This makes sense Vinay! Feel free to create a PR for this.
The decision was to replace it with an in-house common library. I believe @Alanzimmer from the Azure Identity team was working on creating a common library that can be utilized...
@Avery-Dunn I believe we are already using sonar linting in msal4j. Is sonarcloud still a thing?
That's a good suggestion. To add to the list, http://localhost/path works since it picks a random available port. The only format that does not work is when it contains both...
Quoting customer here - "Customer accepted the feedback, but came back with the following inputs: I think also it seems a very technical explanation that doesn’t really address the fundamental...
@MushyMiddle Thanks for bringing this up. Since many users are facing issues, we will prioritize getting this fixed.