westmc

@lexcao I can no longer seem to reproduce this. It is very odd because it was happening on a test system with an image compiled and created on our build...

BasicAuthHelper.RFC6749.createHeader is calling BasicAuthHelper.createHeader ``` public static abstract class RFC6749 { public static String createHeader(String username, String password) { try { return BasicAuthHelper.createHeader( URLEncoder.encode(username, "UTF-8"), URLEncoder.encode(password, "UTF-8") ); } catch...

We discovered it by using a client that had authorization enabled and when the Keycloak Spring Security client would load, it would make the call out to get a token...

or you can just call this directly... ``` log.info(BasicAuthHelper.RFC6749.createHeader("xxxxx-xxxxxxx-service", "b25b7987-a8ef-49c3-87a0-42a6a37123e6")); ``` it will result in... ``` Basic eHh4eHgteHh4eHh4eC1zZXJ2aWNlOmIyNWI3OTg3LWE4ZWYtNDljMy04N2EwLTQyYTZhMzcxMjNl Ng== ``` instead of ``` Basic eHh4eHgteHh4eHh4eC1zZXJ2aWNlOmIyNWI3OTg3LWE4ZWYtNDljMy04N2EwLTQyYTZhMzcxMjNlNg== ```