Creating authentication module via ssoadm causes Not found error in AM 5, 5.1.x and OpenAM 13.0, 13.5

Symptoms

When you create an authentication module via ssoadm with a command such as the following, where the module name and type match:

the module appears to be created but when you try to open it in the console, you will see the following message:

Please note: 

• 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."

Recent Changes

Upgraded to, or installed AM 5 or 5.1.x.

Upgraded to, or installed OpenAM 13.0 or 13.5.

Causes

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.

Solution

This issue can be resolved by upgrading to AM 5.5 and later, or OpenAM 13.5.1; you can download this from BackStage.

Workaround

You can workaround this issue by using a different module name and type when creating the authentication module via ssoadm. For example:

Alternatively, you can create the authentication module via the console, which allows you to use the same module name and type if required.

See Also

N/A

Related Training

N/A

Related Issue Tracker IDs

OPENAM-9156 ('Not Found' error in UI when opening a custom auth module created with ssoadm with the name the same as type)

OPENAM-8574 (The OpenAM CREST processing chain doesn't contain a RuntimeException handler)