-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
SAML connector - PANIC: nil pointer dereference exception #1757
Comments
Doing some more digging into this, the ADFS is sending the following status:
The request still shows dex config for saml connector:
SAML request:
|
We might have solved one problem, but we're still getting the panic from DEX:
Even with this response, the DEX is panicing:
|
Seems like we finally got something going where the saml status was successful but the data returned was encrypted. The problem is that the response, even encrypted, throws a panic. Is the SAML connector like...beta? So we're getting an encrypted payload, but since there is only one certificate for transport, it isn't immediately obvious on how to set up the adfs to encrypt the transport but to not encrypt the payload. If someone could help with that, that would be great! |
I've got very similar issue. |
@notjames
Did you solve this issue? +) config which I use
|
I no longer work for them but no, I never resolved that issue. However, we use SAML2 with dex at my current employer and it works so my assumption (though I don't have time to check right now) is likely a misconfiguration of the SAML IDP? Not 100% sure. |
I solved this issue, But still I don't know what is the exact reason. What I did:
Just my assumption, maybe dex could not find out CA file or could not use CA file properly...? |
@GRuuuuu I do not recommend keeping this configuration in production, it is very important that you validate the response signature. You can consider my example below, it worked on AWS SSO.
In your IDP, you also need to configure the following User attribute in the application | Maps to this string value | Format the caData value must be the content of the certificate in base64 on a single line I ended up preferring to customize the entityIssuer but you can use the callback url itself as long as you configure it in your IdP as well, usually it's the audience |
I'm attempting to set up a SAML2 connector in a k8s cluster for one of our internal environments. While testing this saml setup, the following nil pointer exception happens on every request:
version 2.23.0
version 2.24.0
The following is our SAML connector config, which is not the only connector we use, but it's the one that's relevant for now:
When attempting to test the authentication, the following happens:
https://dex-ad.<domain>/callback
dex logs show output from above.
The text was updated successfully, but these errors were encountered: