In OmniGroupServer, you must configure the repositories that you want to use. Each repository in OmniGroupServer stores group membership information for one type of security. This allows it to respond to actions such as:
http://localhost:3057/action=GetGroups&User=DOMAIN%5CJSMITH
This action retrieves a list of all the groups that DOMAIN\JSMITH is a member of (whether they are a member of that group directly, or a member of another group that is itself a member of that group).
After you have set up your repository you can use actions such as GetGroups, GetAllUsers and GetAllGroups to determine whether the server has collected any group information.
You normally configure repositories automatically in the OmniGroupServer installation process. The configuration file lists repositories in the [Repositories] section. The following example shows a configuration section for storing and collecting NT groups from LDAP:
[Repositories] GroupServerDefaultRepositories=LDAP Number=1 0=LDAP [LDAP] GroupServerLibrary=ogs_ldap.dll LDAPServer=dc LDAPPort=636 LDAPBase=DC=DOMAIN,DC=COM LDAPType=MAD LDAPSecurityType=SSL LDAPBindMethod=NEGOTIATE
The GroupServerDefaultRepositories parameter is set to LDAP, which means that OmniGroupServer queries the LDAP repository if the action does not specify a repository. You can set this parameter to a comma-separated list of repositories.
To force OmniGroupServer to update its repositories, restart the OmniGroupServer service.
|
|