Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Decide how to deal with Jolokia and security
See original GitHub issueIt’s not an endpoint so the EndpointRequest builder won’t cut it. Perhaps just manually defining the pattern is best?
Issue Analytics
- State:
- Created 6 years ago
- Comments:11 (11 by maintainers)
Top Results From Across the Web
Chapter 4. Security - Jolokia
This section specifies the Jolokia commands for which access is generally granted. For each command in the list, access can be further restricted...
Read more >Secure - Jolokia
Security in Jolokia is provided on two levels: The transport channel (HTTP) is secured the standard way as it is defined in the...
Read more >Chapter 3. Agents - Jolokia
A demo agent, which is completely unsecured. Please use this agent only for evaluation purposes, but it is highly recommended that use the...
Read more >Reference Documentation - Jolokia
This provides a good deal of comfort for Java clients of this API, but it is also dangerous because it hides the remoteness...
Read more >Release History - Jolokia
Handle UnsupportedOperationException to allow properly read Runtime MBean on jdk11 ... and "service-all" to allow to lookup an org.jolokia.osgi.security.
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
@joshiste That’s an interesting question. I think they should be. The problem is that both of these endpoints are MVC specific so it won’t make sense to show them in a Jersey/WebFlux application.
We should give some thought to securing third-party servlets that are registered in the management context as well. Spring Cloud is likely to have to move to this model for part of their Hystrix support (see #10257).