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

[WFCORE-5279] Split Elytron SSL into it's own subsystem #371

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

nekdozjam
Copy link
Contributor

* 2 way ssl
* FIPS
* providers
* Lets Encrypt
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This list looks good. A few more use cases come to mind initially:

  • Other certificate authorities that implement the ACME protocol
  • SNI matching
  • Certificate revocation lists / OCSP (although I suspect this might be covered under the truststore related configuration mentioned above)
  • Dynamic SSL contexts (which will be part of WFCORE-5101)

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Also configuration of default SSL context for the server comes to mind. Currently it is done by default-ssl-context resource.

* keystore (truststore) related configuration
* 2 way ssl
* FIPS
* providers
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

+1, we'll want to make it easy to use the WildFly OpenSSL provider.

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

Successfully merging this pull request may close these issues.

None yet

3 participants