[Fedora-directory-users] Problem accessing Configuration Directory after upgrade to 1.0.3

[Richard Megginson]

Dan wrote:
>> I notice 2 differences.  The BIND is using version 2 when trying to
>> start the admin server.  That shouldn't matter.
>>
>> The problem seems to be with the BIND'ing.  When trying to start the
>> admin server, the RESULT to the BIND contains an empty dn.  When run
>> manually, the dn is correct.
>>
>> It seems like it is not authenticating properly with FDS 1.0.3.
>>
>> --
>> Fedora-directory-users mailing list
>> Fedora-directory-users at redhat.com
>> https://www.redhat.com/mailman/listinfo/fedora-directory-users
>>
>>     
>
>
> Any ideas on why the admin user is not binding properly when starting
> the admin server?  The password has not changed.  It is still stored in
> the admpw file as a SHA hash.  The only difference is that SSL was
> enabled for the Configuration DS.
>
> Also, has anyone else had this problem after upgrading to 1.0.3?
>   
Yep.
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=213788

It works if the admin server uses ldap: to talk to the config ds, but 
fails if the admin server uses ldaps: to talk to the config ds.

Try this: edit shared/config/dbswitch.conf - change the ldaps: url to 
ldap: and change the port from the secure port to the non-secure port.  
You should be able to restart admin server.
>
>
> --
> Fedora-directory-users mailing list
> Fedora-directory-users at redhat.com
> https://www.redhat.com/mailman/listinfo/fedora-directory-users
>   
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/x-pkcs7-signature
Size: 3178 bytes
Desc: S/MIME Cryptographic Signature
URL: <http://lists.fedoraproject.org/pipermail/389-users/attachments/20061103/d00dc625/attachment.bin>