-
Notifications
You must be signed in to change notification settings - Fork 34
Allow disable telemetry from BrandingConstants #115
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
Allow disable telemetry from BrandingConstants #115
Conversation
a048024 to
346e1a4
Compare
|
Ok. I think all comments have been addressed. Let me know if I missed something. |
jonbartels
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM Thank you for this PR!
It solves some bigger issues and questions using very little code.
gibson9583
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
server/src/com/mirth/connect/client/core/ConnectServiceUtil.java
Outdated
Show resolved
Hide resolved
cb867db
|
@mgaffigan I pushed my changes. If all look good to you I'm going to rebase and squash this PR. I moved all of the constants to the client-core class, because I didn't like having them split up and some duplicated. As a result I used static imports in several places. I also put a few more safety checks in place and show/hide additional gui components based on the settings. See screenshots below: CENTRAL_USER_REGISTRATION=true; MANDATORY_USER_REGISTRATION=false; registration box not checkedCENTRAL_USER_REGISTRATION=true; MANDATORY_USER_REGISTRATION=false; registration box checkedCENTRAL_USER_REGISTRATION=true; MANDATORY_USER_REGISTRATION=trueCENTRAL_USER_REGISTRATION=falseCHECK_FOR_NOTIFICATIONS=falseCHECK_FOR_NOTIFICATIONS=trueSEND_USAGE_STATISTICS=falseSEND_USAGE_STATISTICS=true |
gibson9583
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
+1 from me
|
@tonygermano, I like the disabled UI for mandatory. Much more clear. Am I missing something re: stats? I was unaware of the setting, but don't see anything that checks it in Mirth.java:404 nor ConnectServiceUtil.java:227. I only see it checked in front-end. It should not be an issue given |
Adds the following settings to BrandingConstants in client-core: - CENTRAL_USER_REGISTRATION - When false, disables the sending of user demographic information and hides the registration and marketing consent boxes from the first time login screen. - MANDATORY_USER_REGISTRATION - used in conjunction with CENTRAL_USER_REGISTRATION. When this is setting is true and the user id is 1, then the user will not be able to unselect the registration checkbox. - CHECK_FOR_NOTIFICATIONS - When false, allows for notification fetching from the client to be disabled. The notification menu task is also removed. - SEND_USAGE_STATISTICS - When false, allows for sending of usage statistics to be disabled. Also hides the setting which allows users to opt-in or opt-out of sending statistics. With the restoration of the registration checkbox when the appropriate settings are enabled, the adjustment of which fields are required on the user profile has also been restored. Co-authored-by: Tony Germano <tony@germano.name> Signed-off-by: Mitch Gaffigan <mitch.gaffigan@comcast.net> Signed-off-by: Tony Germano <tony@germano.name> Issue: OpenIntegrationEngine#5
e3ffc1e to
3954bc5
Compare








Closes #5 by adding branding constants:
As is, stats and registrations are sent to the non-existent https://connect.openintegrationengine.org/. Not sure what is desired, but I presume it is easier to keep it enabled than to try to merge a re-enable later.
This also updates the HttpClient configuration for notifications and telemetry to use the system defaults. I presume the preceding was an over-zealous edit during the "no PHI over anything but TLS1.2" heyday.
Related: #114
Alternative: #107