Set up CILogon on our demo Keycloak deployment

[j08lue]

We need CILogon integration since we want to allow users to authenticate with their existing provider.

To test how some of our use cases work in a realistic configuration, we need to add CILogon to our demo setup.

• Stand up instance of vanilla KeyCloak for testing veda-auth-central#122

E.g. delegation of group management

• UC-05: Group membership management #32

Definition of done

• Automate Deployment for Keycloak and Vault with Terraform and CI/CD veda-auth-central#3
• Identify and document User Profile Attributes for VEDA Apps veda-auth-central#11
• CILogon config is purely in this repository, as IaC (with secrets appropriately stored), rather than done via UI

[alukach]

Closed by be03760

[alukach]

The demo Keycloak instance is connected to CILogon as the only authentication provider

@j08lue This is not yet solved but is being tracked in NASA-IMPACT/veda-auth-central#3. I recommend not tracking that feature within this issue.

We restrict the IDPs that are allowed by CILogon to login to this instance. Based on https://cilogon.org/idplist/, I suggest ORCID, GitHub, University of Toronto (because I (Yuvi) have login credentials) and possibly one other university where someone else in the team has login credentials (Georgia Tech?)

@j08lue I think this should also be moved out to a separate (not yet created) issue.

[j08lue]

Actually @yuvipanda wrote these acceptance criteria :-D

Please feel free to refine / move to other tickets.

[alukach]

Marking this as done being that core requirements are complete. NASA-IMPACT/veda-auth-central#11 is still outstanding however I believe we can track that outside of this ticket.