cli end entity creation DN issue with non-latin letters

[drlight17]

Hello. I apologize if there were already been such discussion. I'm having an issue when trying to create end entity with non-latin CN using cli command like ejbca.sh ra addendentity --username ivanovii --dn 'CN=Иванов Иван Иванович' --token P12 --caname ManagementCA --type 1 --password 1234567890 --email [email protected], as it produces broken CN:

2025-03-19 09:29:58,608+0300 INFO  [org.ejbca.ui.cli.ra.AddEndEntityCommand] (main) Trying to add end entity:
2025-03-19 09:29:58,608+0300 INFO  [org.ejbca.ui.cli.ra.AddEndEntityCommand] (main) Username: ivanovii
2025-03-19 09:29:58,608+0300 INFO  [org.ejbca.ui.cli.ra.AddEndEntityCommand] (main) Password: <password hidden>
2025-03-19 09:29:58,609+0300 INFO  [org.ejbca.ui.cli.ra.AddEndEntityCommand] (main) DN: CN=������������ �������� ����������������

I've tried many things to work this around with the partly help of ChatGPT but with no luck.
Creation of entity with such non-latin using web RA works like a charm. I would be very grateful for any help.
Docker image keyfactor/ejbca-ce:9.0.0 is used.

[drlight17]

Answer to myself: as a workaround I've switched to use SOAP api instead of cli. But I would like the cli method to work too.

[primetomas]

This should have to do with terminal encoding things. Internally the same functions are used as with a SOAP API.

[drlight17]

This should have to do with terminal encoding things. Internally the same functions are used as with a SOAP API.

Hmm... I'm using soap api call with curl in the same terminal on the same host with the same "encoding things" and no issues. Such call looks like this:

curl -X POST -H "Content-Type: text/xml;charset=UTF-8" \
     --cert cert.pem --key private.key --pass 1234567890 \
     -d @- <<EOF \
     https://ca.domain.org/ejbca/ejbcaws/ejbcaws
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:ws="http://ws.protocol.core.ejbca.org/">
   <soapenv:Header/>
   <soapenv:Body>
      <ws:editUser>
         <arg0>
            <username>${user_login}</username>
            <subjectDN>CN=Иванов Иван Иванович</subjectDN>
            <caName>ManagementCA</caName>
            <tokenType>USERGENERATED</tokenType>
            <clearPwd>${passwrd}</clearPwd>
            <email>${user_login}@domain.org</email>
            <subjectAltName>RFC822NAME=${user_login}@domain.org</subjectAltName>
            <endEntityProfileName>profile</endEntityProfileName>
            <certificateProfileName>profile</certificateProfileName>
         </arg0>
      </ws:editUser>
   </soapenv:Body>
</soapenv:Envelope>
EOF

Locale show me this:

LANG=ru_RU.UTF-8
LANGUAGE=
LC_CTYPE="ru_RU.UTF-8"
LC_NUMERIC="ru_RU.UTF-8"
LC_TIME="ru_RU.UTF-8"
LC_COLLATE="ru_RU.UTF-8"
LC_MONETARY="ru_RU.UTF-8"
LC_MESSAGES="ru_RU.UTF-8"
LC_PAPER="ru_RU.UTF-8"
LC_NAME="ru_RU.UTF-8"
LC_ADDRESS="ru_RU.UTF-8"
LC_TELEPHONE="ru_RU.UTF-8"
LC_MEASUREMENT="ru_RU.UTF-8"
LC_IDENTIFICATION="ru_RU.UTF-8"
LC_ALL=

$ echo $LANG shows:

ru_RU.UTF-8

Also terminal output shows cyrillic text without issues or "???". I've also tried to put CN string to the file and use it's content as input for ejbca cli - the same '???'. How could it be? Could you please test it yourself in some playground?