This article has been archived and is no longer maintained by ForgeRock.
When you create an authentication module via ssoadm with a command such as the following, where the module name and type match:$ ./ssoadm create-auth-instance -u amadmin -f pwd.txt -e / -m HOTP -t HOTP
the module appears to be created but when you try to open it in the console, you will see the following message:Not found error.
- You can create authentication modules with the same module name and type via the console.
- This issue affects all authentication modules, including custom ones.
- This issue also affects authentication modules that were created in earlier versions of AM/OpenAM, where the module name and type match. If you upgrade to an affected version and then try to open an authentication module that was created in an earlier version of OpenAM with the same module name and type, you will see the "Not found error."
Upgraded to, or installed AM 5 or 5.1.x.
Upgraded to, or installed OpenAM 13.0 or 13.5.
The sub-configuration is not created if the name of the authentication module is the same as the auth type when the module is created using ssoadm.
This issue can be resolved by upgrading to AM 5.5 and later, or OpenAM 13.5.1; you can download this from BackStage.
You can workaround this issue by using a different module name and type when creating the authentication module via ssoadm. For example:$ ./ssoadm create-auth-instance -u amadmin -f pwd.txt -e / -m HOTPmodule -t HOTP
Alternatively, you can create the authentication module via the console, which allows you to use the same module name and type if required.