AD Users | Update Oracle Database
Rule description
This rule queries the specified Active Directory scope and for each user in this scope finds a record with the same anchor in Oracle Database and updates this record with attribute values that are specified in the Attribute mapping setting.
NOTE: This rule supports the VARCHAR data type.
When to use this rule
Use this rule when you need to write certain Active Directory user attributes back to the Oracle Database.
For example, you can write back the information to HR/ERP/SIS system about whether the user was provisioned to Active Directory, and if he was, specify the proper samAccountName, email address and UserPrincipalName generated for this user.
Rule settings
Query section
| Setting name | Description |
|---|---|
Limit scope to this domain or OU |
This setting defines the search query scope. To improve query performance, limit the scope to a specific OU. IMPORTANT: To test the rule configuration, limit the rule scope to an OU that contains test accounts or objects and use the Preview feature. |
Query criteria |
Query criteria are sent with the query and may improve query performance. TIP: For additional information on the criteria builder, see the How to use Query Builder dialog for Query Criteria and Filter rule settings. |
Active Directory anchor attribute |
Defines the attribute in the Active Directory to which the Data Source anchor attribute is to be compared. |
Data Source Anchor attribute |
Select a column in the data source that contains the attribute value for identifying and mapping a computer. |
| Other Query Settings | |
Properties to display |
Select properties to display for each object found by the query. |
System Properties |
List of properties required for this rule to be executed correctly. |
|
Filter
|
Set the filtering conditions to only return objects or data that need to be processed by the rule. Example: filter by Name column. |
Sort by |
Sort result object list. |
Initialization script |
Usually, rules use query criteria to limit the query search scope. It improves the performance of the executed rule. Due to the PowerShell limitations, it is not possible to use calculated expressions in query criteria. That is the point where the initialization script can help. You can initialize a global variable in this setting and then use it in query criteria. IMPORTANT: To use a variable, declared in the initialization script, in the query scope, it must be global: Example: Update AD users, created in the last ten days.
|
Database Connection Settings | |
Hostname |
Specify Oracle server hostname (or its IP address) to which Cayosoft Administrator will connect. NOTE: For more information, please read Connecting to Oracle database article. |
Service name |
Specify the Oracle database service name. |
Port |
Specify Oracle SQL*Net Listener port number; the default is 1521. |
Table |
Specify Table or View from the selected database. Click the Selector button to display a list of tables from which to choose. |
Credentials |
Specify Oracle user account name and password. |
Action section
| Setting name | Description |
|---|---|
Attribute mapping |
Map Active Directory user attributes whose values must be written back to matching database table columns. |
Other Properties | |
Other Properties |
Data mapping also can be set by the script. If you want every provisioned user to have extension attribute 1 populated with some string value then use this
Copy
If you want every provisioned user to have extension attribute 2 populated with the corresponding value from the column in your data source file, then use this:
Copy
since NOTE: If you set mapping for the same properties both in Other properties and Other properties script, attribute values will be updated by the script. |
Output section
This section defines the output format of this rule.
To get more information about this section, please see the Rule Output section article.
Enforce/Schedule section
This section defines the schedule for how often to run the rule.
To get more information about this section, please see the Rule Enforce/Schedule section article.
Comments
0 comments
Please sign in to leave a comment.