Why can't I get the LDAP device group tags saved to PAM?


Article ID: 103946


Updated On:


CA Privileged Access Manager - Cloakware Password Authority (PA) PAM SAFENET LUNA HSM CA Privileged Access Manager (PAM)


You may have experienced that the tags are not stored when belonging to an imported LDAP device group.
They appear blank the next time the imported LDAP group is edited.
However, if the device group is manually created then the tags are properly saved.

Why can't I get the LDAP device group tags saved to PAM?


Any Virtual or Hardware Appliance running any PAM version. (as of June 2018)


As per the product internal code this is working as designed, as the tags should/will ONLY be applicable to device group, if any only if, the provision type is LOCAL.
In other provision types like AWS/LDAP, the tag specification will just be ignored though specified like you observed.

Additional Information

The reason why you see the tags applicable when you do manually but not through LDAP import is for the same reason.
During import the provision type happens to be LDAP, while manually done you would have kept it LOCAL.
If you specify AWS as provisioning type when manually creating the group, you can observe the tags taking no effect though specified.