-
Notifications
You must be signed in to change notification settings - Fork 29
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
HTTPS #26
Comments
I agree completely. On IBMiOSS on Ryver, Richard Schoen suggested perhaps this should be done by an Apache reverse proxy. |
Absolutely - However SSL/TLS for HTTPS is a plan for the future ...The Apache / Nginx revese proxy is the solution for now |
One of the nice features of ILEastic is its capability to ditch the middle man... Having to use an RP negates some of that. |
.. Actually - the SSL/TLS code is in the project now. I have, however, not made it active yet... |
Sorry to bump this old thread, but ss the SSL/TLS code active in the project yet? |
No - it is not active yet - We use ILEastic primary as exposing RPGLE in a
microservice environment, where we normally use NGINX to dispatch requests
over plain HTTP.
However we can at system & method A/S enable it for you, if you have a
urgent need.
…On Thu, Dec 19, 2024 at 10:31 AM Krister Karlsson ***@***.***> wrote:
Sorry to bump this old thread, but ss the SSL/TLS code active in the
project yet?
I guess not as this issue is still in open status.
—
Reply to this email directly, view it on GitHub
<#26 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAVIPHSU6NVXIVXNFW2WMDT2GKG7ZAVCNFSM6AAAAABT4RXRMCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKNJTGE4DSMBYGE>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
Thanks for the info. No, it is not urgent as we are in an evaluating phase for different web service solution. Using NGINX as a reverse proxy could be a solution. Is activating TLS in ileastic sometime in the future still on the agenda and if so, is there any ETA? |
I hope you are considering Icebreak from the same provider that gave you ileastic, https://system-method.com/icebreak |
Thanx Wim for pointing Krister in that direction. I try to be "neutral"
here in the open source space. But certainly IceBreak will do what Krister
is asking for. Both ILEastic, noxDb and ILEvator are initially carved out
of the enterprise version of IceBreak with courtesy of System & Method -
Thanks to them. So IceBreak is a valid answer to the question.
…On Sat, Dec 21, 2024 at 10:21 AM Wim Jongman ***@***.***> wrote:
I hope you are considering Icebreak from the same provider that gave you
ileastic, https://system-method.com/icebreak
—
Reply to this email directly, view it on GitHub
<#26 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAVIPHS2U5LXPERZJ5FVH5L2GUXINAVCNFSM6AAAAABT4RXRMCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKNJYGA3DCMJUGE>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
SSL / TLS would be nice if services are run with a public interface.
The text was updated successfully, but these errors were encountered: