Possible account information APIs? (lookupd etc)

Matthias Clasen mclasen at redhat.com
Thu Sep 13 23:15:30 UTC 2007


On Thu, 2007-09-13 at 17:29 -0400, William Jon McCann wrote:
> Hi Bill,
> 
> On 9/13/07, Bill Nottingham <notting at redhat.com> wrote:
> > William Jon McCann (mccann at jhu.edu) said:
> > > 1. Query / store user photos (avatars)
> > > 2. Query user account status in an implementation/backend independent
> > > way (locked, expired etc)
> > > 3. Query the user's real world name etc (ie. not just gecos)
> >
> > By this, you mean more than just the name in gecos?
> 
> Ideally, yes.
> 
> > > Darwin seems (at least from these docs) to use lookupd for some of this.
> > >
> > > Anyone have any experience with lookupd specifically?  Or pointers to
> > > different solutions?
> >
> > First, is there even any standard for storing any of this extended account
> > information?
> 
> There are various I guess.  For example, for an LDAP agent:
> http://tools.ietf.org/html/rfc2798#section-2.6
> 
> This would be a reasonable standard to use and most likely a superset
> of any existing functionality.

Looks like it is a bit lighter on the various "contact ids" than what
e.g. e-d-s stores (jabber, msn, aim, etc). But I grant you that the
"license plate" field is pretty unique...




More information about the fedora-devel-list mailing list