Introduction

It might happen that, when you click on the login button, you receive an error 500 "Internal Server Error".

This is because something is missing in your configuration. Let's see how to troubleshoot that.

Troubleshooting

The main thing you have to do is take a look at the conduktor-console container logs. In these logs, you might see:

java.lang.NullPointerException: Cannot invoke "com.nimbusds.openid.connect.sdk.op.OIDCProviderMetadata.getCodeChallengeMethods()" because "opMetadataResolver" is null

This means that Console hasn't been able to talk to your identity provider, because something in the middle is preventing it to. As we couldn't retrieve the context, one of the mandatory fields is null, so we are printing this error.

Solution

As explained above, something is preventing Console speaking to your identity provider. This is probably an HTTP proxy.

In order for Console to know about this HTTP proxy, you have to configure it in the conduktor-console environment variables, as detailed in this documentation.

Then, you can try again and the login should be working!