Skip to content

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

@EmersonPrado

Description

@EmersonPrado

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions