CB-08: Use a community login service with campus login servers
Effort and Costs:
Staff Name (Lastname, Firstname)
Effort (person weeks)
Roles or Contributions
launch activity, write design doc & test plan
design doc v1.1
explore/pilot a streamlined process for SPs without a full blown AMIE deployment, either using RabbitMQ or XCDB API
Establish a process for creating, via XRAS, an XSEDE Project, with the PI / Allocation Managers being the appropriate campus IT administrators and an allocation on the single campus login server resource.
Enhance the SSO Hub to recognize researchers on L3 Resource Login Allocations as "allocated users" so it automatically creates their SSO Hub accounts
Enhance the SSO Hub to display and facilitate login to a dynamically configured set of login servers based on SP self registration via RDR and IPF
CB-8: A campus IT administrator allows XSEDE-registered researchers to log in to campus login servers (remote command shell) using their XSEDE usernames/passwords. http://hdl.handle.net/2142/94821
The capability delivery plan for CB-8 (XCI-33) identifies the following functionality gap:
CB-8 specifies that the "solution should not require the campus services to participate in XSEDE allocation processes." However, XSEDE SSO depends heavily on artifacts of the XSEDE allocation process, namely, users associated with active allocations in XCDB with AMIE packets notifying SPs of account/allocation mappings. To close this gap, we implement a new allocation type, called an L3 Resource Login Allocation, that can be easily created and managed by the campus IT administrator, without needing to follow the usual XSEDE allocation processes.
There are comments for XCI-36 that can be viewed with XSEDE authentication.