IBM BS029ML Self Help Guide - Page 52

Single Sign-On (SSO), Out-of-the-box SSO with WebSphere Portal Server

Page 52 highlights

External Security Managers also address much larger problems, such as enterprise SSO (Single Sign-On), complex authentication, and centralized authorization. 2.6.3 Single Sign-On (SSO) Single Sign-On (SSO) is the term used to describe a system or mechanism where users need to undergo a minimum number of explicit authentication steps in order to be given access to multiple systems or services. SSO enhances user convenience by automating access to all authorized servers and services through a single authentication process. This capability eliminates the need to remember multiple sign-on processes, user IDs, or passwords. Moreover, by this single action, user authentication errors are reduced. The purpose of SSO is to: Provide a SSO capability for all Web-based applications. A user should only need to log in one time to one entity to obtain access to all authorized applications and content, which may reside on various servers. Provide a centralized point of authentication, generating a valid credential (ticket, cookie, and so on). Remove the need for application developers to specifically authenticate users within their application code. The intricacies of security can be abstracted from such applications. Provide a cross-platform security solution. Experience has shown that there is a need to maintain operating system independence for Web-based application security. Provide the ability to control access to Web applications and content, which may be hosted through multiple Web servers, at the URL level. Provide the ability to make fine-grained authorization decisions within applications. While this is not an immediate deployment requirement, the solution must allow for this capability to be added. Support browser based access to applications from both customers and employees. From their desks, internal users may access both internet-hosted applications and internal applications. At this time, there is no requirement for employees to have access to internal applications from the internet. What SSO is not: An Identity Management Solution. A Federated Identity Management Solution. Out-of-the-box SSO with WebSphere Portal Server WebSphere Portal Server, or rather the underlying WebSphere Application Server instance, provides SSO functionality out-of-the-box. However, it is important to understand the capabilities and constraints associated with such a deployment. This statement is made in as much that the out-of-the-box SSO functionality may be insufficient for some enterprise-wide implementations, but also in the context that the adoption of an External Security Manager may simply be overkill. Key points to note about the out-of-the-box SSO provided with WebSphere Portal Server are: SSO is based on the Lightweight Third-Party Authentication (LTPA) token, which is an IBM proprietary standard. It is suitable for achieving SSO between WebSphere and Domino based products only. 38 IBM WebSphere Portal V6 Self Help Guide

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
  • 147
  • 148
  • 149
  • 150
  • 151
  • 152
  • 153
  • 154
  • 155
  • 156
  • 157
  • 158
  • 159
  • 160
  • 161
  • 162
  • 163
  • 164
  • 165
  • 166
  • 167
  • 168
  • 169
  • 170
  • 171
  • 172
  • 173
  • 174
  • 175
  • 176
  • 177
  • 178
  • 179
  • 180
  • 181
  • 182
  • 183
  • 184
  • 185
  • 186
  • 187
  • 188
  • 189
  • 190
  • 191
  • 192
  • 193
  • 194
  • 195
  • 196
  • 197
  • 198
  • 199
  • 200
  • 201
  • 202
  • 203
  • 204
  • 205
  • 206
  • 207
  • 208
  • 209
  • 210
  • 211
  • 212
  • 213
  • 214
  • 215
  • 216
  • 217
  • 218
  • 219
  • 220
  • 221
  • 222
  • 223
  • 224
  • 225
  • 226
  • 227
  • 228
  • 229
  • 230
  • 231
  • 232
  • 233
  • 234
  • 235
  • 236
  • 237
  • 238
  • 239
  • 240
  • 241
  • 242

38
IBM WebSphere Portal V6 Self Help Guide
External Security Managers also address much larger problems, such as enterprise SSO
(Single Sign-On), complex authentication, and centralized authorization.
2.6.3
Single Sign-On (SSO)
Single Sign-On (SSO) is the term used to describe a system or mechanism where users need
to undergo a minimum number of explicit authentication steps in order to be given access to
multiple systems or services. SSO enhances user convenience by automating access to all
authorized servers and services through a single authentication process. This capability
eliminates the need to remember multiple sign-on processes, user IDs, or passwords.
Moreover, by this single action, user authentication errors are reduced.
The purpose of SSO is to:
±
Provide a SSO capability for all Web-based applications. A user should only need to log in
one time to one entity to obtain access to all authorized applications and content, which
may reside on various servers.
±
Provide a centralized point of authentication, generating a valid credential (ticket, cookie,
and so on).
±
Remove the need for application developers to specifically authenticate users within their
application code. The intricacies of security can be abstracted from such applications.
±
Provide a cross-platform security solution. Experience has shown that there is a need to
maintain operating system independence for Web-based application security.
±
Provide the ability to control access to Web applications and content, which may be
hosted through multiple Web servers, at the URL level.
±
Provide the ability to make fine-grained authorization decisions within applications. While
this is not an immediate deployment requirement, the solution must allow for this capability
to be added.
±
Support browser based access to applications from both customers and employees. From
their desks, internal users may access both internet-hosted applications and internal
applications. At this time, there is no requirement for employees to have access to internal
applications from the internet.
What SSO is not:
±
An Identity Management Solution.
±
A Federated Identity Management Solution.
Out-of-the-box SSO with WebSphere Portal Server
WebSphere Portal Server, or rather the underlying WebSphere Application Server instance,
provides SSO functionality out-of-the-box. However, it is important to understand the
capabilities and constraints associated with such a deployment. This statement is made in as
much that the out-of-the-box SSO functionality may be insufficient for some enterprise-wide
implementations, but also in the context that the adoption of an External Security Manager
may simply be overkill.
Key points to note about the out-of-the-box SSO provided with WebSphere Portal Server are:
±
SSO is based on the Lightweight Third-Party Authentication (LTPA) token, which is an IBM
proprietary standard. It is suitable for achieving SSO between WebSphere and Domino
based products only.