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

[IDEA] Configuration setting to hide values in Global Map panel #5783

Open
mikeyw opened this issue May 15, 2023 · 3 comments
Open

[IDEA] Configuration setting to hide values in Global Map panel #5783

mikeyw opened this issue May 15, 2023 · 3 comments
Labels
enhancement New feature or request Internal-Issue-Created An issue has been created in NextGen's internal issue tracker RS-10680 triaged

Comments

@mikeyw
Copy link

mikeyw commented May 15, 2023

Is your feature request related to a problem? Please describe.
With Configuration Map entries, the default setting in the Mirth Administrator is to hide the values. The same functionality would be useful in the Global Maps panel of the Dashboard.

Describe your use case
To maintain high security, my organization regularly rotates database passwords. To avoid having to reconfigure database connections in each channel, we store the credentials in the Global Map and reference the them in the channels. This works very well, but the one drawback is that the database credentials are visible in plain text in the Global Maps panel to any onlooker that passes by the developer's desk. Having the values hidden by default would increase security.

Describe the solution you'd like
Add a checkbox to the Global Map panel in the Mirth Administrator Dashboard the gives the option to show or hide Global Map values. Default the checkbox to the "hide"

Describe alternatives you've considered
We have considered loading the database credentials from a file in a secured folder, but that adds unwanted overhead.

@mikeyw mikeyw added the enhancement New feature or request label May 15, 2023
@kirbykn2
Copy link

kirbykn2 commented May 15, 2023 via email

@pacmano1
Copy link
Collaborator

pacmano1 commented May 15, 2023

I agree with the original ask. In fact the only thing in $cfg for our work is enough for one DB connect to then go get everything else needed which is stored in $g.

In our case, everything per EHR brand is sourced from a DB (e.g. base_url, creds, potential decision logic, etc.) and stored to $g in JS objects for accessability by channels. $cfg does not accept objects.

@mikeyw
Copy link
Author

mikeyw commented May 15, 2023 via email

@lmillergithub lmillergithub added triaged Internal-Issue-Created An issue has been created in NextGen's internal issue tracker RS-10680 labels May 17, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request Internal-Issue-Created An issue has been created in NextGen's internal issue tracker RS-10680 triaged
Projects
None yet
Development

No branches or pull requests

4 participants