I'm trying to use the interactive authorization API to generate a token to use to connect to an azure resource from my desktop application. The client id that I am using in the request has a local loopback url registered that includes a path (http://localhost:8000/login). Unfortunately though, the logic in AuthorizationResponseHandler explicitly checks that the URL is "/" and so my callback with a path "/login" is silently ignored. The authorization call then times out without a token being generated.
It looks to me from this article (https://learn.microsoft.com/en-us/azure/active-directory/develop/reply-url#localhost-exceptions) that local URLs with paths are valid so is this just a bug with the msal implementation ? I'm assuming that a fix would need the valid URL to be passed into the response handler when it is instantiated.
I am using 1.8.0 of the azure-identity SDK.
I can see that my application correctly launches the browser, authenticates using my local credentials and the browser successfully posts the token back to the http server exposed by the msal API. (I have checked using the browser debug view and my java debugger).
