Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

New Auth Modules can not be enabled in the Docker image #15

Closed
deftdawg opened this issue May 6, 2018 · 2 comments
Closed

New Auth Modules can not be enabled in the Docker image #15

deftdawg opened this issue May 6, 2018 · 2 comments
Assignees
Labels
Milestone

Comments

@deftdawg
Copy link

deftdawg commented May 6, 2018

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:

  1. Deploy to docker
  2. Create a default repo
  3. Login as amAdmin
  4. 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.

@vharseko vharseko added the build label May 6, 2018
@vharseko vharseko added this to the 14.1 milestone May 6, 2018
@vharseko
Copy link
Member

vharseko commented May 7, 2018

after the restart of the service, the created modules are available in the list?

vharseko added a commit that referenced this issue May 8, 2018
Fix ReCaptcha settings typo +#13 + #15
maximthomas added a commit to maximthomas/OpenAM that referenced this issue May 10, 2018
@deftdawg
Copy link
Author

This issue is back for 14.1.5, this issue should be reopened.
@maximthomas, was there a particular reason why you reverted @vharseko's fix?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants