Task #3304
Story #3738: Identity portal enhancements
Upgrade portal to use OAuth for MyProxy (CILogon upgrade)
100%
Description
We are the last group still using CILogon 1.x for client authentication. They have politely asked that we upgrade at our convenience.
The upgrade has changed quite a few thing, most notably it removes the requirement that we tract transactions as the user navigates through the authentication process. This frees us from using postgres for that, but it also means we need to have safe and secure way for sharing the clients' certificates on all three CNs when they have successfully authenticated. We may need to just keep the DB in place since it has been working and communication with it is via TLS.
History
#1 Updated by Ben Leinfelder over 11 years ago
- % Done changed from 0 to 50
Locally, I switched d1_portal_servlet to the newer maven artifacts and refactored as needed. The lingering question is how to best manage and store cert/key pairs for each user...
#2 Updated by Ben Leinfelder over 11 years ago
- Status changed from New to In Progress
- Category set to d1_portal_servlet
#3 Updated by Ben Leinfelder about 11 years ago
Jeff Gaynor has included certificate storage in the next CILogon 2 release and will be assisting me in our upgrade.
#4 Updated by Ben Leinfelder about 11 years ago
- Parent task set to #3738
#5 Updated by Ben Leinfelder almost 11 years ago
- Subject changed from Upgrade portal to use CILogon 2 to Upgrade portal to use OAuth for MyProxy (CILogon upgrade)
#6 Updated by Ben Leinfelder almost 11 years ago
- Status changed from In Progress to Testing
This in trunk/unstable channel and deployed to cn-dev.
#7 Updated by Ben Leinfelder over 10 years ago
- Status changed from Testing to Closed
- translation missing: en.field_remaining_hours set to 0.0
This was installed on the production CNs as part of the CCI 1.2.0 release
