When a user with a whitespace character (i.e. my username) in their username logs in, an account is successfully created and they will be able to access the Simphony-Remote dashboard. However, application containers will not be properly deployed / connected to.
Unfortunately there is not a very verbose error traceback - in the logs we typically get something like:
Code: 500 Server at http://127.0.0.1:49164/user/my%20username/containers/my-container/ didn't respond in 30 seconds
This is particularly an issue when supporting OAuth2 login flow, since we don't have control over the username that is returned from the Identity provider. It is then left up to on the Authenticator class to handle the returned username appropriately, but this component is configurable and may be contributed by a 3rd-party.
In short, we should either fully support usernames with whitespace or better document that we do not.
When a user with a whitespace character (i.e.
my username) in their username logs in, an account is successfully created and they will be able to access the Simphony-Remote dashboard. However, application containers will not be properly deployed / connected to.Unfortunately there is not a very verbose error traceback - in the logs we typically get something like:
This is particularly an issue when supporting OAuth2 login flow, since we don't have control over the username that is returned from the Identity provider. It is then left up to on the
Authenticatorclass to handle the returned username appropriately, but this component is configurable and may be contributed by a 3rd-party.In short, we should either fully support usernames with whitespace or better document that we do not.