Contents

Identity and Authentication
===========================

Users can be identified in any number of ways and carry with them various
attributes that determine the entirety of "who they are". Our typical needs
include identifying a person by username or email address, and building a
profile of attributes such as geographical region (as determined by IP address),
or University status (student, staff, etc.). The identifiers and attributes are
intrinsic to the user and do not, by themselves, grant any permissions within
an application. Likewise, these attributes cannot be granted within an
application, only inspected.

A&E will continue to provide the identity and attributes of users. The
specifics of whether this will be implemented with environment variables,
HTTP headers, SAML, or other means is to be determined. An application is
not expected to implement its own login process except to the degree that
it can recognize the required authentication information provided to it.

Version data entries

4 entries across 4 versions & 1 rubygems

Version	Path
checkpoint-1.0.3	docs/authentication.rst
checkpoint-1.0.2	docs/authentication.rst
checkpoint-1.0.1	docs/authentication.rst
checkpoint-1.0.0	docs/authentication.rst