-
Title
Automatically Assign Users to Labels without Requiring Login by Leveraging LDAP Import and CUSTOM User Fields -
Description
LDAP Filters require each user to login in order for the label to be applied to said user(s). In some environments, users rarely or never login to the K1000 interface. In these situations, the provided workaround approach detailed here is more feasible.
-
Resolution
As a workaround, the attached custom ticket rule can be imported to the K1000 and slightly modified based on user/label criteria to auto-populate User-based labels by way of utilizing the CUSTOM_1, CUSTOM_2, CUSTOM_3, and CUSTOM_4 fields - which are mappable during LDAP import.
WARNING: Use at your own risk. This rule is tested but unsupported. KACE is not responsible for any damage caused by manipulating or using this custom ticket rule.
WARNING: A manual appliance backup should be run before running/testing a new custom ticket rule. In the event the custom ticket rule results in unexpected behavior, the appliance can then be restored to the backup performed immediately before the rule was implemented.
LDAP Import (Step 0, must be completed before ticket rule will function correctly) -
During LDAP import, the CUSTOM field(s) must be mapped to the Active Directory attribute(s) for which the rule is going to apply. Alternatively, the CUSTOM fields can be manually populated.
Either way, this configuration must be completed as a prerequisite for the rule to function properly.
Step 1 -
Create the manual label for use with this ticket rule. Then, import the attached custom ticket rule kpkg.
Step 2 -
Modify the Select Query to suit your needs.
- Set the 'Value' to the actual value you are attempting to find in the CUSTOM field (in the template, CUSTOM_1 is used).
- Also, set the 'Label Name' to the name of your label.
select U.ID from USER U join USER_LABEL_JT J on U.ID=J.USER_IDwhere U.CUSTOM_1='Value' and U.ID not in (select USER_ID from USER_LABEL_JT join LABEL on USER_LABEL_JT.LABEL_ID=LABEL.ID where LABEL.NAME='Label Name')Step 3 -
Modify the Update Query to match the changes in Step 2 (notice the update query defines the label name twice).
- Set the 'Value' to the actual value you are attempting to find in the CUSTOM field (in the template, CUSTOM_1 is used).
- Also, set the 'Label Name' to the name of your label.
insert into USER_LABEL_JTselect U.ID,L.ID from USER U join USER_LABEL_JT J on U.ID=J.USER_IDjoin LABEL L on L.NAME = 'Label Name'where U.CUSTOM_1='Value' and U.ID not in (select USER_ID from USER_LABEL_JT join LABEL on USER_LABEL_JT.LABEL_ID=LABEL.ID where LABEL.NAME='Label Name')Step 4 -
- Modify the ticket rule schedule to suit environmental needs (Daily, Hourly, however frequently desired). NOTE: Setting schedule to "On ticket save" is strongly discouraged.
- Enable ticket rule and save.
Advanced Techniques -
- U.CUSTOM_1 can be changed to U.CUSTOM_2, U.CUSTOM_3, or U.CUSTOM_4, as needed.
- Multiple CUSTOM fields can be evaluated with AND or OR boolean operators. Example: To match users with a value of '1' in CUSTOM_1 and '2' in CUSTOM_2, the U.CUSTOM_1='Value' portion of both queries would be rewritten as U.CUSTOM_1='1' and U.CUSTOM_2='2'
-
Attachments