Interoperability Issues

Novell ®SecureLogin, Novell SecretStore®, Novell iChain®, and Novell Portal Services can share secrets when the formats for the secrets are the same. If you have a secret in iChain that you want to leverage with SecureLogin, the naming conventions must be the same. Because SecureLogin makes the naming convention, use this convention in other services.

  1. Install SecureLogin.

  2. Set up a Web application in SecureLogin.

  3. Using SecretStore Manager, view the secret.

    See "Viewing a Secret" in the Novell SecretStore 3.3.3 Administration Guide.

  4. In the other service (for example, iChain), create the same type, with the same name.


SecureLogin and iChain

The authentication page in iChain has a Destination field. The SecureLogin client saves this field as an Optional parameter. This is the URL being requested. iChain is accelerating or securing the URL.

If iChain is also accelerating other Web pages or sites, the original Destination that SecureLogin saved when the user first saved the credentials will always be the URL that the user finally receives, regardless of the Web page or site that the user requested.

If the user needs to authenticate to iChain to get to the Web page, SecureLogin replaces the Destination where the user wants to go with the Destination that SecureLogin first saved.

Scenario: Changing the Destination Field. Markus Kurz wants to go to the Web server's index page. He enters the URL http://www.mkurz.com. SecureLogin saves this URL. The next time that Markus wants to go to GW WebAccess (www.mkurz.com/servlet/webacc), SecureLogin changes the Destination to http://www.mkkurz.com. Markus has to do a manual operation to get to GWWebAccess.

To fix the problem, Markus uncomments the Type $Optional line from the script. SecureLogin then ignores the Destination field.


First-Time Login to DEX 4.1 Portal Services

When a user first logs in to DEX 4.1 Portal Services, SecureLogin prompts the user to save the credentials. After the credentials are saved, and the user logs out or accesses the login page again, SecureLogin does the following:

SecureLogin copied the Username and Password values from the page and added them to its configuration. SecureLogin created a script that has the following lines:

Type $Username 
Type $Password. 
#Click #1 
# If this script does not submit the data correctly, try uncommenting the Click #1. 
# If this script puts the username or password in the incorrect fields, try counting the fields on 
# the page and adding the correct number to the Type commands (for example, Type $Username #2.)

To resolve the issue, uncomment the line that begins "#Click #1."


Integrating with BorderManager's Java Applet for Proxy Authentication

  1. Make sure that the SUN Java Runtime Environment is installed on the workstation and that Java has been enabled in SecureLogin.

    See "Enabling a Java Application" in the Nsure SecureLogin 3.51.2 User Guide.

  2. Configure the BorderManager proxy to use a Java applet for authentication

  3. Configure the browser to use the proxy.

  4. Launch the browser, attempt to connect to a site that requires authentication, then click Yes.

    SecureLogin should detect the login to a Web site and prompt you to create a script.

  5. On SecureLogin's main dialog box, click Applications, select the BorderManager applications, then click Edit.

  6. Click Script.

    The script for BorderManager should display the following lines:

    # control: 1 name:  *null (class java.awt.TextField) 
    # control: 2 name:  *null (class java.awt.TextField) 
    # control: 3 name:  *null (class java.awt.TextField) 
    # control: 4 name:  * Ok (class java.awt.Button) 
    # control: 5 name:  *Cancel (class java.awt.Button) 
    # control: 6 name:  *null (class BMLFrame)

  7. Add the following lines to the end of the script:

    Dialog 
    Type $Username #1 
    Type $Password #2 
    Click #4 
    EndDialog

    The revised script should display as follows:

    # control: 1  name: *null (class java.awt.TextField) 
    # control: 2  name: *null (class java.awt.TextField) 
    # control: 3  name: *null (class java.awt.TextField) 
    # control: 4  name: * Ok (class java.awt.Button) 
    # control: 5  name: *Cancel (class java.awt.Button) 
    # control: 6  name: *null (class BMLFrame) 
    Dialog 
      Type $Username #1 
      Type $Password #2 
      Click #4 
    EndDialog

  8. Save the script and exit.

  9. Close and restart the browser, then again attempt to connect to a site that requires proxy authentication.

    Don't move the mouse while SecureLogin is completing the applet form. SecureLogin moves the mouse to the OK button, then clicks it. If you move the mouse, SecureLogin might not be able to click OK.

    SecureLogin should now take you to the requested Web site.