Novell Home

My Favorites

Close

Please to see your favorites.

Working with iChain custom login pages.

(Last modified: 22Apr2005)

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

goal

Working with iChain custom login pages.

fact

iChain 2.1

iChain 2.2

iChain 2.3

Custom login page

symptom

Custom login page is not working.

Error: "The specific authentication profile login page is missing."

cause

The authentication profile is configured to use a protocol for which there is no proper custom login page.

fix

iChain 2.1 and later provides the ability to create a custom login page per accelerator.  When using custom login pages it is necessary to ensure that the proper HTML page is available, depending on the type of authentication profile associated with the accelerator configuration.

The designated login pages are as follows:

  • CALOGLDP.HTM
    • iChain 2.1, 2.2:
      Used for accelerators that have an LDAP profile with an "LDAP login name format" of "Use distinguished name", and where LDAP contexts are specified.  (User enters only their username to login.  e.g. johndoe)
    • iChain 2.3:
      Used for accelerators that have an LDAP profile with an "LDAP login method" of "Build distinguished name", and where LDAP contexts are specified.  (User enters only their username to login.  e.g. johndoe)
  • CALOGLNC.HTM
    • iChain 2.1, 2.2:
      Used for accelerators that have an LDAP profile with an "LDAP login name format" of "Use distinguished name", and where LDAP contexts are NOT specified.  (User enters their fully distinguished username to login.  e.g. cn=johndoe,ou=unit,o=org)
    • iChain 2.3:
      Used for accelerators that have an LDAP profile with an "LDAP login method" of "Build distinguished name", and where LDAP contexts are NOT specified.  (User enters their fully distinguished username to login.  e.g. cn=johndoe,ou=unit,o=org)
  • CALOGLFN.HTM
    • iChain 2.1, 2.2:
      Used for accelerators that have an LDAP profile with an "LDAP login name format" of "Use field name".
    • iChain 2.3:
      Used for accelerators that have an LDAP profile with an "LDAP login method" of "Search on a single attribute" or "Search using a query".
  • CALOGLMA.HTM
    • iChain 2.1, 2.2:
      Used for accelerators that have an LDAP profile with an "LDAP login name format" of "Use user's email".
    • iChain 2.3:
      The use of this file has been phased out in iChain 2.3.  Use CALOGLFN.HTM instead.
  • CALOGRAD.HTM
    • Used for RADIUS-based authentication profiles.

The default pages for each of the valid profile types are stored in the SYS:\ETC\PROXY\DATA directory on the iChain box.  These files may be used as examples from which to base custom login pages.  It is recommended that custom login pages be placed in separate directories, rather than modifying the default files.

Custom login pages may reside in subdirectories of either SYS:\ETC\PROXY\DATA or USERVOL:\ETC\PROXY\DATA (if space on the SYS: volume is an issue).

For example, if an accelerator is configured with a "Custom login page location" of NOVELL, the full path to the directory would be either of the following:
SYS:\ETC\PROXY\DATA\NOVELL
USERVOL:\ETC\PROXY\DATA\NOVELL

If a "Custom login page location" is specified for a web server accelerator, the appropriate file must reside in the appropriate directory, or an error page with the following message will be displayed: "The specific authentication profile login page is missing."

Consider the following examples (iChain 2.3 options are used):

  • If an LDAP profile is being used and the "LDAP login method" is "Build distinguished name" and LDAP contexts are listed, then the appropriate login page would be CALOGLDP.HTM.
  • If an LDAP profile is being used and the "LDAP login method" is "Build distinguished name" and no LDAP contexts are listed, then the appropriate login page would be CALOGLNC.HTM.
  • If an LDAP profile is being used and the "LDAP login method" is "Search on a single attribute", then the appropriate login page would be CALOGLFN.HTM.

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:
  • 10095706
  • Solution ID: NOVL99995
  • Creation Date: 03Dec2004
  • Modified Date: 22Apr2005
    • NetIQiChain

Did this document solve your problem? Provide Feedback