Save cilogon administrative client creds

[GeorgianaElena]

I've filled in the form in https://cilogon.org/oauth2/admin-register (2i2c client name and I used the support email) and it generated this creds. Once the client gets approved we should be able to use them. But until then, let's store them somewhere safe (the old ones will probably become obsolete, but let's keep them both until we figure out the new auth infra ?? )

Ref: #967

[sgibson91]

Hey @GeorgianaElena, this PR will create a conflict with #1027

I suggest:

1. Wait til Secret config refactor and relative path discovery of files in the deployer #1027 is merged
2. Rename shared/deployer/enc-auth0-credentials.secret.yaml to something sensible: shared/deployer/enc-auth-provider-credentials.secret.yaml?
3. Add the CILogon credentials to that file

Does that sound OK?

[GeorgianaElena]

@sgibson91, of course!

[sgibson91]

#1027 is now merged so feel free to update this PR when you have the time :)

[GeorgianaElena]

I've rebased the PR @sgibson91. Also, this new client has recently been approved by CILogon folks 🚀 We just need to figure out how to use it

[sgibson91]

@GeorgianaElena I pushed a commit to update the hard-coded path in the deployer, otherwise this is great - thank you!!

[choldgraf]

Just to confirm - this is embedding the CILogon API credentials in our secrets, so that we could re-use them in subsequent iterations in setting up CILogon with our stack. Is that right? That sounds good to me!

[GeorgianaElena]

@GeorgianaElena I pushed a commit to update the hard-coded path in the deployer, otherwise this is great - thank you!!

Thanks @sgibson91 <3

Just to confirm - this is embedding the CILogon API credentials in our secrets, so that we could re-use them in subsequent iterations in setting up CILogon with our stack. Is that right? That sounds good to me!

Yes! Right now they aren't being used since we're still using the old ones for the current setup.

Thank you both for the review 🎉 hitting the merge button now