[Asterisk-Users] LDAP synchronization script

[Stefan de Konink]

The base problem, I presume is not that there is no documentation, but how
to combine all those defacto standards, from an user and an application
point of view.
An Active Directory implementation in Linux (for users and application)
for me starts with the standard PAM/NSS stuff but why not extend that for
Jabber, Asterisk, Postfix/Sendmail, DHCPd, DNS and a zillion other stuff
like (a higher level) ENUM?

For most of the above application are 'dynamic' ldap backends made, which
are usable. Though what is the best thing to start with? Application with
users under it. Users with Application under it. Or the last type I think
it is the most usuable way of implementing:

Organisation/
	Groups/
		Applications	(Group/Application Specific configs)
	Users/
		Applications	(User/Application Specific configs)
	Applications	(Organisation Specific configs)

Applications (Basic configuration)
	Name/			(Name like Asterisk)
		ID/		(Which Asterisk server IP address etc.)


Which makes .application and /etc/application obsolete if well
implemented. Performance wise you would not want to poll the LDAP server
24/7 (though I want it ;) but only fetch while reloading.

In the combination and integration of those things I'm now writing a
thesis with a production proof-proof of concept, for Unified Messaging in
a Box. Though, importing all schema's like cosine, dhcpd, etc. the mess
only gets bigger eq. there need to be a basic structure and I would
like to have some feedback about it.

The main objective is to make the user have a 'home' peer/server, though
it doesn't depends on this peer but it is like 'the first choice'. For
example two Asterisk servers, one crashes the other peer/server takes over
and starts accepting the other servers its users.

Ok, this basically implies there is a distributed filesystem around, at
the moment I use CodaFS for that. (Requires patching of some programs like
Postfix)


Stefan


On Fri, 18 Jun 2004, Lars Boegild Thomsen wrote:

> Hi,
>
> > The what belongs were is my big question at the moment and I personally
> > don't want to design anything LDAP-ish that would become my private tree
> > instead of defacto implementation.
>
> You should definitely have a look at the defacto standards for storing users
> and groups (check http://www.padl.com/OSS/pam_ldap.html).  Would be rather
> cool to have a Linux network with users and groups defined in LDAP - and
> each user just having an extension defined in his record.  Asterisk base
> configuration should go in separate three.
>
> Regards,
>
> 	Lars...
>
> _______________________________________________
> Asterisk-Users mailing list
> Asterisk-Users at lists.digium.com
> http://lists.digium.com/mailman/listinfo/asterisk-users
> To UNSUBSCRIBE or update options visit:
>    http://lists.digium.com/mailman/listinfo/asterisk-users
>