RE: How is access control done?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



 

> -----Original Message-----
> From: fedora-directory-users-bounces@xxxxxxxxxx 
> [mailto:fedora-directory-users-bounces@xxxxxxxxxx] On Behalf 
> Of speedy zinc
> Sent: Tuesday, October 18, 2005 5:28 PM
> To: General discussion list for the Fedora Directory server project.
> Subject: Re:  How is access control done?
> 
> directory, or can I just add the new schema, and tell the 
> server that the new attributes are now allowed in 
> inetOrgPerson/Person/posixAccount/etc?

You _can_ do that but it highly discouraged.  Schema (particularly standard
schema) is intended to remain static so that all clients know what they are
dealing with.

> 
> The important thing is, I don't want to rebuild anything, not 
> to interrupt any service.
> 

You can create new schema for an auxillary objectclass that represents your
application and add that objectclass to the users that need it.

> I see there are quite a few of Netscape schema, for specific 
> apps, such as Collabra Server, etc. How do I add app-specific 
> schema like that without rebuilding the directory? Or do I 
> have to rebuild it everytime a new schema is added?

As mentioned above, simply add the objectclass to an existing user entry.
You should never have to rebuild anything.



--
Fedora-directory-users mailing list
Fedora-directory-users@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/fedora-directory-users

[Index of Archives]     [Fedora Directory Users]     [Fedora Directory Devel]     [Fedora Announce]     [Fedora Legacy Announce]     [Kernel]     [Fedora Legacy]     [Share Photos]     [Fedora Desktop]     [PAM]     [Red Hat Watch]     [Red Hat Development]     [Big List of Linux Books]     [Gimp]     [Yosemite News]

  Powered by Linux