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

class wildfly::setup hardcodes subsystem when setting up remote user #303

Open
EmersonPrado opened this issue Oct 25, 2023 · 2 comments
Open

Comments

@EmersonPrado
Copy link
Contributor

Affected Puppet, Ruby, OS and module versions/distributions

  • Puppet/Ruby/Distribution: any
  • Module version: current

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

@rwaffen
Copy link
Member

rwaffen commented Oct 27, 2023

was this in before, or did i break it while migratin' it to vox?

@EmersonPrado
Copy link
Contributor Author

was this in before, or did i break it while migratin' it to vox?

It already happened (long) before.

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

No branches or pull requests

2 participants