Unfortunately, that's a huge question.  Or a really simple one, depending 
on if you've done it before.  We use Nginx with TLS as the front-end for 
many services and plain HTML websites at my work, so putting Jenkins behind 
Nginx/TLS was just like putting any other service behind Nginx/TLS - 
perhaps a half hour of work.  But I remember trying to put my first website 
behind TLS several years ago: there's a LOT to learn.  First, you need to 
find a tutorial on setting up Nginx (or some other web server, if that's 
your preference).  And you need to set it up as a proxy for Jenkins.  Then, 
you need to find a (almost always separate) tutorial on how to secure your 
already existing and functional Nginx.

I think you're looking for a single-click solution to this problem - and 
that's fair, it would be great if there was one.  But I'm not aware of one, 
so if you want to do this you need to start reading up on how to set up a 
web server, how to proxy a service, and then how to secure a web server.

I recommend Nginx: I've used both Apache and Nginx over many years, and 
have come to prefer Nginx as it's both lighter weight and a bit faster.  
But both are very good.  If you have a local guru who can support you who 
prefers a different web server entirely, use that (so long as they'll help 
you out).

I hope this helps.

On Thursday, 17 October 2019 14:51:54 UTC-4, TimeTravel wrote:
>
> Can someone please specify the steps of configurations to configure 
> Jenkins 2.190.1 to use TLS 1.2?
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/58d1ff20-8b9f-48ca-b4a8-ade715cb8c2a%40googlegroups.com.

Reply via email to