We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Set wildfly::secret_value and/or wildfly::remote_username parameter
Remote user always falls into security-realm subsystem, regardless of actual subsystem being used
Class should receive subsystem as a parameter and allocate configuration accordingly
The text was updated successfully, but these errors were encountered:
was this in before, or did i break it while migratin' it to vox?
Sorry, something went wrong.
It already happened (long) before.
No branches or pull requests
Affected Puppet, Ruby, OS and module versions/distributions
How to reproduce (e.g Puppet code you use)
Set wildfly::secret_value and/or wildfly::remote_username parameter
What are you seeing
Remote user always falls into security-realm subsystem, regardless of actual subsystem being used
What behaviour did you expect instead
Class should receive subsystem as a parameter and allocate configuration accordingly
The text was updated successfully, but these errors were encountered: