Skip to content
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

LDAP Client x509 Certificate Authentication #3

Open
precurse opened this issue Mar 15, 2019 · 3 comments
Open

LDAP Client x509 Certificate Authentication #3

precurse opened this issue Mar 15, 2019 · 3 comments

Comments

@precurse
Copy link

Google announced their LDAP service: https://support.google.com/cloudidentity/answer/9089736 and we wanted to see if we could get it working for our users.

However, it requires a client certificate to authenticate to the server, which SimpleSAMLphp doesn't support: https://simplesamlphp.org/docs/stable/ldap:ldap . It seems to only support username/password for client authentication.

It would be nice to be able to support client cert/key for authentication in addition to username/password. OpenLDAP supports it using TLS_CERT and TLS_KEY.

It seems that support for this may have only come into PHP in version 7.1: http://php.net/manual/en/function.ldap-set-option.php

@tvdijen
Copy link
Member

tvdijen commented Mar 8, 2022

Hi @precurse ! I've just released v2.0.0-rc1 of this module which is a complete rewrite. It's based on symfony/ldap and allows you to pass connection options supported by the symfony package.. I think what you would need is this, am I right? You should now be able to pass them in the options array of the ldap-authsource.

If this is indeed what you're after, I invite you to run a few tests with this module. You have to use SSP v2.0.0-beta.8 + v2.0.0-rc1 of this module. Your feedback is highly appreciated.

@precurse
Copy link
Author

Thanks @tvdijen. Oh wow, I totally forgot I had this ticket open :)

I'm no longer in a role that would let me test this unfortunately, but from quickly eyeballing the source it looks right. Thanks for the follow up.

I'll close the ticket, but feel free to re-open if you want someone else to confirm if this works.

Cheers!

@tvdijen tvdijen reopened this Mar 28, 2022
@tvdijen
Copy link
Member

tvdijen commented Mar 28, 2022

Sorry for taking so long...
I suspect this to become a more common use-case, so I'm keeping this open for now. Thanks for getting back!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants