When running on Openshift and using the oauth-proxy, the UI does not receive a user id, but does receive a token. Job processing for command actions requires a user id to identify ownership so the UI can display only the jobs that belong to the current user. The token needs to be converted to a user id by calling the oauth server.
cvignola
commented
4 years ago
When running on Openshift and using the oauth-proxy, the UI does not receive a user id, but does receive a token. Job processing for command actions requires a user id to identify ownership so the UI can display only the jobs that belong to the current user. The token needs to be converted to a user id by calling the oauth server.