389-users March 2007

389-users@lists.fedoraproject.org

59 participants
64 discussions

Start a nNew thread

[Fedora-directory-users] Password Sync Error
by Jeffrey Jamisola 07 Mar '07

07 Mar '07

2 1

[Fedora-directory-users] sorry retarded question on fds and tcpip no luck in faq
by SheridanJ West 07 Mar '07

07 Mar '07

Excuse me - i need a big clue I have a fc6 box with many ethernet cards in ip runs ..... [rfc 1918 range] - local garbage postgres... [proper ip 1] www postfix cyrus-imap [proper ip 2] " [proper ip 3] " [proper ip 4] " with fds - 1.04 (most recent) it appears i can only run one port 389/636 using the java startconsole then its using some odd port number for each new domain rather than ideally [proper ip 1] www postfix ldap:389 ldap:90009 ldap:90010 ldap:900011 [proper ip 2] " noldap running [proper ip 3] " [proper ip 4] " The carter book on ldap appears to make no mention of a 'listen' like command you fing in apache, theres a hint in the the fds wiki of an inf file where things like server identifier can be specified but is fds upto the job each ldap stores will be light with data, rather than big So is what im trying to do possible with fds ?, I think no is the answer with java. Any responses (even rude ones most welcome)

3 2

[Fedora-directory-users] Password Sync Error
by Jeffrey Jamisola 06 Mar '07

06 Mar '07

2 1

[Fedora-directory-users] 2 user passwords ? / updates on consumer without referral
by ivan mitev 06 Mar '07

06 Mar '07

hello list ! i'm doing some tests to replace our openldap based ldap infrastructure with fds; i'm really happy with fds compared to openldap, but i'm running into a little problem... what i'm trying to achieve: we have 2 different user passwords: one for our lan, the other for the dmz (imap, jabber, ...) ; the ldap supplier is in the lan, and there's a consumer in the dmz; the lan password should be used for user/services binding to the lan server, while the dmz password should be used for user/services binding to the dmz server is there a simple way to do that with fds (eg. a plugin where one can choose which attribute fds uses for binds) ? with openldap, on the supplier, the lan password was stored in userPassword, and the dmz password was stored in obsDmzPassword (from our custom schema) ; the userPassword attribute was excluded from the lan->dmz replication, and we had a script that would connect to the dmz as the directory manager (-> so no referral with this user) and which would copy the content of obsDmzPassword to userPassword that's ugly, but it worked fine now, with fds, i managed to do the same thing, when selecting "use the databases" under "suffix request processing" on the consumer ; however, this setting goes back to "return referrals for update operations" after each full consumer initialization ; is there a way to prevent that from happening ? thanks ! ivan

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

389-users March 2007