Expected list of logins is not presented when visiting a new webpage in the same domain as a previously visited page

  • 7000619
  • 06-Jun-2008
  • 01-Jun-2012


NSL6.1 hotfix 4



Users are not prompted with the expected list of logins when visiting a new webpage in the same domain as a previous page unless they exit and restart their internet browser

Users are asked if they “would you like to login again” when visiting a new page in the same domain as a previously visited page

Users are prompted to fix login credentials when visiting a new page; doing so changes the credentials of the previous page


Bug report has been entered.

Write your own application definition or use a pre-built application definition if available.

Steps to duplicate:

1. Login to two or more subdomains off of the same main webpage (for example novell.com and gmail.novell.com). These subdmains must require different passwords.

2. Allow the SecureLogin Web Wizard to detect and create logins for each of these pages. Do not write a script for the pages or accept any predefined application definitions for these pages; by default the web wizard will create a new login for each page.

3. Relaunch your internet browser. The first time one of these pages is accessed after the browser is started, the user will be presented with a list of all the logins that have been created for the various subdomains, and will be prompted to select the appropriate login for the current page. This is the expected behavior and is what should happen every time one of the pages is visited.

4. Go to one of the other pages WITHOUT exiting the browser, the user will NOT be presented with the pick list of logins. Instead users will see a prompt asking if they want to login again. This is the first problem.

5. Answer yes to the “would you like to log in again?” prompt. The login will be attempted and the user will then be a box saying login credentials are wrong and need to be corrected. But if you look in Manage Logins on the workstation the credentials will show correctly – the message is presented because SecureLogin thinks it is logging in to the previous page and is using the login credentials that go with that prior page.

6. Correct the credentials as prompted. , expecting NSL to change the credentials only for the current page.

7. SecureLogin changes the credentials for the previous page – the one it thought was being re-accessed. Now the login for the previous page is wrong.