Difference between revisions of "LDAPS User Sync Profile"
Jump to navigation
Jump to search
Jrobertson (talk | contribs) |
Jrobertson (talk | contribs) |
||
| Line 34: | Line 34: | ||
|[[Image: usersearchcontainer.png]] | |[[Image: usersearchcontainer.png]] | ||
|- | |- | ||
| − | | | + | |[[Image: Userroles.png]] |
|Users created with this sync profile will have the selected role | |Users created with this sync profile will have the selected role | ||
| | | | ||
|- | |- | ||
| − | | | + | |[[Image: Usermailfield.png]] |
|User attribute containing primary email address | |User attribute containing primary email address | ||
| | | | ||
|- | |- | ||
| − | | | + | |[[Image: Useraltemail.png]] |
|Additional email addresses for a user can be imported here | |Additional email addresses for a user can be imported here | ||
| | | | ||
|- | |- | ||
| − | | | + | |[[Image: Userupn.png]] |
|This option will make sure a user's UPN will always be present in the Alternative Addresses for that user | |This option will make sure a user's UPN will always be present in the Alternative Addresses for that user | ||
| | | | ||
|- | |- | ||
| + | |[[Image: Userusername.png]] | ||
| + | |User attribute containing the username | ||
| | | | ||
| − | |||
|- | |- | ||
| − | | | + | |[[Image: Userallowemail.png]] |
|Allows users to have an email address as their username, this may have unexpected side-effects and each email address must be unique | |Allows users to have an email address as their username, this may have unexpected side-effects and each email address must be unique | ||
| | | | ||
|- | |- | ||
| − | | | + | |[[Image: Userguid.png]] |
|User attribute containing a unique and immutable identifier | |User attribute containing a unique and immutable identifier | ||
| | | | ||
|- | |- | ||
| − | | | + | |[[Image: Userlastname]] |
|User attribute containing the user's surname | |User attribute containing the user's surname | ||
| | | | ||
Revision as of 01:40, 10 January 2022
Base Settings
| Field | Description | Active Directory Example |
|---|---|---|
|
A short description to identify the sync profile | |
|
IP address or host name of the directory server to collect information from. Password reset will only work over LDAPS:// | |
|
Username to bind to when collecting | |
|
Password to use when collecting information from the server |
User Settings
| Field | Description | Active Directory Example |
|---|---|---|
|
The qualified name for the container to look for users. eg, OU=students, OU=users, DC=yourdomain, DC=com | 
|
|
Users created with this sync profile will have the selected role | |
|
User attribute containing primary email address | |
|
Additional email addresses for a user can be imported here | |
|
This option will make sure a user's UPN will always be present in the Alternative Addresses for that user | |
|
User attribute containing the username | |
|
Allows users to have an email address as their username, this may have unexpected side-effects and each email address must be unique | |
|
User attribute containing a unique and immutable identifier | |
| File:Userlastname | User attribute containing the user's surname | |
| The LDAP attribute that stores the SIS ID for a user. This field is important for Canvas and other services |
Advanced Settings
| Field | Description | Active Directory Example |
|---|---|---|
| Users and Org Units created by this profile will be created under this Org Unit. | ||
| When this option is enabled, Cloudwork will not create any of the Org Units in the search container field. Users and sub Org Units will be created directly under the parent Org Unit | ||
| When a user is deleted or moved to a location that Cloudwork can't see, Cloudwork will perform the chosen action | ||
| The email domain for groups. If Force Mail Domain is selected, user accounts created or updated by replace the email domain with this domain | ||
| Cloudwork will use this template to send welcome emails, if the "send Welcome" option is enabled. |
