Using GridServer Built-In Authorization

GridServer’s built-in role-based access control can be used to define what features a user can access on the system. Depending on the authentication type used, there are different methods for assigning roles to users.

If you are using GridServer’s built-in authentication, user authorization is mapped in the user account stored within GridServer. When you create or edit an account on the Admin > User Admin > User Admin page, the Security Roles section of the Edit User dialog enables you to select one or more roles that are given to that user’s account.

You can also use LDAP or Windows authorization, and edit roles so they map to users based on their group name. When you edit a role on the Admin > User Admin > Role Admin page, set the LDAP Group Name to the name of the group that receives that role.

If you are using Pure Kerberos or LDAP authentication, you can either use built-in authorization or LDAP authorization. If you use built-in authorization, this means you must create accounts for each of your users using GridServer’s built-in authentication, and specify one or more roles for each user. Although you need to set passwords when you create the user, they are ignored and Kerberos is used for authentication.