NOTE: This problem is now fixed in Reporter versions, 9.3.x and above.
To duplicate this issue, follow these steps:
- Install Reporter, and connect it, via LDAP, to a AD tree.
- On the AD server, add Russian input language in Windows and create a group with Russian symbols in it, and a group with only English symbols.
- Create two users, and add each to the above groups.
- Test to see if you can login to reporter by both usernames.
Result: You cannot login to a user who is a member of the group named with Russion symbols, using Cyrillic names (font and type).
You will see this type of message in the journal:
BCRJ:2010-06-03 10:06:51 (4c07548b) NOR.INFO.WEBSE
PostAuth => Attempted non-existent user: a.rybinsky
NOTE: Reporter will still be unable to properly process double byte created usernames found in the acess logs it processes. This specific issue has been reported to Bluecoat engineering, and they are working on a response. For more information on this issue, please see 000009062
Links to other articles:
For details on how to setup LDAP, and Reporter, see 000013348
For details on how to tell the difference between groups found in access logs, and groups found in the LDAP realm, see 000010129
For details on what each LDAP attribute means, see 000021975
For details on what type of usernames you can process in a acess log, see 000014866