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 its own subsystem and layer #2

Closed

Conversation

jessicarod7
Copy link

PoC for elytron-tls-subsystem. Will derive from changes in ELY-2084 branch of wildfly-elytron. Continuing from #1.

Related issues:

@jessicarod7 jessicarod7 force-pushed the WFCORE-5279 branch 3 times, most recently from c813e2d to 198a620 Compare July 25, 2022 19:56
@jessicarod7 jessicarod7 force-pushed the WFCORE-5279 branch 3 times, most recently from 6791bf8 to 4b42740 Compare August 3, 2022 20:44
@jessicarod7 jessicarod7 force-pushed the WFCORE-5279 branch 3 times, most recently from ed3f2ce to 76fc1dc Compare August 15, 2022 21:34
Temporarily disabled key/trust manager objects for SSLContext, key store
objects for key/trust managers. Acts the same as references.
Project successfully builds as-is
Started to convert most components to use Service, as opposed to
deprecated Service<T> and InjectedValue<T>
- Removed unneeded artifacts for feature packs
- Added missing dependencies for WildflyAcmeClient
- Created new feature group with full Elytron for early testing
- Removed redundant elytron-tls-base feature group
Need to review if inherited classes of RuntimeServiceFunction is a better
solution for runtime injection. May just end up removing
FunctionSupplier altogether.
Renamed to RuntimeServiceMethods, which is extended by each Service
@jessicarod7 jessicarod7 deleted the WFCORE-5279 branch September 29, 2022 18:40
@jessicarod7
Copy link
Author

jessicarod7 commented Sep 29, 2022

Removing this PR since the changes needed to implement the new Service API are rather extensive and undoing the changes directly is unfeasible. Will open a new PR for WFCORE-5279 using the legacy Service API.

This branch and its changes was renamed to new-service-template and might be used later on as method to implement the new API. Relevant files are:

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.

3 participants