Re: [jetty-user] Question about Jetty and HTTPS

The only way I know would be to assign different port numbers to the different client services, then Jetty can be configured to have a separate certificate for each port/service.

You would get users to the right page by having a per-domain http:example.com which would do a redirect to the https port for that domain.

However, this approach looks ugly from the client POV (with addresses looking like "https:example.com:444" in the browser's navigation bar), so probably not very attractive.


Chris



On Thursday, September 30, 2010 at 4:42:02 PM, Silvio Bierman wrote:
> Hello all,

> We use a embedded Jetty instances to implement a multi-tier web-based 
> system. We serve multiple customers concurrently and distinguish between
> them by the DNS they use to get into the system. We use one single primary
> IP and use CNAME (alias) DNS chains that in the end all point to that same
> IP.

> We would like to extend this scheme with HTTPS. We want our customers to be
> able to provide their own certificates and use these in combinations with
> their DNS-es only. So we would have

DNS1 ->> Customer A@IP
DNS2 ->> Customer A@IP
DNS3 ->> Customer A@IP
DNS4 ->> Customer B@IP
DNS5 ->> Customer B@IP

> and use multiple certificates behind the same SSL listener on the same IP.
> Is this at all possible? Can a certificate be bound to only a single (or
> preferably a set of) DNS(-es)? Will using multiple different certificates on
> the same IP/port cause any kind of conflict?

> I know little about HTTPS and certificates. I have read some tutorials about
> Jetty + HTTPS and think I know what to do but if what I want is not possible
> then that effort would be wasted.

> Thanks in advance to everyone who can enlighten me here.

> Kind regards,

> Silvio
>  


> ---------------------------------------------------------------------
> To unsubscribe from this list, please visit:

>     http://xircles.codehaus.org/manage_email



---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email