Skip to content

Add a warning note regarding optional TLS mutual auth - #5434

Merged
traefiker merged 2 commits into
traefik:v1.7from
bradjones1:patch-4
Nov 27, 2019
Merged

traefiker merged 2 commits into
traefik:v1.7from
bradjones1:patch-4

Conversation

@bradjones1

Copy link
Copy Markdown
Contributor

What does this PR do?

Adds a warning to the TLS mutual authentication section regarding non-universal client support for optional client certificates during handshaking.

Motivation

We got burned by certain clients which do not treat this option as truly optional; see this Chromium ticket for an example of this incompatibility in the wild.

More

  • Added/updated tests
  • Added/updated documentation

@jbdoumenjou

Copy link
Copy Markdown
Contributor

Hi @bradjones1,

Could you give more details on your difficulties and use cases to be sure to understand everything?

@bradjones1

Copy link
Copy Markdown
Contributor Author

@jbdoumenjou thanks for the response. The issue linked in the original post sums up a usual case pretty well; not all browsers properly implement the TLS 1.1 and 1.2 standards regarding client certificate CAs expressed as supported by the server. Per the specs, the client either SHOULD (1.1) or MUST return an empty set of client certificates (since they have none that match) and the server can choose to continue the handshaking ("optional" mode in Traefik.)

Not all browsers - in our experience older browsers on mobile, and even some newer ones - properly implement this flow. In the case of Chrome on Android, because Android < 10 does not reveal client certificate storage info to the app, the user is always presented with a scary-looking certificate request. If you cancel it out, the handshaking proceeds, but this is bad UX particularly for customer-facing sites.

In our experience, hosting many client web sites that serve the broad public, this UA incompatibility on many devices means we had to back out of using client certificate validation, as it meant a measurable decrease in traffic from affected devices/UAs.

Does that help?

@jbdoumenjou

Copy link
Copy Markdown
Contributor

Thank you for this clarification.
Have you tried v2.0? Mutual authentication is now configurable

@bradjones1

Copy link
Copy Markdown
Contributor Author

We are evaluating 2.0 but no I have not yet had a chance to and we are on 1.x for the time being. I think this is helpful to add to the documentation as it caused quite a surprise for us and I don't see much elsewhere about the risk of implementing this with respect to these mobile browsers.

Comment thread docs/configuration/entrypoints.md Resolved

@ldez ldez left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks 👍

@jbdoumenjou jbdoumenjou left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants