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

Protect sensitive configuration by Security Manager permission check #14634

merged 1 commit into from Mar 12, 2019


None yet
3 participants
Copy link

commented Mar 4, 2019

This PR adds security manager protection to member config methods.

This allows using user-code deployments in a more secure way.

@kwart kwart added the Team: Core label Mar 4, 2019

@kwart kwart added this to the 3.12 milestone Mar 4, 2019

@kwart kwart self-assigned this Mar 4, 2019

@kwart kwart marked this pull request as ready for review Mar 4, 2019

Introduce Security Manager permission HazelcastRuntimePermission and …
…use it to protect sensitive Config methods

@kwart kwart force-pushed the kwart:jsm-HazelcastRuntimePermission branch from 645e197 to 7e8f296 Mar 6, 2019

@kwart kwart requested review from olukas and tkountis Mar 6, 2019


olukas approved these changes Mar 7, 2019


This comment has been minimized.

Copy link

commented Mar 7, 2019

Just a minor thing - would not be better to have HazelcastRuntimePermission names as public constants in those classes?

@kwart kwart merged commit 632cc7c into hazelcast:master Mar 12, 2019

1 check passed

default Test PASSed.

@kwart kwart deleted the kwart:jsm-HazelcastRuntimePermission branch Mar 12, 2019

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.