Ability to log in using a digital certificate

Aron - In order for this contribution to be considered for inclusion, please click the "contribute solution" button in the workflow of this ticket, accept the contributor's agreement and then accept the contribution in the workflow. This places the ticket in a state that indicates that an engineer must review your contributions. Thanks! Cynthia

Contribution agreement accepted. Thank you, Cynthia.

Hey Aron, thanks for this contribution! We are beyond the point where we could include this into the 6.1 release as it is very close to finished, and we are only fixing bugs from here on out. I would suggest that you could also place this into the community repository and eventually the Liferay Marketplace, once it is operational. The repository can be found at http://www.liferay.com/downloads/liferay-portal/community-plugins

Hi James. Thanks for the idea, that sounds good. Before doing that, however, I would appreciate feedback whether the solution conforms the proposal. I'm also wondering if modifications apart from the core autologin module, in particular the portlet UI adjustments should be part of the hook (and if they should, is there anything else I've overlooked).

Finally, there is this issue mentioned in the readme about the insecure session cookie. I'm not entirely comfortable with the workaround of disabling HTTP access to the portal altogether (which is basically the only guest view in this case). Could someone check and let me know if there is a different way? Thanks!

Hi Áron:
First of all, thank you very much for this awesome contribution and sorry for the delay in the response.
This feature is something a lot of customers and community members have been asking for a long time.
I'm reviewing it to analyze if we can include it in the Liferay core for the next version, so I will contact you soon to discuss over the issues you mention in the "Readme "file
Thanks a lot,
Juan Fernández

This is a very good idea, but I see a problem in this. What happens when server is behind cluster with SSL termination? In this case connections are made in http from ssl termination to J2EE server (Liferay), hence certificate won't be available, isn't it?

Even ignoring previous fact, source should be adapted to map Liferay attributes (email, screenName, etc) to custom certificate fields (example, spanish Id Card).

This can be achieved using CAS, anyway.

In preparation for Ideation; we are moving this contributed solution tickets to “Feature Request”. Additional information to follow.