-
Notifications
You must be signed in to change notification settings - Fork 80
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Google Chrome/Linux not currently working #9
Comments
This issue is still valid for Chromium v51 (51.0.2704.79). |
Hello Simon, We checked recently with the people of FAS, and they are working on it. (being able to set up a secure connection when the client only sends a leaf certificate). I'll send them a reminder and point them to your post. Wkr, |
As soon Chrom(e|ium) 54 is released, we will be able to mark this bug as resolved \o/ https://bugs.chromium.org/p/chromium/issues/detail?id=579480#c29 |
Chrome 54 has been released now. Additionally, since the same problem now occurs with Safari 10 on macOS 10.12, it is reasonable to say that this is no longer a case of a single browser not working. Therefore, a change has been made to the federal authentication service (FAS) to work with browsers that exhibit this behaviour. The two combine to resolve this bug, so closing the issue. |
Users rejoice ! |
Currently, eID authentication on Google Chrome (or Chromium) for Linux does not work. This seems to be due to a change in Google Chrome made after Chrome 46.
Filed a bug report at https://code.google.com/p/chromium/issues/detail?id=579480
The text was updated successfully, but these errors were encountered: