TL;DR: The authors concentrate on authentication for real-time, interactive services that are offered on computer networks, which includes remote login, file system reads and writes, and information retrieval for applications like Mosaic.
Abstract: When using authentication based on cryptography, an attacker listening to the network gains no information that would enable it to falsely claim another's identity. Kerberos is the most commonly used example of this type of authentication technology. The authors concentrate on authentication for real-time, interactive services that are offered on computer networks. They use the term real-time loosely to mean that a client process is waiting for a response to a query or command so that it can display the results to the user, or otherwise continue performing its intended function. This class of services includes remote login, file system reads and writes, and information retrieval for applications like Mosaic. >
TL;DR: This document describes a protocol for carrying authentication, authorization, and configuration information between a Network Access Server which desires to authenticate its links and a shared Authentication Server.
Abstract: This document describes a protocol for carrying authentication, authorization, and configuration information between a Network Access Server which desires to authenticate its links and a shared Authentication Server.
TL;DR: This document describes an updated version of the IP Authentication Header (AH), which is designed to provide authentication services in IPv4 and IPv6, and obsoletes RFC 2402 (November 1998).
Abstract: This document describes an updated version of the IP Authentication
Header (AH), which is designed to provide authentication services in
IPv4 and IPv6. This document obsoletes RFC 2402 (November 1998).
[STANDARDS-TRACK]
TL;DR: In this paper, a computer system (200) is used to authenticate users of vendors supplying services and/or products to the users, the system having programmed processors providing authentication rules (245a), authenticating users according to the authentication rules responsive to user authentication requests (300), configuring authentication rules in real-time, thereby allowing realtime customization of the system, providing multi-factor user authentication processes (100), using any data sources (230/250) providing information about and or known to users, thereby providing a data agnostic system, and authentication strategies correspond to
Abstract: A computer system (200) to authenticate users of vendors supplying services and/or products to the users, the system having programmed processors providing authentication rules (245a), authenticating users according to the authentication rules responsive to user authentication requests (300), configuring the authentication rules in real-time, thereby allowing real-time customization of the system, providing multi-factor user authentication processes (100), using any data sources (230/250) providing information about and/or known to the users to authenticate the users, thereby providing a data agnostic system, and authentication strategies correspond to the authentication rules, thereby allowing the system to support authentication strategy experimentation.
TL;DR: In this article, the authors propose a single sign-on system for authentication of mobile device applications using a native, independent browser using a single-signon system, where an authentication module within the mobile application can direct the mobile device's native browser to a URL to initiate authentication with an authentication appliance.
Abstract: Features are disclosed for authentication of mobile device applications using a native, independent browser using a single-sign-on system. An authentication module within the mobile application can direct the mobile device's native browser to a URL to initiate authentication with an authentication appliance. The mobile browser can receive and store a browser-accessible token to indicate previous authentication performed by the user. The mobile application can receive from the application appliance and store a client application ID token that may be presented to network services for access. A second mobile device application may direct the same browser to the authentication appliance. The authentication appliance may inspect the persistent browser-accessible token and issue a second client application ID identity to the second application without collecting additional authentication information, or collecting additional authentication information that is different from the first authentication information.