Skip to main content link. Accesskey S
  • HCL Logo
  • HCL Notes and Domino wiki
  • THIS WIKI IS READ-ONLY. Individual names altered for privacy purposes.
  • HCL Forums and Blogs
  • Home
  • Product Documentation
  • Community Articles
  • Learning Center
  • API Documentation
Search
Community Articles > Lotus Domino > Domino security > Sametime Server 8.5.2 - IFR1 (Single Sign on)
  • Share Show Menu▼
  • Subscribe Show Menu▼

Recent articles by this author

Sametime Server 8.5.2 - IFR1 (Single Sign on)

This article provides information on Simple and Protected GSS-API Negotiation (SPNEGO) and its use in a Lotus® Sametime® 8.5.x environment, while keeping Linux platform

Configuring SPNEGO authentication with IBM Lotus Sametime 8.5.2 - IFR1

This article provides information on Simple and Protected GSS-API Negotiation (SPNEGO) and its use in a Lotus® Sametime® 8.5.x environment, while keeping Linux platform
Community articleSametime Server 8.5.2 - IFR1 (Single Sign on)
Added by ~Emile Umfooverobu | Edited by ~Wendy Quethipilyynds on August 7, 2012 | Version 11
  • Actions Show Menu▼
expanded Abstract
collapsed Abstract
This article provides information on Simple and Protected GSS-API Negotiation (SPNEGO) and its use in a Lotus® Sametime® 8.5.x environment, while keeping Linux platform
Tags: Single Sign On
ShowTable of Contents
HideTable of Contents
  • 1 Introduction

Introduction

Authentication
As described in the IBM Redbooks® publication, WebSphere® Application Server V7.0: Concepts, Planning,
and Design:
Authentication is the process of identifying who is requesting access to a resource. For the
authentication process, the server implements a challenge mechanism to gather unique information
to identify the client. Secure authentication can be knowledge-based (user and password), key-based
(physical keys, encryption keys), or biometric (fingerprints, retina scan, DNA, and so forth).
The authentication mechanism in WebSphere Application Server typically collaborates closely with a
user registry. When performing authentication, the user registry is consulted. A successful
authentication results in the creation of a credential, which is the internal representation of a
successfully authenticated client user. The abilities of the credential are determined by the
configured authorization mechanism


  • Actions Show Menu▼


expanded Attachments (0)
collapsed Attachments (0)
Edit the article to add or modify attachments.
expanded Versions (1)
collapsed Versions (1)
Version Comparison     
VersionDateChanged by              Summary of changes
This version (11)Aug 7, 2012, 3:15:37 PM~Wendy Quethipilyynds  
expanded Comments (0)
collapsed Comments (0)
Copy and paste this wiki markup to link to this article from another article in this wiki.
Go ElsewhereStay ConnectedAbout
  • HCL Software
  • HCL Digital Solutions community
  • HCL Software support
  • BlogsDigital Solutions blog
  • Community LinkHCL Software forums and blogs
  • About HCL Software
  • Privacy
  • Accessibility