[squid-users] Mutual authentication managed by Squid
Yuri Voinov
yvoinov at gmail.com
Fri Feb 20 09:24:10 UTC 2015
Transparent SSL Bump interception, eh?
20.02.15 15:14, Ilya Karpov пишет:
> Hi guys,
> can anyone suggest solution to make following scenario work using squid:
>
> step1.
> Client(actually server application) calls HTTP://example
> <http://example>.org squid via proxy.
> |
> V
> step2.
> Proxy(Squid) understands that all calls to HTTP://example.org
> <http://example.org> should be changed to HTTPS://example.org
> <httpS://example.org>, trusts CA that uses example.org
> <http://example.org> and knows client certificate to use for https
> client authentication
> |
> V
> step3.
> Origin(some server in internet) accepts https request, authenticates
> client, returns response
>
> The main aim is to make client know nothing about https complexity
> (storing certificates/keys, knowing specific algorithms etc), and make
> squid manage this things.
>
>
> Best regards,
> Ilya Karpov
> karpoftea at gmail.com <mailto:karpoftea at gmail.com>
>
>
>
>
>
> _______________________________________________
> squid-users mailing list
> squid-users at lists.squid-cache.org
> http://lists.squid-cache.org/listinfo/squid-users
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.squid-cache.org/pipermail/squid-users/attachments/20150220/70586e1a/attachment.html>
More information about the squid-users
mailing list