> if it's likely that the DSA you're using for OX will be the only (or
> rather the authoritative) one (in your oraganization) I would use
just
> "dc=hitt,dc=at" (you'll probably have an ou=OxObjects container in
> there anyway unless you change things yourself).

ok thx.


>> 1.  if I want to use a second domain on the server. does this
change
>> the above question?
> 
> since (at least with OpenLDAP) there can be only one basedn per
> database: no.  while you could have several databases in your DSA I
> don't expect OX to handle this.

thats no problem as we'll host only company mail addresses, but for
congresses and that stuff we've often additional domains.

>> 2. I took a look at luma as ldap client. Is it save to change stuff
>> in the ldap or is that bad because the data is also stored
somewhere
>> else? Which data is save to change only in ldap
> this depends on what you're changing. there's data that's stored in
> both (the RDBMS and the DSA) and there's data that's only stored in
> the DSA.

I'm looking for a list what is save to change and what not ;-)

>> 3. Whats the best way to define aliases? is there a ox way or is
>> done only by the mta?
> one could have a look at the way the OX admin interface does this.

I'm using the gpl version

> other than that this probably depends on the MTA you're using.

yes, I can configure that in my mta, I just thought its better do to
that also in ox, as I can provide an domain at creating an user on the
command line.

> see pages 136ff in this sample chapter from the O'Reilly LDAP System
> Administration book (which I don't really recommend, btw) for a
start:
> http://www.oreilly.com/catalog/ldapsa/chapter/ch07.pdf

will take a look at it. 

>> 5. where can I find a list of all options I can use for adduser_ox
>> and changeuserattr_ox?
> did you try:
>   vim adduser_ox
>   adduser_ox -- help

both. adduser_ox is somewhat ok documented but changeuserattr_ox is
not.

# changeuserattr_ox -h

Usage: /usr/sbin/changeuserattr_ox [Options]

Options:

  --username=NAME              The Username - eg. john

  --attrib=NAME                The Attribute - eg. givenName

  --value=VALUE                The new Value of the Attribute - eg.
Miller

  --file=FILE                  If given, custom ldif File is used for
modifying! - eg. /home/f00/bar.ldif
                               See ldapmodify for Details!

can I only manipulate attributes which are also setable in the
adduser_ox or are there some additional?


> don't know about these OX tools but changing passwords with
*anything*
> (ldapmodify, luma, gq, lat, web2ldap, etc.) should be fine as long
as
> the used hashes are supported all components. note that RFC 2256
says:

ok

>> ps: I'm missing a FAQ part in the wiki, I'll add a new page to the
>> wiki with the answers to my questions.
> 
> good idea. I'm not too sure of the structure (FAQ vs. different
> categories for different topics) but the main idea for the wiki was
> just that --  to "distill" stuff from the mailing lists. so go
ahead!


I missing a faq section most, so I'll start sharing my in the faq this
week ;-)




--

Robert Penz
HITT - health information technologies tirol gmbh
Tel: +43-512-576523 - 232
Fax: +43-512-576523 - 70
email: robert.penz at hitt.at

"Windows Vista" is the abbreviation for "Windows with Viruses,
Instability, 
Spyware, Trojans and Adware"