Checks whether a valid token is provided in the request before serving environment routes.
Bug: T350915
Looks good! At this point, once we know that the token is valid (i.e. the signature is correct), we should make sure the token isn't expired (make sure the timestamp in the exp field of the JWT is not less than the current Unix timestamp). And, eventually, we'll have to check to see if the user is authorized to use catalyst. For the time being, we could do that by seeing if the JWT contains the group "project-catalyst" in the groups array.
Cicalese (28011d6c) at 19 Dec 15:00
fix typo
Cicalese (870fe4f7) at 19 Dec 14:57
accept either GET or POST for login
Cicalese (dbfb2e7c) at 18 Dec 20:29
Cicalese (dbfb2e7c) at 18 Dec 20:23
remove unnecessary code
Cicalese (ccd929ec) at 18 Dec 20:08
Cicalese (ccd929ec) at 18 Dec 20:07
add /auth to other routes
Update the login path since the auth server url has changed to catalyst.wmcloud.org/auth
Cicalese (2bd75299) at 18 Dec 14:55
change ingress hostname
Cicalese (a00cd9c0) at 18 Dec 14:28
Cicalese (a00cd9c0) at 18 Dec 14:28
change auth server ingress to path
Cicalese (a00cd9c0) at 16 Dec 21:37
change auth server ingress to path
Cicalese (097e3ddd) at 14 Dec 18:40
Cicalese (097e3ddd) at 14 Dec 18:19
fix missing $