Ajeet S Raina wrote:
Let me explain you what is the requirement.
1.All we have different projects in Noida and Hyderabad.
Those Projects are running on Linux Machines.We are setting up the 389
Server so that these Project Machine Client can authenticate through
389 Server credentials (Just like ADS Clients).Now We need to setup
for the same.As of now there are 15 Sysadmin in Noida and 30 Sysadmins
in Hyderabad.We need to setup for them.
Ah - so you are using windows sync, so you must maintain the same tree
structure between AD and 389?
2.Can we provide Self Service for these users to fill up the data
themselves?I dont know how gonna it work but can it be done.
Yes. Use the 389-dsgw package - this provides a web app that can be
used for self service, including allowing the user to change his/her
password.
3.Users should be able to change password after 90 days.
You can control this with password policy
4.We need to setup Master -Slave Replication structure too.
None of this would require using a hierarchical tree with multiple OU
containers, except if you are using windows sync.
Pls Suggest.
------------------------------------------------------------------------
--
389 users mailing list
389-users@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/fedora-directory-users
--
389 users mailing list
389-users@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/fedora-directory-users
