Description of problem: When FreeIPA is configured with AD trust support, Kerberos tickets may also contain PAC which makes them bigger than usually expected (bigger than 2048 B) - 389-ds-base SASL layer does not accept that. # ipa-adtrust-install ... [11/19]: activating sidgen plugin and task [12/19]: activating extdom plugin [13/19]: configuring smbd to start on boot [14/19]: adding special DNS service records Unexpected error - see /var/log/ipaserver-install.log for details: NetworkError: cannot connect to 'ldapi://%2fvar%2frun%2fslapd-F19-AD-TEST.socket': # service dirsrv@F19-AD-TEST status Redirecting to /bin/systemctl status dirsrv dirsrv - 389 Directory Server F19-AD-TEST. Loaded: loaded (/usr/lib/systemd/system/dirsrv@.service; enabled) Active: active (running) since Wed 2013-03-20 15:54:11 CET; 47min ago Main PID: 16664 (ns-slapd) CGroup: name=systemd:/system/dirsrv@.service/F19-AD-TEST └─16664 /usr/sbin/ns-slapd -D /etc/dirsrv/slapd-F19-AD-TEST -i /var/run/dirsrv/slap... Mar 20 16:07:23 ipa.f19.ad.test ns-slapd[16664]: GSSAPI server step 1 Mar 20 16:07:23 ipa.f19.ad.test ns-slapd[16664]: GSSAPI server step 2 Mar 20 16:07:23 ipa.f19.ad.test ns-slapd[16664]: GSSAPI server step 3 Mar 20 16:41:26 ipa.f19.ad.test ns-slapd[16664]: GSSAPI server step 1 Mar 20 16:41:26 ipa.f19.ad.test ns-slapd[16664]: GSSAPI server step 2 Mar 20 16:41:26 ipa.f19.ad.test ns-slapd[16664]: GSSAPI server step 3 Mar 20 16:41:29 ipa.f19.ad.test ns-slapd[16664]: GSSAPI server step 1 Mar 20 16:41:29 ipa.f19.ad.test ns-slapd[16664]: GSSAPI server step 2 Mar 20 16:41:29 ipa.f19.ad.test ns-slapd[16664]: GSSAPI server step 3 Mar 20 16:41:30 ipa.f19.ad.test ns-slapd[16664]: encoded packet size too big (3014 > 2048) /var/log/dirsrv/slapd-F19-AD-TEST/errors: [20/Mar/2013:15:54:10 +0100] - slapd stopped. [20/Mar/2013:15:54:11 +0100] - 389-Directory/1.3.0.4 B2013.072.1657 starting up [20/Mar/2013:15:54:11 +0100] schema-compat-plugin - warning: no entries set up under cn=computers, cn=compat,dc=f19,dc=ad,dc=test [20/Mar/2013:15:54:11 +0100] schema-compat-plugin - warning: no entries set up under cn=ng, cn=compat,dc=f19,dc=ad,dc=test [20/Mar/2013:15:54:11 +0100] schema-compat-plugin - warning: no entries set up under ou=sudoers,dc=f19,dc=ad,dc=test [20/Mar/2013:15:54:11 +0100] - Skipping CoS Definition cn=Password Policy,cn=accounts,dc=f19,dc=ad,dc=test--no CoS Templates found, which should be added before the CoS Definition. [20/Mar/2013:15:54:12 +0100] - Skipping CoS Definition cn=Password Policy,cn=accounts,dc=f19,dc=ad,dc=test--no CoS Templates found, which should be added before the CoS Definition. [20/Mar/2013:15:54:12 +0100] - slapd started. Listening on All Interfaces port 389 for LDAP requests [20/Mar/2013:15:54:12 +0100] - Listening on All Interfaces port 636 for LDAPS requests [20/Mar/2013:15:54:12 +0100] - Listening on /var/run/slapd-F19-AD-TEST.socket for LDAPI requests [20/Mar/2013:16:41:29 +0100] - sasl_io_recv failed to decode packet for connection 23 This section in the 389-ds-base source code looks to be blamed: $ find -type f | xargs grep -C 5 maxbufsize ./ldap/servers/slapd/saslbind.c- prop_request(propctx, dn_propnames); ./ldap/servers/slapd/saslbind.c- } ./ldap/servers/slapd/saslbind.c- } ./ldap/servers/slapd/saslbind.c- ./ldap/servers/slapd/saslbind.c- /* Enable security for this connection */ ./ldap/servers/slapd/saslbind.c: secprops.maxbufsize = 2048; /* DBDB: hack */ ./ldap/servers/slapd/saslbind.c- secprops.max_ssf = 0xffffffff; ./ldap/servers/slapd/saslbind.c- secprops.min_ssf = config_get_minssf(); ./ldap/servers/slapd/saslbind.c- /* If anonymous access is disabled, set the appropriate flag */ ./ldap/servers/slapd/saslbind.c- if (config_get_anon_access_switch() != SLAPD_ANON_ACCESS_ON) { ./ldap/servers/slapd/saslbind.c- secprops.security_flags = SASL_SEC_NOANONYMOUS; Version-Release number of selected component (if applicable): 389-ds-base-1.3.0.4-1.fc19.x86_64 How reproducible: Steps to Reproduce: 1. Install freeipa-* packages 2. Run ipa-server-install 3. Run ipa-adtrust-install Actual results: ipa-adtrust-install crashes due to issue described above. Expected results: 389-ds-base accepts tickets with PAC and installer does not crash. Additional info:
I just verified that by increasing this value, FreeIPA fixes too.
Upstream ticket: https://fedorahosted.org/389/ticket/632
Hello Nathan, I see that the upstream ticket was closed, but the Bugzilla is still in NEW state. Is the bug fixed in 389-ds-base-1.3.0.5-1.fc19? This fix is very important for our users to be able to run Fedora 19 Test Day AD scenarios.
(In reply to comment #3) > I see that the upstream ticket was closed, but the Bugzilla is still in NEW > state. Is the bug fixed in 389-ds-base-1.3.0.5-1.fc19? This fix is very > important for our users to be able to run Fedora 19 Test Day AD scenarios. Sorry, Martin. Yes, the fix is in 389-ds-base-1.3.0.5-1.fc19.
This message is a notice that Fedora 19 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 19. It is Fedora's policy to close all bug reports from releases that are no longer maintained. Approximately 4 (four) weeks from now this bug will be closed as EOL if it remains open with a Fedora 'version' of '19'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 19 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.