source: trunk/LATMOS-Accounts/man/man8/latmos-accounts-base-sql.pod @ 1508

# $Id$

=head1 DESCRIPTION

=head1 SPECIFIC SETUP PARAMTERS

=head2 db_conn

The C<libpq> connection parameters, eg a semin colon separated paramaters
containing the server, the database name, user and password, etc...

=head1 FEATURES

=head2 Network managment

Link::Accounts can build automatically some part of your DNS or DHCP
configuration.

To do this you have to create a C<netzone> object. Such object need a type:

=over 4

=item dns: to build a DNS zone for classic domain

=item reverse: for reverse IP address (168.192.in-addr.arpa)

=item dhcp: ISC dscpd configuration for fixed address

=item puppet: puppet configuration

=back

The way it works is quite simple, each zone will make the code to write a file
you can include in your server configuration. The match is done by looking the
zone IP address masks and the host IPs.

For example someone having a zone named C<private.mydomain.com> having masks
C<192.168.5.0/24>, and having an host named C<foo> with IP C<192.168.5.3> and
another host C<bar> with IP C<192.168.13.78>. The zone built will look likes:

    foo IN A 192.168.5.3

As you can see this DNS zone is not valid: the goal of such feature is to make
the repetive work for us, not to manage the full zone (even such feature could
be possible). The repetitive work is declaring the hundred computers our users
have.

The output will be happend to a template have the name of the zone suffixed by
C<.in>. You can put in this template evering about the zone declaration (SOA,
NS, TXT...).

=head2 User endcircuit

The C<endcircuit> attribute contain the deadline for people to make
admnistrative task when starting to work.
If set this attribute take precedence to C<expire> attribute for computed
attributes (C<accountExpires> for Active Directory).

=head2 User endEmployment

THis attribute compute the next day the user will leave the company according
the employment object registered.

The parameter C<employment_delay> give the number of days to ignore when a hole
exists between two employment

=head2 Group AutoMemberFilter

Group objects contains users members by setting either C<members> or
C<memberUID> attributes.

Sometimes it can be usefull to have group automatically populated by arbitrary
rules.

This is possible by setting a filter in the C<autoMemberFilter> attribute,
The filter format is the same the one used by L<la-search>, the attribute is
multivaluable.

So for example one can create an account automatically a group containing people
having "Olivier" as first name:

    autoMemberFilter: givenBame=Olivier

A probably more usefull example is a group containing people from two others
groups:

    autoMemberFilter: memberOf=group1
    autoMemberFilter: memberOf=group2

The  C<members> or C<memberUID> attribute becomes read-only attribute once
C<autoMemberFilter> attribute is set.

=head2 Aliases AutoMemberFilter

This attribute allow to create automatics dynamics aliases according filter
rules exactly like L<Group AutoMemberFilter> works.

The C<forward> attributes is automatically set with email address of selected
user, user w/o email address are ignored.