{"action":"opened","issue":{"url":"https://api.github.com/repos/jupyterhub/oauthenticator/issues/210","repository_url":"https://api.github.com/repos/jupyterhub/oauthenticator","labels_url":"https://api.github.com/repos/jupyterhub/oauthenticator/issues/210/labels{/name}","comments_url":"https://api.github.com/repos/jupyterhub/oauthenticator/issues/210/comments","events_url":"https://api.github.com/repos/jupyterhub/oauthenticator/issues/210/events","html_url":"https://github.com/jupyterhub/oauthenticator/issues/210","id":354318054,"node_id":"MDU6SXNzdWUzNTQzMTgwNTQ=","number":210,"title":"Normalization of user names due to 404 error on worker (GoogleAuth)","user":{"login":"h4gen","id":12556763,"node_id":"MDQ6VXNlcjEyNTU2NzYz","avatar_url":"https://avatars1.githubusercontent.com/u/12556763?v=4","gravatar_id":"","url":"https://api.github.com/users/h4gen","html_url":"https://github.com/h4gen","followers_url":"https://api.github.com/users/h4gen/followers","following_url":"https://api.github.com/users/h4gen/following{/other_user}","gists_url":"https://api.github.com/users/h4gen/gists{/gist_id}","starred_url":"https://api.github.com/users/h4gen/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/h4gen/subscriptions","organizations_url":"https://api.github.com/users/h4gen/orgs","repos_url":"https://api.github.com/users/h4gen/repos","events_url":"https://api.github.com/users/h4gen/events{/privacy}","received_events_url":"https://api.github.com/users/h4gen/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":0,"created_at":"2018-08-27T13:25:50Z","updated_at":"2018-08-27T13:25:50Z","closed_at":null,"author_association":"NONE","body":"I ran into an error which caused the hub to show an 404 page after the spawner tried to redirect to the notebook instance on the worker. I used google authentication but I guess it can happen for every kind of authentication. I do not know what exactly caused the error on the hub side but I figured out that the problem was caused by special characters in the user name. In this case the user names had the format xxx.xxx@company.com leading to user names xxx.xxx  on the hub. This seems to be a problem if oauthenticator is used but not if in development mode with no authentication. I ended up using the `c.Authenticator.username_map()` to normalize the user names. This works pretty well. Maybe this should be documented somewhere."}}
{"actor":{"display_login":"h4gen"}}