You can use Novell iChain to eliminate a dual user login into your network and into Vibe. The instructions in this section assume that you have an understanding of iChain, as described on the Novell iChain 2.3 Documentation Web site and that you have iChain set up and running on your system.
There are many ways to configure iChain. This section illustrates one possible way to configure iChain to support Vibe. Before following the steps in this section, you must have Vibe, as well as iChain, installed, configured, and running.
In order to get the best performance and reliability from iChain with Vibe, you must install iChain 2.3 Support Pack 5 Release 4 version 2.3.410. This software is available on the iChain tab on the Novell Downloads Web site. Follow the installation instructions that are provided with the patch.
Access the iChain Proxy Administration Tool at the following URL:
http://proxy_server_address:port/appliance/config.html
Click , then click to create a new Web server accelerator for Vibe.
The new accelerator is enabled by default.
In the field, provide a unique and descriptive name for the new accelerator.
For example, you might want to call it Vibe.
Select .
Select .
In the Multi-Homing Options dialog box, select to configure the Vibe URL as a DNS name prepended to your Internet domain name, for example:
http://vibe.yourcompanyname.com
The A record for the DNS name must already exist. The Proxy Administration Tool does not create it for you.
In the field, specify the DNS A record.
Click to save your multi-homing settings.
If you have created a custom login page for your Vibe Web site, specify it in the field.
The default location for custom login pages is sys:\etc\proxy\data. The custom login page must be an HTML file with a .htm extension. If it is located in a directory other than the default, specify the full pathname for the file.
Select .
In the field on the right, specify the port number that the iChain proxy server should use to communicate with the Web server where Vibe is installed.
If desired, select .
Click to save your secure exchange options.
Under the Web Server Addresses box, click .
Specify the IP address or DNS hostname of the Web server where you have installed Vibe.
Click to add the Web server to the list in the Web Server Accelerator dialog box.
Click to save the new Web server accelerator.
Continue with Adding the New Web Server Accelerator to the iChain Server Object in ConsoleOne.
Start ConsoleOne in a location where the iChain snap-ins are installed.
Browse to and right-click the iChain Server object, then click .
Click to display a list of protected resources.
Click the icon to add a new protected resource.
In the field, provide a unique and descriptive name for the new protected resource, which is the Web server accelerator.
In the field, specify the part of the URL that precedes the application-specific part of the URL; for example:
vibe.yourcompanyname.com/*
Select the type of access you want to provide for users to view the URL: , , or .
Click to save the new protected resource.
Select the new protected resource, then click the icon to display the OLAC Parameters dialog box.
In the column, specify Authorization.
In the column, specify ldap.
In the column, specify cn.
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.
Click to save the OLAC parameters.
When prompted, click to refresh the iChain proxy configuration with the new changes.
Provide the password to the proxy server, then click to perform the refresh operation immediately.
Now that you have created an iChain Web server accelerator for Vibe and have configured the iChain Server object for the new Web server accelerator, users should be able to authenticate to Vibe in a single step, using their eDirectory or LDAP passwords.