Novell Home

My Favorites

Close

Please to see your favorites.

iChain 2.0 and Novell Portal Services Integration FAQ

(Last modified: 02Oct2002)

This document (10068296) is provided subject to the disclaimer at the end of this document.

fact

iChain 2.0

iChain 2.1

Novell Portal Services 1.0

Novell Portal Services 1.5

goal

iChain 2.0 and Novell Portal Services Integration FAQ

fix

1)  How do I configure to access Novell Portal Services (NPS) internally as well as externally (through iChain)?
Options:
A)  The DNS name (URL) in the gadget's configuration must match the entry in the Web Server Addresses field of the accelerator's configuration.  Set up an internal DNS server that resolves the DNS name to the internal address; Verify that the same DNS name resolves to the IP address for that accelerator for external users.   (This is the preferred method)
B)  Use the iChain custom rewriter to rewrite the redirect sent by the gadget (http://www.internal.com) to the accelerator address (https://www.external.com)
C)  You can use the HTML Gadget.  Under Advanced Settings, within the HTML gadget instance, the option 'Make links continue to appear inside of portal' specifies whether the URL actually gets redirected through the Portal or whether it goes straight to the Internet. The options are:

on = redirect through portal
off = go direct to link (default option with NPS 1.5)

You will want to set 'Make links continue to appear inside of portal' = ON for the URL to get redirected through the Portal Server.
*Note* Keep in mind that this option,'Make links continue to appear inside of portal',  is ONLY available with the HTML gadget...  The reason other gadgets (such as the iFrame, Shortcuts gadgets) do not have this option is because these gadgets do not pass the content thru the portal.  They just point the browser at the configured site, provide SSO, etc.  Thus, the Shortcuts/iFrame gadgets do not currently have Proxy-like features.  In simplistic terms, the Shortcuts and iFrame gadgets, build URLs for browsers.  They do not retrieve any web content.  The HTML gadget, on the other hand, retrieves the content, filters it, rewrites URLs, etc.

2)  Why does the connection fail when I enable SSLizer on iChain?
The DNS name (URL) in the gadget's configuration must match the entry in the Web Server Addresses field of the accelerator's configuration.  Otherwise, the internal rewriter will not rewrite the href/redirect from http to https.

3)  How do I single-sign on to Portal?
1)  On the LDAP configuration profile under LDAP Option, configure to use Field name | CN
2)  Under Configure | Web Server Accelerater > Portal accelerator's name | Modify | Authentication Options check the box to forward authentication information to Web Server.  Also see item 4 below.
*OLAC can be configured and used instead.

4)  Why do I get a page not found error when I access the accelerator?
The INDEX.HTML page from the NPS directory must be copied to the document root directory of the Web Server.

disclaimer

The Origin of this information may be internal or external to Novell. Novell makes all reasonable efforts to verify this information. However, the information provided in this document is for your information only. Novell makes no explicit or implied claims to the validity of this information.
Any trademarks referenced in this document are the property of their respective owners. Consult your product manuals for complete trademark information.

  • Document ID:
  • 10068296
  • Solution ID: NOVL71880
  • Creation Date: 13Feb2002
  • Modified Date: 02Oct2002
    • NovellConnectivity Products

      Web Services

Did this document solve your problem? Provide Feedback