Today, we ask people to submit an "account request" but also require them to authenticate during this process with an organizational credential. I propose that we change to a model where you always log into the portal with an organizational credential, and from there can request authorization to use RC resources. This would further support moving to OAuth or a similar authentication mechanism to handle authentication at the home institution, rather than proxied through us. (We'll need to do this to support XSEDE users, anyway.)
This encourages users to engage with RCAMP as a holistic portal from the beginning, and would support removing the workflow documentation from the website in favor of minimal pointers in the portal application itself.
Today, we ask people to submit an "account request" but also require them to authenticate during this process with an organizational credential. I propose that we change to a model where you always log into the portal with an organizational credential, and from there can request authorization to use RC resources. This would further support moving to OAuth or a similar authentication mechanism to handle authentication at the home institution, rather than proxied through us. (We'll need to do this to support XSEDE users, anyway.)
This encourages users to engage with RCAMP as a holistic portal from the beginning, and would support removing the workflow documentation from the website in favor of minimal pointers in the portal application itself.