I am trying to use an employeeID in AD to be used for the badge attribute fields so we can have users login with their badges. I am able to populate the users on the domain controller, but I am having difficulty getting the badge number from this attribute/field. Any help on this would be beneficial. Thanks
1 Like
You may be able to try using a test login to see if badge number is returned by your Identity Provider. Here is our documentation on test login: Test Login and Logout - Ignition User Manual 8.1 - Ignition Documentation.
This is an example IdP response from a test login:
Yes I saw this, but it never shows me the badge number. Does Ignition not let the badge number be shown when testing a login? Does Ignition only compare the string/int associated with the corresponding 'badgeID' attribute??
Also, Does it matter which attribute in AD I use?
I can get everything else except the attribute I use for the badge number which is 'employeeID' or even 'employeeNumber' in AD.
I am able to use the badge id with the internal user source, just no luck with the AD.
Am I missing something?
Any help would be appreciated.
I was finally able to figure out why I couldn't use a badge to login. I missed have the (&(objectClass=user)("Attributebeingused"={0})). I had "Attributebeingused" to "badge", which was wrong.
Also, is there anyway to update a users "badge" field if I was going to use a hybrid or internal data source by incorporating a gateway script on a page in a client window??
EX. push a button, ask for a user name that is in a user source, and use the badge reader to change the 'badge' attribute inside that users properties??
Active Directory users are managed by the Active Directory Server itself, even when using an AD/Internal, or AD/Database hybrid. The Internal and Database hybrid part is able to handle roles, and contact information, but I do not believe it contains any response data we can update such as the badge field.
This AD/Database Hybrid User Source is not manageable from within Ignition. Users/passwords must be administered through Active Directory, and roles, contact info, and so on, must be administered directly through the database
"The Internal and Database hybrid part is able to handle roles, and contact information, but I do not believe it contains any response data we can update such as the badge field."
Is there potential or headway in order to update this badge field inside a hybrid source via gateway script from the client window? If we can update roles and other information why can't the badge field also be updated??
This would be fantastic, and would better Ignition if we can do this!
Let me know! Thanks.
User authentication, including badge info, is governed by AD when AD is used. You have to manage it in AD, not Ignition.
1 Like