[#XCI-205] Identify user X.509 credential assurance use cases and how to maintain them with OpenID
Project: XSEDE Cyberinfrastructure Integration
CILogon, Globus Auth
PY8 (Sep '18 - Aug '19), PY9 (Sep '19 - Aug '20)
XCI Engineering Analysis
Associated bugs and stories
Security Token Assurance for Authenti...
is deliverable of
Impact Analysis: Support for open sou...
XSEDE Enterprise Services
XSEDE Priority: -
Public activity link:
CAN-06: Authenticate with an application, CAN-09: Establish and manage a community identity
Effort and Costs:
Staff Name (Lastname, Firstname)
Effort (person weeks)
Roles or Contributions
two weeks of effort to lead the activity (required)
two weeks of effort to provide input to engineering analysis and coordinate with TAGPMA
two weeks of effort to provide input to engineering analysis, coordinate with Globus, and help with use case analysis
Implemented Software Capability
Other type of deliverable
TRR Baseline* (Shava)
Deployment Baseline* (Shava)
Test Report* (Shava)
Click on "Deliverables" tab for URL.
Planned Launch Date:
Actual Launch Date:
Planned Design Review Date:
Planned Complete Date:
XSEDE's accepted certificate authorities and related policies and procedures provide a certain level of assurance for user's X.509 credentials. We need to identify the use cases behind this credential assurance and identify how we will maintain or improve that assurance when users use OpenID credentials.
There are comments for
XCI-205 that can be viewed with XSEDE authentication.