Executive Summary: An application or science gateway (hereafter referred to as the “application”) needs to retrieve non-public, user-specific information from a remote service. For example, to help a researcher manage his/her HPC jobs, an application needs to retrieve the researcher’s current job status information (which is private). As a second example, to help a researcher customize his/her user profile, an application needs to retrieve the researcher’s profile, which may contain private fields.
|Component||User facing?||Component’s role in the capability|
|Globus Auth||yes||Provides the ability for the user to authenticate using XSEDE-accepted credentials (including federated identity providers) to the application and to the remote service before granting the application access to the remote service on the user's behalf.|
|Information Services||yes||Is the remote service that provides an API for accessing user specific information, like the user jobs running on XSEDE resources and user profile information.|
|Service Provider Batch Processing Services||no||An example of a service where that produces user information that is accessible thru the remote service.|
|XSEDE Central Database||no||An example of a service where that has user information that is accessible thru the remote service.|