cancel
Showing results for 
Search instead for 
Did you mean: 
Read only

Backoffice Login: Issue with "German Umlauts"

0 Likes
831

Hello,

we are running hybris 6.4 and are experiencing an issue with the backoffice login page regarding german umlauts like "ä", "ü", "ö" or "ß". Those don't seem to be send to server correctly no matter if we are using standard hybris authentication or ldap authentication. Furthermore using ldap auth will result in a user being locked upon entering the password "incorrectly" after a certain amount of attempts.

How to reproduce:

  • Set a password of a user with access rights to hac and backoffice to e.g. "würtenberg"

  • Login to hmc (works)

  • Login to backoffice (fails, password incorrect)

Did any one else experience this issue yet? Is there maybe a known workaround for the default behavior?

Kind Regards,

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Likes

Hello

There is one solution that might work for you.

  1. go to backoffice/web/webroot/WEB-INF/web-fragments and create encodingFilter folder.

  2. Create a web-fragment.xml file and copy the code from attachment1 into it.

  3. Change web-fragment.xml in backofficefilterchain so it should look like attachment2:

  4. Ant clean all, restart server

Best regards,

Błażej Wcisło

0 Likes

Thanks that worked like a charm! We are running this customization with ant customize overwriting the two xml files until upgrading to an advanced version of hybris.

Answers (3)

Answers (3)

0 Likes

Hello Błażej,
Hello Vyacheslav,

thank you for your response. Any chance we can backport this to 6.4? Unfortunatelly we are currently stuck @6.4 due to the removal of the print extension in newer versions of SAP hybris.

Best Regards,

Former Member
0 Likes

Johannes,

try to apply the solution from this document https://launchpad.support.sap.com/#/notes/2609923

Former Member
0 Likes

Hello,

Pay attention to the task https://jira.hybris.com/browse/ECP-3201, it is very similar for your question.

Former Member
0 Likes

Hello

Apparently, there was a bug in previous versions. It was fixed in 6.7, 1808.

Best regards,

Błażej Wcisło