Network authentication service allows the iSeries™ server and several iSeries services, such as iSeries eServer™ Access for Windows®, to use a Kerberos ticket as an optional replacement for a user name and password for authentication.
A user authenticates with a principal and a password that is stored in the Kerberos server. Once a principal is authenticated, the Kerberos server issues a ticket-granting ticket (TGT) to the user. When a user needs access to an application or service on the network, the Kerberos client application on the user's PC sends the TGT back to the Kerberos server to obtain a service ticket for the target service or application. The Kerberos client application then sends the service ticket to the service or application for authentication. Once the service or application accepts the ticket a security context is established and the user's application can then exchange data with a target service. Applications can authenticate a user and securely forward his or her identity to other services on the network. Once a user is known, separate functions are needed to verify the user's authorization to use the network resources.
Network authentication service implements the following specifications:
i5/OS™ implementation of network authentication service operates with authentication, delegation, and data confidentiality services compliant with these RFCs and Microsoft's Windows 2000 Security Service Provider Interface (SSPI) APIs. Microsoft® Windows Active Directory uses Kerberos as its default security mechanism. When users are added to Microsoft Windows Active Directory, their Windows identification is equivalent to a Kerberos principal. Network authentication service provides for interoperability with Microsoft Windows Active Directory and its implementation of the Kerberos protocol.