Environment
Novell SecureLogin
NSL6.x
NSL7.0.1
SLManager
MMC
"Users and Computers"
SecureLogin system tray utility on workstation
NSL6.x
NSL7.0.1
SLManager
MMC
"Users and Computers"
SecureLogin system tray utility on workstation
Situation
Unable to import SecureLogin applications or settings into a new container with desktop-based SecureLogin utilities
Admin cannot export XML file from one container and import into another
Problem occurs using "Users and Computers" and SLManager
Problem occurs after file extension was renamed from .xml to .XML
Same problem occurs with .esx file exported with the workstation system tray tool, and renamed to .ESX.
Importing file fails with error: "Cannot load this file - unknown type"
Admin cannot export XML file from one container and import into another
Problem occurs using "Users and Computers" and SLManager
Problem occurs after file extension was renamed from .xml to .XML
Same problem occurs with .esx file exported with the workstation system tray tool, and renamed to .ESX.
Importing file fails with error: "Cannot load this file - unknown type"
Resolution
Fixed with NSL7 SP3 or newer.
Workaround:
Rename file extension to lowercase .xml or .esx. The file import is case sensitive when using the SecureLogin desktop utilities.
Importing "whatever.XML" will fail, but importing "whatever.xml" will succeed.
Altertnaively, use iManager. The problem does not occur when importing with the iManger SecureLogin SSO plugin.
Importing "whatever.XML" will fail, but importing "whatever.xml" will succeed.
Altertnaively, use iManager. The problem does not occur when importing with the iManger SecureLogin SSO plugin.
Status
Reported to EngineeringAdditional Information
Workarounds:
1. Rename file extension to lowercase .xml or .esx. The file import is case sensitive when using the SecureLogin desktop utilities.
Importing "whatever.XML" will fail, but importing "whatever.xml" will succeed.
2. Altertnaively, use iManager. The problem does not occur when importing with the iManger SecureLogin SSO plugin.
Importing "whatever.XML" will fail, but importing "whatever.xml" will succeed.
2. Altertnaively, use iManager. The problem does not occur when importing with the iManger SecureLogin SSO plugin.