Clone Tools
  • last updated a few minutes ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
[WFCORE-3393] For ManagementClientChannelStrategy.Establishing incorporate the ProtocolConnectionConfiguration connectionTimeout in the deadline for opening the Channel once the connection is opened.

[WFCORE-3183] CallbackKinds restriction for for CLI handler

[WFCORE-3145] Comment out unused logger methods

  1. … 19 more files in changeset.
[WFCORE-2917] allow-all-mechanisms, allow/forbid-sasl-mechanisms removing

  1. … 9 more files in changeset.
[WFCORE-2811] Remove JBoss Local User quiet setting from ProtocolConnectionUtil.

[WFCORE-2803] Remove default wildfly-config.xml and ensure our callback handler is adapted for correct local authentication behaviour.

    • -36
    • +0
    ./resources/META-INF/wildfly-config.xml
  1. … 6 more files in changeset.
[WFCORE-2731] Restore recognition of user-specifical sasl mechanism properties and default use of quiet auth if the JBOSS_LOCAL_USER mechanism is used

Change the authentication defaults to exclude explicit quiet auth and other unneeded configurations

    • -5
    • +1
    ./resources/META-INF/wildfly-config.xml
  1. … 2 more files in changeset.
Add back defaults for SSL / TLS connections

[WFCORE-2025] Restore using OptionMap for remaining non-security configuration.

[WFCORE-2025] Correct the priority when selecting the SSLContext to use with the CLI.

1. The SSLContext from jboss-cli.xml

2. An SSLContext from wildfly-config.xml

3. The default SSLContext that can prompt for trust decisions.

  1. … 3 more files in changeset.
[WFCORE-2225] Restore use of the configured client-side bind address

  1. … 1 more file in changeset.
[WFCORE-2121] Do not set an AnonymousCallbackHandler where one is not supplied by the caller, instead leave to be handled within the resolved AuthenticationConfiguration.

[WFCORE-2112] Non atomic updates

  1. … 1 more file in changeset.
[WFCORE-2075] Update Elytron configuration for schema modifications in Elytron 1.1.0.Beta17

    • -4
    • +7
    ./resources/META-INF/wildfly-config.xml
  1. … 4 more files in changeset.
[WFCORE-2020] Update the default configurations to discover the Elytron Provider using service loader discovery.

    • -8
    • +6
    ./resources/META-INF/wildfly-config.xml
  1. … 6 more files in changeset.
[WFCORE-1954] Update to latest WildFly Elytron API changes for defining the SSLContext to be used for the CLI.

[WFCORE-673] Prevent NPE if the connection is null

[WFCORE-673] Close the connection asynchronously to avoid a hang in ProtocolConnectionManager.shutdown()

[WFCORE-296]: Switch URI scheme from remoting:// http-remoting:// https-remoting:// to remote:// remote+http:// and remote+https://

Changing also the URL format for JMX and the default protocol is schemas.

  1. … 58 more files in changeset.
[WFCORE-952] Use standard null checks

  1. … 1 more file in changeset.
[WFCORE-673] Modify the AuthenticationConfiguration used so that the available CallbackHandler and SSLContext are used.

[WFCORE-673] Adjustments to the CLI and Protocol modules so that Elytron backed security configuration will be used.

  1. … 4 more files in changeset.
[WFCORE-1618] Just drop ProtocolChannelClient; this issue has lots of breaking changes in protocol module, no reason to deprecate this class and leave it around unused

[WFCORE-1618] Drop use of ProtocolChannelClient which is just an odd way to implement some factory methods Also standardize on ProtocolConnectionConfiguration instead of the ProtocolChannelClient.Configuration subclass which brings no added functionality

  1. … 10 more files in changeset.
[WFCORE-1618] Make ProtocolConnectionManager final; reduce class and method visibility where possible

[WFCORE-1618] Reduce method visibility; class is final, no uses in package outside this class

[WFCORE-1618] Drop no-op protected method for cruft bye-bye handling

[WFCORE-1618] Remove pointless hoops to get ref to 'this'

[WFCORE-1618] Clarify ManagementClientChannelStrategy use by not having ManagementChannelHandler create its own strategy It's helpful to know which classes are using ManagementClientChannelStrategy.Existing

  1. … 6 more files in changeset.