Details
-
Type:
Task
-
Status: Closed (View Workflow)
-
Priority:
Major
-
Resolution: Done
-
Affects Version/s: None
-
Fix Version/s: None
-
Labels:None
-
Story Points:0.5
-
Epic Link:
-
Sprint:Summer 2 2023 May 29, Summer 3 2023 June 12
Description
Recommends restarting the server.
Attachments
Activity
After the EC2 instance was restarted, Bioviz Connect still seems to throw 500 error. Used postman to test if the Terrain APIs are working and the 'Retrieve Bearer Token' API threw the following error, which is an uncaught error in the Cyverse API:
500 Server Error
{"error_code":"ERR_UNCHECKED_EXCEPTION","reason":"java.net.UnknownHostException: cas: Name does not resolve"}
'UnknownHostException indicates that the IP address of a hostname could not be determined. It can happen because of a typo in the hostname'. In this case, it seems like CAS is not recognized.
I was not able to connect using ssh ubuntu@connect.bioviz.org:
ssh: connect to host connect.bioviz.org port 22: Connection timed out
When we go to Bioviz Connect in the browser, the error message page, shown in the attached image, is served by bioviz connect server. Seeing that we have not changed Bioviz Connect code base in a while and the postman API call is not working either, I feel like this is probably a CAS issue and we may need to address this issue to the Cyverse Team.
After restarting the server multiple times, the 500 error did not resolve. The 'Retrieve Bearer Token' API still throws the above error. I am going to send a mail to the Cyverse team.
Email that was sent to Sarah Roberts and Paul Sarando:
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
RE: [EXTERNAL] Re: Questions regarding CyVerse Terrain API and CAS authentication
6/13/2023
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
RE: [EXTERNAL] Re: Questions regarding CyVerse Terrain API and CAS authentication
6/13/2023
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
Bioviz Connect is up and running after the support for CAS was provided by the Cyverse Team
To log: