Using Ichain For Authentication; Using Novell Access Manager For Authenticating To Teaming Or Conferencing - Novell GROUPWISE 8 - INTEROPERABILITY Manual

4c Select the type of access you want to provide for users to view the URL: Secure,
Restricted, or Public.
4d Click OK to save the new protected resource.
5 Select the new protected resource, then click the Parameters icon to display the OLAC
Parameters dialog box.
5a In the Name column, specify
5b In the Data Source column, specify
5c In the Value column, specify
These settings add an extended HTTP request header called X-Authorization that stores
each user's cn (common name). The cn is retrieved from the LDAP server by the iChain
OLAC process so that users can log in automatically.
5d Click OK to save the OLAC parameters.
6 When prompted, click Yes to refresh the iChain proxy configuration with the new changes.
7 Provide the password to the proxy server, then click OK to perform the refresh operation
immediately.

25.1.4 Using iChain for Authentication

Now that you have created an iChain Web server accelerator for Teaming or Conferencing and have
configured the iChain Server object for the new Web server accelerator, users should be able to
authenticate to Teaming or Conferencing in a single step, using their eDirectory or LDAP
passwords.
25.2 Using Novell Access Manager for
Authenticating to Teaming or Conferencing
Novell Access Manager is not currently supported for use with Novell Teaming or Conferencing.
.
Authorization
.
ldap
.
cn
Streamlining Authentication to Teaming or Conferencing 247