The Known Issue re: "Authorization token is missed" is somewhat vague and leaves interpretation to the user. We could flesh this out a bit.

Some feedback from the field:

You would think such a simple statement would be easy "add the self-signed TLS certificate to the browser". Which I did with no luck earlier today. So turns out you also have to go to keycloak and accept that cert as well or I would get the same result on login. Using two browsers I neglected to go to keycloak in firefox and accept that cert as well.

And...

*Also for the terminal error "connection failed with terminal - some error happened with the terminal websocket connection"
In the logs I see Firefox can’t establish a connection to the server at wss://route76gt0nv6-cr-project.apps.ocp.demo.....

so similarly browsing to https://route76...... and adding that cert fixed the terminal issue.

So I guess with self signed certs there are a few to accept post deploy to get it all working.

– from rstarr@redhat.com