You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We've had multiple occurrences of users not being able to log in via the API, because their username contained non-ASCII characters. See the following Shopware JIRA Issue as well: https://issues.shopware.com/issues/SW-15358
As there is no realistic way to fix this, we should implement a special validation in the Shopware backend user administration which only allows ASCII characters in the username when the API key (and therefore API access) is activated:
The text was updated successfully, but these errors were encountered:
samuelvogel
added
bug
Issues that describe an unexpected behaviour in an existing functionality.
minor
"bug" issues that are neither "critical" nor "major".
labels
Nov 21, 2017
We've had multiple occurrences of users not being able to log in via the API, because their username contained non-ASCII characters. See the following Shopware JIRA Issue as well: https://issues.shopware.com/issues/SW-15358
Unfortunately this is deeply buried inside the Zend Framework 1 which is shipped with Shopware: https://github.com/zendframework/zf1/blob/a90f3a8d71e0788020f730da83674b7312bd3b16/library/Zend/Auth/Adapter/Http.php#L527-L532
The ctype_print function is used to check the base64-decoded
Authorization
header for non-ASCII characters. See here fore the referenced ticket ZF-1253: https://framework.zend.com/issues/browse/ZF-1253As there is no realistic way to fix this, we should implement a special validation in the Shopware backend user administration which only allows ASCII characters in the username when the API key (and therefore API access) is activated:
The text was updated successfully, but these errors were encountered: