We are attempting to move to badge-based login. However, all of our badge readers use prefix and suffix delimiters when scanning badges. For example, a badge 12345 gets scanned in as {12345}. This was installed for security purposes and I'm hoping we don't need to reconfigure all badge readers to remove these delimiters.
Is there anything in the works to allow for delimiters?
We are using a pure Active Directory user source so editing the badge value for each user is not an option.
Could you use the AD Database Hybrid option and utilize the Badge Authentication Query?
You could put in a Concat('{', ? '}') in the where clause.
That sounds like it would require us to manage the storage and the link of badge values to users. The advantage of the pure AD user source allows our HR team to manage the badge values, and our user source immediately reflects updates to users and their badges.
Users, badges, and passwords are still managed in the AD source in hybrid, you just have to get roles from a separate external db. You can also modify how Ignition queries the AD (i.e. add your brackets to the ADs badge numbers.)
https://docs.inductiveautomation.com/display/DOC81/AD+Database+Hybrid