Single Sign-On

Single sign-on 1 Single sign-on (SSO) is a property of access control of multiple related, but independent software systems. With this property a user logs in once and gains access to all systems without being prompted to log in again at each of them. Conversely, single sign-off is the property whereby a single action of signing out terminates access to multiple software systems.

Single sign-on 1 As different applications and resources support different authentication mechanisms, single sign-on has to internally translate to and store different credentials compared to what is used for initial authentication.

Single sign-on - Criticisms 1 The term enterprise reduced sign-on is preferred by some authors who believe single sign-on to be impossible in real use cases.

Single sign-on - Criticisms 1 As single sign-on provides access to many resources once the user is initially authenticated ("keys to the castle") it increases the negative impact in case the credentials are available to other persons and misused. Therefore, single sign-on requires an increased focus on the protection of the user credentials, and should ideally be combined with strong authentication methods like smart cards and one-time password tokens.

Single sign-on - Criticisms 1 Single sign-on also makes the authentication systems highly critical; a loss of their availability can result in denial of access to all systems unified under the SSO. SSO can thus be undesirable for systems to which access must be guaranteed at all times, such as security or plant-floor systems.

Single sign-on - Smart card based 1 Initial sign-on prompts the user for the smart card. Additional software applications also use the smart card, without prompting the user to re-enter credentials. Smart card-based single sign- on can either use certificates or passwords stored on the smart card.

Single sign-on - Security Assertion Markup Language 1 The user is called the subject in the SAML-based single sign-on

Single sign-on - Shared authentication schemes which are not single sign-on 1 Single sign-on requires that users literally sign in once to establish their credentials. Systems which require the user to log in multiple times to the same identity are inherently not single sign-on. For example, an environment where users are prompted to log into their desktop, then log into their using the same credentials, is not single sign-on.

Security token - Single sign-on software tokens 1 Some types of Single sign-on (SSO) solutions, like enterprise single sign-on, use the token to store software that allows for seamless authentication and password filling. As the passwords are stored on the token, users need not remember their passwords and therefore can select more secure passwords, or have more secure passwords assigned.

SAPgui - Single sign-on 1 SAPGUI on Microsoft Windows or Internet Explorer can also be used for single sign-on. There are several portal-based authentication applications for single sign-on. SAPGUI can have single sign-on with SAP Logon Ticket as well. Single sign-on also works in the Java GUI.[ s_in_the_SAP_GUI_for_Java.html Single Sign-on for SAP Java GUI]

SAP NetWeaver Process Integration - Single Sign-On 1 SAP NetWeaver PI allows for Single Sign-On through SAP Logon Tickets[ /en/32/1c1041a0f6f16fe a1550b0/fr ameset.htm Single Sign-On Configuration - Procedure for PI Web Components] and x.509 certificates. Certificates allow for the usage of Secure Network Communications (SNC) and Secure Socket Layer (SSL).

SAP Logon Ticket - Single Sign-On 1 SAP Logon Tickets can be used for single sign-on through the SAP Enterprise Portal. SAP provides a Web Server Filter that can be used for an authentication via http header variable and a Dynamic Link Library for verifying SSO Tickets in 3rd party software which can be used to provide native support for SAP Logon Tickets in applications written in C or Java.

SAP Logon Ticket - Single Sign-On to Microsoft Web Applications 1 This new ISAPI Filter requests a constrained Kerberos ticket for users identified by valid SAP Logon Ticket that can be used for SSO to Microsoft web based applications in the back end.[ troot/docs/library/uuid/47d0cd c86- f81b1c812e50?QuickLink=indexoverridela yout=true Using SAP Logon Tickets for Single Sign-On]

SAP XI - Single Sign-On 1 SAP NetWeaver PI allows for Single Sign- On through SAP Logon Tickets[ ata/en/32/1c1041a0f6f16fe a155 0b0/frameset.htm Single Sign-On Configuration - Procedure for PI Web Components] and x.509 certificates. Certificates allow for the usage of Secure Network Communications (SNC) and Secure Socket Layer (SSL).

Public key infrastructure - Temporary certificates and single sign-on 1 This approach involves a server that acts as an online certificate authority within a single sign-on system. A single sign-on server will issue digital certificates into the client system, but never stores them. Users can execute programs, etc. with the temporary certificate. It is common to find this solution variety with X.509-based certificates.Single Sign-On Technology for SAP Enterprises: What does SAP have to say? [

Univention Corporate Server - Single sign-on 1 With help of the identity provider, a single sign-on functionality for third party web services and applications (e.g., Google Apps, Salesforce.com etc.) can be realized while the authentication is done at the identity provider itself

For More Information, Visit: m/the-single-sign-on- toolkit.html m/the-single-sign-on- toolkit.html The Art of Service