A Forum reader asked this question:

“Does anyone have any “how to” tips for creating an iChain accelerator for Groupwise WebAccess?”

And here are two suggestions:


Steve Bratt

There is nothing really special about this process, as Webaccess is like any other webserver from IChain’s perspective. Here’s what you need to do:

  1. Verify that your webaccess is avaiable via the IP address on your internal Webaccess server.
  2. Configure an accelerator in iChain that has this tested IP as it’s webserver address and your “public” IP for the accelerator assigned (and tested) on the IChain box.
  3. Verify that you have a good DNS entry set up that points the hostname you
    want to the public accelerator IP.

You should be off and running. From that point, setting up advanced features like formfill, authentication, SSL, etc., should follow the standard documentation.

There can sometimes be additional settings required with alternate hostnames. However, if your Webaccess is a standard install, it should respond to any requests on the correct IP and port, so that shouldn’t be necessary.

Martin Farrer

For GroupWise 6.5 or 7, don’t mess with form fill! Instead, just set basic authentication and forwarding authentication header.

Then there are a few tricks that you need to use:

  1. Enable OLAC on the iChain server.
  2. In ConsoleOne > iChain Service Object > Accelerator Configuration, get iChain to inject via OLAC, the cn or UID (otherwise, the dn gets passed). ICHAIN_UID, LDAP, CN will be the values you’ll need.
  3. To edit the properties of the GroupWiseWebAccess object inside the Domain, go to Application > Security and enter the default private IP address of the iChain server(s) as trusted.
0 votes, average: 0.00 out of 50 votes, average: 0.00 out of 50 votes, average: 0.00 out of 50 votes, average: 0.00 out of 50 votes, average: 0.00 out of 5 (0 votes, average: 0.00 out of 5)
You need to be a registered member to rate this post.

Disclaimer: As with everything else at NetIQ Cool Solutions, this content is definitely not supported by NetIQ, so Customer Support will not be able to help you if it has any adverse effect on your environment.  It just worked for at least one person, and perhaps it will be useful for you too.  Be sure to test in a non-production environment.

Leave a Reply

No Comments
By: coolguys
Oct 4, 2006
12:00 am
Active Directory Authentication Automation Cloud Computing Cloud Security Configuration Customizing Data Breach DirXML Drivers End User Management Identity Manager Importing-Exporting / ICE/ LDIF Intelligent Workload Management IT Security Knowledge Depot LDAP Monitoring Open Enterprise Server Passwords Reporting Secure Access Supported Troubleshooting Workflow