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

Remoting JMX Update #25

Closed
wants to merge 20 commits into from
Closed

Conversation

darranl
Copy link

@darranl darranl commented Aug 28, 2013

This one is for WildFly only so that Remoting JMX disables local authentication if username/password authentication is possible.

EAP is using version 1.1 so I will send a pull request for that one separately.

bstansberry and others added 20 commits August 27, 2013 11:52
…sic test of the 'simple' provider using 'roles' headers
…ble so they can be passed from process to process.
…g management requests from a trusted master can request a Subject to use when executing the operation.

For host controller to managed server interactions the two are always kept in sync version wise.
For master to slave communication the master must be the same version as the slave or higher i.e. a slave sending this new request will not cause an interop issue as the master must be at least a version that understands it.
…n 'anonymous' user is associated with the current request.
…r and SubjectSupplemental implementations to aid debugging of authentication / authorization failures.
Also a minor update to only set the CallbackHandler if username/password authentication is actually required as this disabled the local authentication mechanism.
@bstansberry
Copy link
Owner

Merged into my rbac branch and included in wildfly#4982

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
5 participants