Today I encountered a request to allow API actions by a service account which seems to have exceeded a 20 character name limitation.
20 character names are recognized, 21 character names are not.
Is this documented anywhere? I can’t seem to locate it if so.
I tested this on BigFix 11.0.4 using the IEM CLI with an operator account that has a 24-character username, and I was able to authenticate successfully using iem.exe login. I also verified the session by running REST API queries afterward, so I couldn't reproduce the issue with a 24-character operator name.
I believe this is LDAP user if so something outside BigFix is interfering it.
This limitation likely stems from the Active Directory sAMAccountName (pre-Windows 2000 logon name) attribute, which has a strict 20-character limit for backward compatibility with legacy Windows and LAN Manager clients.
To close this thread off - This is 100% the case, we figured this out late last Friday.
The Windows admin/AD SME apologized for making the name so long and not recalling this known limitation when he did so. Thanks for your response @shabircse.