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

ConfigXmlGenerator Masking Should Be Optional #12217

ghost opened this issue Jan 29, 2018 · 0 comments

ConfigXmlGenerator Masking Should Be Optional #12217

ghost opened this issue Jan 29, 2018 · 0 comments


Copy link

@ghost ghost commented Jan 29, 2018

ConfigXmlGenerator masks certain fields like passwords. This is unnecessary since the person creating the hazelcast.xml should already know the values or they should be input by an end user installing the application. By masking the fields automatically the end user is forced to manually edit the hazelcast.xml, which creates a manual step in what should be automated process. Also, if the configuration needs to be changed and the ConfigXmlGenerator is used again, the fields are masked again and the user's values are lost. By making the masking optional the application developer can create an installer which queries the end user for the sensitive values and stores them in the hazelcast.xml.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

1 participant
You can’t perform that action at this time.