| - |
====Configuring the Authorization Realm====
|
+ |
====Configuring the Authentication Realm====
|
| |
[[Image:Corresponding uDeploy Authorization Zone.png]] |
|
[[Image:Corresponding uDeploy Authorization Zone.png]] |
| |
[[Image:Authorization Realm Ex.png]] |
|
[[Image:Authorization Realm Ex.png]] |
| |
Once this configuration is completed successfully, the expected functionality would be when a user attempts to login to uDeploy, a quarry is made to Active Directory. Assuming that a username is found and that the password for that user is correct, the user's information is imported to uDeploy, including the groups that the user belongs to. With this in mind, it's important to limit your user and group search bases to users and groups that are useful in uDeploy. When regarding this, a user will only be imported when they attempt to log in, thus only 1 user will be imported per login attempt. This means that you could configure you user search base to be the entire AD, but you would only have extra users if those extra users attempted to login. This makes limiting the user search base important only in regards to limiting the users that CAN login to uDeploy. However, this is not the same for groups. If one user logs in and belongs to 1000 groups, unless you've limited your group search base to the location of the groups that are important to uDeploy, all 1000 groups will be imported. This make focusing your group search base VERY important if you have a large number of groups in AD. |
|
Once this configuration is completed successfully, the expected functionality would be when a user attempts to login to uDeploy, a quarry is made to Active Directory. Assuming that a username is found and that the password for that user is correct, the user's information is imported to uDeploy, including the groups that the user belongs to. With this in mind, it's important to limit your user and group search bases to users and groups that are useful in uDeploy. When regarding this, a user will only be imported when they attempt to log in, thus only 1 user will be imported per login attempt. This means that you could configure you user search base to be the entire AD, but you would only have extra users if those extra users attempted to login. This makes limiting the user search base important only in regards to limiting the users that CAN login to uDeploy. However, this is not the same for groups. If one user logs in and belongs to 1000 groups, unless you've limited your group search base to the location of the groups that are important to uDeploy, all 1000 groups will be imported. This make focusing your group search base VERY important if you have a large number of groups in AD. |
