If user is a member of a group with cyrillic symbols in it - this user doesn't get any roles assigned. That includes nested groups.

1. Scenario 1 (works fine): UserID (samaccountname property for user object in AD) is in latin, user is added as role - works as expected.
2. Scenario 2 (works fine): GroupID (samaccountname property for group object in AD) is in latin, group is added as a role - works as expected
3. Scenario 3 Simple (doesn't work): GroupID has cyrillic symbols in samaccountname - group gets added as a role but is displayed with questionmarks in place of cyrillic symbols => none of the members of such group gets role assigned
4. Scenario 4 Nested (doesn't work):

MainGroupID (in latin)
--NestedGroupID (has cyrillic symbols in name)
----UserID (in latin)

When MainGroupID gets added as a role - UserID still does not get role assigned because UserID is not a direct member of MainGroupID - UserID is a member of NestedGroupID which does have cyrillic symbols => entire chain breaks

In scenario 3 and 4 when user doesn't get role assigned - such user gets "no read/overall" permission error after logging into web interface. And mentioned previously question marks are displayed.

• 767.v4ffe48a_50303 is a version I ended up reverting to (and also readded all the roles with cyrillic symbols) - everything works fine again
• 771.v3fa_85a_df2c50 - haven't tested this version but presumably it should work too (I just didn't have clear understanding if my roles were working at this point in time when I upgraded to it)
• 775.vf7c4a_97194dd and 773.vfb_b_5a_ec97335 - on both of these versions roles with cyrillic symbols do not work