[]  Provide SSLContext to Apache Artemis JMS client

In  messaging elytron security
Tracked by 

Overview

Currently Apache Artemis provides the connection parameters to any client or broker via a connector. The goal is to be able to get the SSLContext from Elytron and pass it to the client connector to be used when the connection factory connects.

Issue Metadata

Issue

Dev Contacts

QE Contacts

Testing By

  • Engineering

  • QE

Affected Projects or Components

Other Interested Projects

Relevant Installation Types

  • Traditional standalone server (unzipped or provisioned by Galleon)

  • [] Managed domain

  • [] OpenShift s2i

  • [] Bootable jar

Requirements

Plug elytron so that the artemis client can load the SSLContext from elytron itself. Since the Artemis client needs to access the elytron context it has to load the configuraton file. Until ARTEMIS-3756 is fixed the path to the elytron client configuration file URL is passed using the 'wildfly-config-url' or 'wildfly.config.url' system property as for a 'standard' elytron usage.

Hard Requirements

Nice-to-Have Requirements

Once ARTEMIS-3756 is fixed, use the 'wildfly-config-url' parameter from the connector to get the URL to the elytron client configuration file.

Non-Requirements

Backwards Compatibility

Default Configuration

Importing Existing Configuration

Deployments

Interoperability

Implementation Plan

Provide a SSLContextFactory implementation to Artemis so that the client has access to elytron provided SSLContexts. By extending the org.apache.activemq.artemis.core.remoting.impl.ssl.DefaultSSLContextFactory we are ensuring that it will provide backwards compatibility.

Security Considerations

Test Plan

Community Documentation

Release Note Content