Electronic Federated Identity (EFI) Sign-on Service

DESCRIPTION
Electronic Federated Identity (EFI) Service uses UCF federated login services to
authenticate UCF users to on-site and contractual partnered (cloud) services via the
central username directory.
UCF uses Shibboleth software to host an Identity Provider (IdP) capable of
authenticating users against the central directory using their NID and NID password.
Once authenticated, the IdP sends the userID back to the application along with any
unique computed value(s) or an attribute(s) from the directory. Applications can use
these attributes to identify the type of user authenticating to the system.

Once a user authenticates using EFI, they will be able to log into other Service Providers
(SP) defined in the IdP without an additional login (timeout limited).

FUNCTIONALITY LIST
Allows for central signon authentication based on the central NID directory.

TECHNICAL SPECIFICATIONS
The service uses SAML2 version, or higher, assertions to pass NET domain NID
authentication information to the application. The most compatable Service Provider
can be implemented with the Shibboleth SP open source code. Information about the
Shibboleth SP can be found at http://shibboleth.internet2.edu/documentation.html.

INCLUDED SERVICE COMPONENTS – OVERVIEW:
Connection to the Identity Provider (IdP) Interface for web applications.

OPTIONAL SERVICE COMPONENTS – OVERVIEW:
UCF is a member of the InCommon Federation. As an option Service Provider (SP)
metadata for an application set up to authenticate to UCF IdP can be published to
InCommon to be added to the federation metadata. This would allow the application to
accept authentication from any IdP in the InCommon Federation.