ssh ubuntu@connect.bioviz.org

500 Server Error

{"error_code":"ERR_UNCHECKED_EXCEPTION","reason":"java.net.UnknownHostException: cas: Name does not resolve"}

ssh: connect to host connect.bioviz.org port 22: Connection timed out

Hi Sarah and Paul,

I work at the Genome Visualization Lab at UNC Charlotte with Dr. Nowlan Freese and Dr. Ann Loraine for the Bioviz Connect Team. Bioviz Connect is has been down since the last Cyverse maintainence (last week) because when the application attempts to retrieve the access token from CAS, we get the following error:

{"error_code":"ERR_UNCHECKED_EXCEPTION","reason":"java.net.UnknownHostException: cas: Name does not resolve"}

Attempts to restart the Bioviz Connect server did not pan out. I wanted to know if this is an issue from the Terrain API end, specifically the CAS authentication because attempts to use the API directly did not pan out either – kept getting the same error. Please let me know if there is something I can do from my end.

Regards,
Karthik Raveendran

Hi Karthik,

I think I’ve got support for CAS authentication working in Terrain again. Could you give it another try and let us know if it works.

In the long run, we’d like to suggest switching over to Keycloak. Software updates are much easier with Keycloak, so we’d like everyone to migrate if at all possible. We’ll be happy to set up an OpenID Connect client for you in Keycloak if and when you decide to migrate.

Best,
Sarah

Hi Karthik,
It appears that CAS is running, but I do see the error that you’re encountering when I try to call the token endpoint. We can look into that, but I’d like to suggest moving to Keycloak if that’s possible for you? If you’re obtaining tokens from Terrain then you can append /keycloak to the end of the URL to have Terrain attempt to get the Token from Keycloak instead, for example:
$ curl -su sarahr "https://de.cyverse.org/terrain/token/keycloak"
If BioViz is authenticating using CAS then migrating to Keycloak would be more involved because it would have to be updated to use OpenID Connect rather than the CAS protocol for authentication.
I’ll try to dig into the problem today and let you know if I make any headway.
Best,
Sarah