Details
-
Type: Improvement
-
Status: Closed (View Workflow)
-
Priority: Major
-
Resolution: Done
-
Affects Version/s: None
-
Fix Version/s: None
-
Labels:None
-
Story Points:1
-
Epic Link:
-
Sprint:Fall 6 2021 Oct 25 - Nov 5
Description
Situation: To authorize users to login to CyVerse we use the Terrain OAuth2 authorization endpoint (auth.cyverse.org/cas5/oauth2.0/authorize). The CyVerse team has stated that they are going to use a new endpoint for authenticating users using Keycloak.
Task: Investigate the CyVerse Terrain documentation to identify how we can use the new Keycloak authentication endpoint.
https://de.cyverse.org/terrain/docs/index.html#!/token/get_terrain_token_keycloak
NF: CyVerse has now moved to KeyCloak for user authentication and at some point may stop supporting the current scheme, which we are using. We need to migrate to using KeyCloak.
Question: Do users need to do anything with their accounts? NF: Nothing changed for me, as a user. So probably users are oblivious to the change.