You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When attempting to enable a new module instance in the docker image (OpenAM 14.1.1 Build 2f3d35c (2018-April-28 10:03)), following the steps to add and provide any optional configuration values (such as datastore for HTTP Basic Auth), the modules do not appear in the list of enabled modules and can not be used in an authentication chain.
Steps to reproduce:
Deploy to docker
Create a default repo
Login as amAdmin
Go to Realms tab -> select (Top Level Realm) -> Authentication tab -> Module Instances, click "New" -> add an authentication module -> save
The module does not appear in the module instances and can't be used in the Authentication chaining.
Tried with both non-XUI and XUI UI modes.
The above steps worked as expected on "OpenAM 11.0.3 Community Edition" built from source.
The text was updated successfully, but these errors were encountered:
When attempting to enable a new module instance in the docker image (OpenAM 14.1.1 Build 2f3d35c (2018-April-28 10:03)), following the steps to add and provide any optional configuration values (such as datastore for HTTP Basic Auth), the modules do not appear in the list of enabled modules and can not be used in an authentication chain.
Steps to reproduce:
The module does not appear in the module instances and can't be used in the Authentication chaining.
Tried with both non-XUI and XUI UI modes.
The above steps worked as expected on "OpenAM 11.0.3 Community Edition" built from source.
The text was updated successfully, but these errors were encountered: