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.

Sign up for GitHub

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

Jump to bottom

Clarify whether/how to integrate the SecurityManager #56

Open
struberg opened this issue Mar 1, 2018 · 1 comment
Open

Clarify whether/how to integrate the SecurityManager #56

struberg opened this issue Mar 1, 2018 · 1 comment

Comments

@struberg
Copy link
Contributor

struberg commented Mar 1, 2018

Currently the whole config approach assumes that all the information is available in the whole ClassLoader/application.

If someone want's to guard against such an access, then this should best be done via the SecurityManager. But how to integrate this best?
@struberg
Copy link
Contributor Author

struberg commented Mar 1, 2018

We might also end up with coming to the conclusion that we don't want to define this in the spec and leave it to the implementations whether they want to have it.

jeanouii pushed a commit to jeanouii/ConfigJSR that referenced this issue Mar 8, 2018
@struberg
fixes eclipse#56 adding JavaDoc and TCK
0f6bacc 
Empty internal values are to be interpreted as not-existing configuration
Signed-off-by: Mark Struberg <[email protected]>
jeanouii pushed a commit to jeanouii/ConfigJSR that referenced this issue Mar 8, 2018
@struberg @OndroMih
fixes eclipse#56 adding JavaDoc and TCK
ad8e2e7 
Empty internal values are to be interpreted as not-existing configuration
Signed-off-by: Mark Struberg <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@struberg