Bug ID 611240: Import of config with securid might fail

Last Modified: Nov 07, 2022

Bug Tracker

Affected Product:  See more info
BIG-IP APM(all modules)

Known Affected Versions:
12.1.0, 12.1.0 HF1, 12.1.0 HF2, 12.1.1, 12.1.1 HF1, 12.1.1 HF2

Fixed In:
13.0.0, 12.1.2

Opened: Aug 16, 2016
Severity: 3-Major
Related Article:


Import of the profile used for securid auth might fail if the profile has already been used for auth purposes at the moment of export.


Unable to import certain configurations.


This occurs when the following conditions are met: -- Profile configured for securid authenticaiton with securid server attached. -- Profile has been used for authentication more than 0 times. -- Full import (no reuse) or Reuse import when secureid server under the same name is not present.


1. In VPE, open securid auth item and set server to none before export. 2. Export profile. 3. Import profile. 4. Re-create the aaa securid server. 5. In VPE, open the securid auth item and set server to one from step #4. Or 1. Export profile. 2. Create aaa securid server under the same name. 2. Import profile with reuse. It is also possible to remove securid entry from config-files of securid server configuration in .conf.tar.gz, which would also work.

Fix Information

It is now possible to successfully export and the import profile using securid in any state.

Behavior Change