Open ID Connect Authentication Attempt Results in Connection Failure

[Mike-E-angelo]

I have been using the Open ID Connect authenticator and it works perfectly with https://demo.duendesoftware.com. However, I have been having trouble when attempting to connect to an Open ID Connect server on localhost.

I am able to connect to the discovery document just fine when I access it directly in the browser. However, when attempting to login via the Uno application on Android, I get the following error:

System.InvalidOperationException: Command 'Login' failed when executing command with '-null-'.
 ---> System.InvalidOperationException: Error loading discovery document: Error connecting to https://localhost:7275/.well-known/openid-configuration. Connection failure.
 ---> System.Net.Http.HttpRequestException: Connection failure
 ---> Java.Net.ConnectException: Failed to connect to localhost/127.0.0.1:7275
   at void Java.Interop.JniEnvironment+InstanceMethods.CallVoidMethod(JniObjectReference instance, JniMethodInfo method, JniArgumentValue* args) in /Users/runner/work/1/s/xamarin-android/external/Java.Interop/src/Java.Interop/obj/Release/net8.0/JniEnvironment.g.cs:line 20371
   at void Java.Interop.JniPeerMembers+JniInstanceMethods.InvokeAbstractVoidMethod(string encodedMember, IJavaPeerable self, JniArgumentValue* parameters) in /Users/runner/work/1/s/xamarin-android/external/Java.Interop/src/Java.Interop/Java.Interop/JniPeerMembers.JniInstanceMethods_Invoke.cs:line 47
   at void Javax.Net.Ssl.HttpsURLConnectionInvoker.Connect() in /Users/runner/work/1/s/xamarin-android/src/Mono.Android/obj/Release/net9.0/android-35/mcw/Javax.Net.Ssl.HttpsURLConnection.cs:line 443
   at Task Xamarin.Android.Net.AndroidMessageHandler.ConnectAsync(HttpURLConnection httpConnection, CancellationToken ct)+() => { } [0] in /Users/runner/work/1/s/xamarin-android/src/Mono.Android/Xamarin.Android.Net/AndroidMessageHandler.cs:line 567
  --- End of managed Java.Net.ConnectException stack trace ---

I've also tried 127.0.0.1:

System.InvalidOperationException: Command 'Login' failed when executing command with '-null-'.
 ---> System.InvalidOperationException: Error loading discovery document: Error connecting to https://127.0.0.1:7275/.well-known/openid-configuration. Connection failure.
 ---> System.Net.Http.HttpRequestException: Connection failure
 ---> Java.Net.ConnectException: Failed to connect to /127.0.0.1:7275
   at void Java.Interop.JniEnvironment+InstanceMethods.CallVoidMethod(JniObjectReference instance, JniMethodInfo method, JniArgumentValue* args) in /Users/runner/work/1/s/xamarin-android/external/Java.Interop/src/Java.Interop/obj/Release/net8.0/JniEnvironment.g.cs:line 20371
   at void Java.Interop.JniPeerMembers+JniInstanceMethods.InvokeAbstractVoidMethod(string encodedMember, IJavaPeerable self, JniArgumentValue* parameters) in /Users/runner/work/1/s/xamarin-android/external/Java.Interop/src/Java.Interop/Java.Interop/JniPeerMembers.JniInstanceMethods_Invoke.cs:line 47
   at void Javax.Net.Ssl.HttpsURLConnectionInvoker.Connect() in /Users/runner/work/1/s/xamarin-android/src/Mono.Android/obj/Release/net9.0/android-35/mcw/Javax.Net.Ssl.HttpsURLConnection.cs:line 443
   at Task Xamarin.Android.Net.AndroidMessageHandler.ConnectAsync(HttpURLConnection httpConnection, CancellationToken ct)+() => { } [0] in /Users/runner/work/1/s/xamarin-android/src/Mono.Android/Xamarin.Android.Net/AndroidMessageHandler.cs:line 567
  --- End of managed Java.Net.ConnectException stack trace ---

I've done some searching around this and found a possible emulator port configuration discussed here:
https://stackoverflow.com/questions/6760585/accessing-localhostport-from-android-emulator

However, I have tried all the suggestions and it doesn't seem what I am encountering. Most notably, there doesn't seem to be a Connection Failure message found in this the reported messages.

Any assistance and pointers around this would be appreciated.

[jeromelaban]

Thanks for the question.

127.0.0.1 is for the device itself, are you running a web server on the device for the port in question? Or is it running on your host machine?

[Mike-E-angelo]

Hi @jeromelaban thank you for your assistance here. 🙏 This has been a tricky one for me as I am completely new to all of this, having had my nose in Blazor for the past 5 years, where an emulator is not a consideration.

After several further attempts, I was able to determine the issue to be the that the authority should be http://10.0.2.2:5275. However, now the Open ID Connect client is having problems with the http:// and saying that HTTPS is required.

There is a policy on the OidcClientOptions and I have tried to set the following after the IHost is created with little avail:

var snapshot = host.Services.GetRequiredService<IOptionsSnapshot<OidcClientOptions>>();
		var options  = snapshot.Value;
		options.Policy.Discovery.RequireHttps = false;

I am wondering if there is a better/preferred way to assign this value. It is also worth noting that I have I tried to debug and place breakpoints in the Open ID Connect code but am running into this problem here. So yeah, all sorts of challenges I am adjusting to here. 😁

[Mike-E-angelo]

Going to mark this as resolved as this appears to be working now with the URL, now I need to access the policy which I have created a thread here: #19178

[carldebilly]

The error message you are getting is suggesting you're using a local server as the Authority (the IAM) server, the server used to login. The Oidc library will seek for /.well-known/openid-configuration on the authority url to get details about keys, endpoints and other settings. This should be on the server used to authenticate users, not on localhost on a mobile device.

[Mike-E-angelo]

Thank you for your reply. It is indeed searching for the localhost for the document http://10.0.2.2:5275/.well-known/openid-configuration. However, I am getting a policy error System.InvalidOperationException: Error loading discovery document: Error connecting to http://10.0.2.2:5275/.well-known/openid-configuration. HTTPS required. I have attempted to modify the policy as described here with little luck. If you have any guidance I would greatly appreciate it. 🙏