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

Connecting a subdomain via LDAP to another subdomain #98

Open
Nikita-zeroBit opened this issue Jul 5, 2023 · 4 comments
Open

Connecting a subdomain via LDAP to another subdomain #98

Nikita-zeroBit opened this issue Jul 5, 2023 · 4 comments

Comments

@Nikita-zeroBit
Copy link

There is a FreeIPA root domain (test.lan) and 2 child domains (subtest.test.lan, subtest2.test.lan). Trust has been set up between domains between Kerberos domains:

  1. Trusted accounts have been created between subtest.test.lan and test.lan, and between subtest2.test.lan and test.lan. The entries were created via kadmin local.
  2. From the subtest2.test.lan domain, you can get the tgs of the subtest.test.lan domain.

but the connection via LDAP SASL GSSAPI does not occur and the error "SASL(-14): authorization failure: " appears
3. Do I need any additional actions to be able to perform bind LDAP SASL GSSAPI?
Maybe I need to do SASL mapping?
I set up a trust relationship according to the instructions https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/7/html/system-level_authentication_guide/using_trusts

@Nikita-zeroBit
Copy link
Author

Снимок экрана 2023-07-05 в 13 12 28
Снимок экрана 2023-07-05 в 13 13 04
Снимок экрана 2023-07-05 в 13 13 53

@abbra
Copy link
Owner

abbra commented Jul 5, 2023

This is not supported. I'm on vacation for next couple weeks and cannot dive into details, sorry. Please remind me closer to end of July....

@Nikita-zeroBit
Copy link
Author

Thank you for quick reply. Have a nice vacation!

@abbra
Copy link
Owner

abbra commented Jul 16, 2023

Users from a trusted domain will only be able to auth to LDAP if they map onto an ID override with their name in the 'Default trust view'. Basically, there is a mapping rule for SASL authorization in LDAP server configuration that maps an incoming (authenticated) Kerberos principal from SASL to an LDAP object (ID override). If that matches, LDAP bind will be mapped to this LDAP object and access to LDAP server will be granted with permissions available to that ID override. This works for any 'normal' principal from a trusted domain as long as you are able to define it in ID overrides, even without any actual overrides.

See https://freeipa.readthedocs.io/en/latest/designs/adtrust/admin-ipa-as-trusted-user.html for some details. For IPA-IPA trust this would rely on the fact that you have a trust object visible to ipa trust-find command and that SSSD on IPA server is able to resolve this principal. That is not currently possible for IPA-IPA trust as I haven't completed this work in my branch yet and there are few things to be fixed first at SSSD side too.

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