Currently the properties files are read as ANSI, dropping any unicode char.
Please can you describe what this bug is about and how to verify it? Thanks.
(In reply to Pavel Novotny from comment #1) > Please can you describe what this bug is about and how to verify it? Thanks. for example create ldap configuration with unicode profile name, you can copy/paste from here between arrows: -->פרופיל1<-- you will notice that before we could not read this properties file.
I just can't get it work. When I try to login as user with UTF-8 chars. I get no 'search for princ', bind is successfull: 2015-09-18 13:37:18,416 DEBUG [org.ovirt.engineextensions.aaa.ldap.Framework] (ajp-/127.0.0.1:8702-6) BindRequest: SimpleBindRequest(dn='čeněk.lab.eng.brq.redhat.com') 2015-09-18 13:37:18,416 DEBUG [org.ovirt.engineextensions.aaa.ldap.Framework] (ajp-/127.0.0.1:8702-6) bind 2015-09-18 13:37:18,419 DEBUG [org.ovirt.engineextensions.aaa.ldap.Framework] (ajp-/127.0.0.1:8702-6) BindResult: LDAPResult(resultCode=0 (success), messageID=3) ........ 2015-09-18 13:37:18,459 DEBUG [org.ovirt.engineextensions.aaa.ldap.Framework] (ajp-/127.0.0.1:8702-6) SearchRequest: SearchRequest(baseDN='', scope=SUB, deref=NEVER, sizeLimit=0, timeLimit=0, filter='&(userPrincipalName=čeněk.lab.eng.brq.redhat.com)', attrs={cn}, controls={SimplePagedResultsControl(pageSize=100, isCritical=false)}) 2015-09-18 13:37:18,462 DEBUG [org.ovirt.engineextensions.aaa.ldap.Framework] (ajp-/127.0.0.1:8702-6) SearchResult: SearchResult(resultCode=0 (success), messageID=3, entriesReturned=0, referencesReturned=0, responseControls={SimplePagedResultsControl(pageSize=0, isCritical=false)}) When I try to use UTF-8 user in config file, fails while creating gc pool: 2015-09-18 13:48:03,369 DEBUG [org.ovirt.engineextensions.aaa.ldap.Framework] (ServerService Thread Pool -- 54) BindRequest: SimpleBindRequest(dn='čeněk.lab.eng.brq.redhat.com') 2015-09-18 13:48:03,369 DEBUG [org.ovirt.engineextensions.aaa.ldap.Framework] (ServerService Thread Pool -- 54) Creating LDAPConnectionPool .. 2015-09-18 13:48:03,728 DEBUG [org.ovirt.engineextensions.aaa.ldap.Framework] (ServerService Thread Pool -- 54) Sequence ad-open-pools create gc pool failed due to exception: 80090308: LdapErr: DSID-0C0903C5, comment: AcceptSecurityContext error, data 52e, v2580 2015-09-18 13:48:03,729 DEBUG [org.ovirt.engineextensions.aaa.ldap.Framework] (ServerService Thread Pool -- 54) Exception during sequence: LDAPException(resultCode=49 (invalid credentials), errorMessage='80090308: LdapErr: DSID-0C0903C5, comment: AcceptSecurityContext error, data 52e, v2580', diagnosticMessage='80090308: LdapErr: DSID-0C0903C5, comment: AcceptSecurityContext error, data 52e, v2580') Bind and search works OK in ldapsearch. Is issue on my side?
> When I try to use UTF-8 user in config file, fails while creating gc pool: the issue here is plain text, such as profile name (user visible) or any unicode string, unrelated to aaa specifically, the read of the file was invalid. never actually tried bind user this way... but I do know that utf-8 user is working in master with sso (first time we actually tried that). let's resolve this bug if profile name can be utf-8 other issues will be addressed when sso will be available. but I will try this anyway :)
profile name works fine with utf-8
Fixed bug tickets must have version flags set prior to fixing them. Please set the correct version flags and move the bugs back to the previous status after this is corrected.
oVirt 3.5.5 has been released including fixes for this issue.