#908 ✓resolved
Tim Stone

When using SSL, Play always requests client authentication

Reported by Tim Stone | June 13th, 2011 @ 11:41 PM | in 1.2.3 (closed)

Framework version: 1.2.1

Reproduction steps:

  • Configure Play to use SSL
  • Attempt to access the site using a browser that will prompt for a client certificate (IE 9 and Chrome dev, in my case)
  • Receive prompt


In most cases, it's probably not desirable to request client authentication. If users press OK on the dialog they're presented, the site can refuse the connection if they have a bad client certificate. If they press Cancel, they can access the site normally, but this can be annoying and unintuitive if they weren't expecting it.

Currently, SslHttpServerPipelineFactory calls setWantClientAuth(true) on the SSLEngine unconditionally (overwriting the earlier call to setNeedClientAuth(true)). I think it would be better if this was based on a configuration option instead, that allowed for one of the following states:

  • no client auth
  • want client auth
  • need client auth

Comments and changes to this ticket

Please Sign in or create a free account to add a new ticket.

With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.

New-ticket Create new ticket

Create your profile

Help contribute to this project by taking a few moments to create your personal profile. Create your profile »

<h2>Play framework</h2>

Play makes it easier to build Web applications with Java. It is a clean alternative to bloated Enterprise Java stacks. It focuses on developer productivity and targets RESTful architectures. Learn more on the <a href="http://www.playframework.org">http://www.playframework.org</a> website.<br><br>

<h2>Source code is hosted on github</h2>Check out our repository at <a href="http://github.com/playframework/play">http://github.com/playframework/play</a><br><br>

<h2>Contributing, creating a patch</h2> Please read the <a href="http://play.lighthouseapp.com/projects/57987/contributor-guide">contributor guide</a><br><br>

<h2>Reporting Security Vulnerabilities</h2> Since all bug reports are public, please report any security vulnerability directly to <em>guillaume dot bort at gmail dot com</em>.<br><br>

<h2>Creating a bug report</h2> Bug reports are incredibly helpful, so take time to report bugs and request features in our ticket tracker. We’re always grateful for patches to Play’s code. Indeed, bug reports with attached patches will get fixed far quickly than those without any.<br><br>

Please include as much relevant information as possible including the exact framework version you're using and a code snippet that reproduces the problem.<br><br>

Don't have too much expectations. Unless the bug is really a serious "everything is broken" thing, you're creating a ticket to start a discussion. Having a patch (or a branch on Github we can pull from) is better, but then again we'll only pull high quality branches that make sense to be in the core of Play.

Referenced by