Overview#
Our IDM Best Practices Documents for naming of Global Configuration Value Naming Best Practices.idv.dit.data.*#
These DirXML Variables are Global Configuration Variables that are specific to the tree structure within the IDV. Normally, these would normally not need edited unless the tree structure changes. Typical entries we commonly use:| display-name | name | value |
|---|---|---|
| User Container | idv.dit.data.users | |
| Active Users Container | idv.dit.data.users.active | |
| Terminated Users Container | idv.dit.data.users.terminated | |
| Default Password Policy | idv.dit.data.default-password-policy | |
| Posix Number Counter DN | idv.dit.data.posix-counter-container | |
| Group Container | idv.dit.data.groups | |
| Role Location | idv.dit.data.roles | |
| Regions Location | idv.dit.data.regions | |
| Sectioncodes Location | idv.dit.data.sectioncodes | |
| Current In-Scope Regions | idv.dit.data.inscope.regions | |
| Roles In Scope | idv.dit.data.inscope.roles |
idv.data.*#
These DirXML Variables are Global Configuration Variables that are specific to data within the IDV. Normally, these would normally need to be modified when changing environments, like from test to production.Typical uses would be:
| display-name | name | value |
|---|---|---|
| Email Address Exchange Team | idv.data.emailaddress.exchange | exchange@willeke.com |
| Email Address IDM Team | idv.data.emailaddress.idm | idmteam@willeke.com |
idv.workflow.*#
These DirXML Variables are Global Configuration Variables that are specific to workflow operations within the IDV. Normally, these would normally not need to be modified when changing environments, like from test to production.Typical uses would be:
| display-name | name | value |
|---|---|---|
| User account for starting workflows | idv.workflow.user | |
| Default workflow approver | idv.workflow.default.approver | |
| Workflow definition container | idv.workflow.container | |
| definition display-name | idv.workflow.url |
idv.workorder.*#
These DirXML Variables are Global Configuration Variables that are specific to workorder driver operations within the IDV. Normally, these would normally not need to be modified when changing environments, like from test to production.Typical uses would be:
| display-name | name | value |
|---|---|---|
| Workorder Container | idv.workorder.container | |
| User Removal Delay (Seconds) | idv.workorder.delete.delay | |
| WorkOrder Cleanup | idv.workorder.type.cleanup | |
| WorkOrder Enable | idv.workorder.type.enable | |
| WorkOrder Disable | idv.workorder.type.disable |
idv.credprov* #
These DirXML Variables are Global Configuration Variables that are specific to workorder driver operations within the IDV. Normally, these would normally not need to be modified when changing environments, like from test to production.Typical uses would be:
| display-name | name | value |
|---|---|---|
| SecretStore Repository | idv.credprov.nss.repository | system\services\idm\driverset1\Library\lib-CredProv-NSSRepository |
| SecureLogin Repository | idv.credprov.nsl.repository | system\services\idm\driverset1\Library\lib-CredProv-NSLRepository |
Driver Configuration Value Naming#
These DirXML Variables are Global Configuration Variables are Driver Scope and are values that are "local" to the driver and not available to other drivers.Unfortunately, Novell's driver developers are all over the place on these and so many do not follow any naming conventions.
drv.data.*#
These DirXML Variables are Global Configuration Variables are Driver Scope and are specific to data for the driver. Normally, these would normally need to be modified when changing environments, like from test to production.drv.*#
These DirXML Variables are Global Configuration Variables are Driver Scope and are specific to the driver. Normally, these would normally not be modified when changing environments, like from test to production.| display-name | name | value |
|---|---|---|
| Connected System or Driver Name | ConnectedSystemName |
drv.dit.data.*#
These DirXML Variables are Global Configuration Variables are Driver Scope and that are specific to the tree structure within the Connected Application. Normally, these would normally not need edited unless the connected system structure changes. Typical entries we commonly use:| display-name | name | value |
|---|---|---|
| User Container | drv.dit.data.users | |
| Active Users Container | drv.dit.data.users.active | |
| Terminated Users Container | drv.dit.data.users.terminated |
