Skip to content
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

Closed
yoe opened this issue Jan 20, 2016 · 6 comments
Closed

Google Chrome/Linux not currently working #9

yoe opened this issue Jan 20, 2016 · 6 comments
Assignees

Comments

@yoe
Copy link
Member

yoe commented Jan 20, 2016

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

@yoe yoe changed the title Google Chrome/Linux Google Chrome/Linux not currently working Feb 17, 2016
@yoe yoe self-assigned this Feb 17, 2016
@dagwieers
Copy link
Contributor

This issue is still valid for Chromium v51 (51.0.2704.79).

@simonh1000
Copy link

simonh1000 commented Jun 22, 2016

Any update as it is tax-paying time, and I feel nervous using a site that cannot provide a secure connection....!

See below for Chrome Version 50.0.2661.26 beta (64-bit) on Ubuntu 16.04

image

@Frederikus
Copy link
Contributor

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).
Would using firefox be an acceptable workaround to fill in your taxes in the meantime?

I'll send them a reminder and point them to your post.

Wkr,
Frederik

@wget
Copy link

wget commented Sep 2, 2016

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

@yoe
Copy link
Member Author

yoe commented Oct 25, 2016

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.

@yoe yoe closed this as completed Oct 25, 2016
@dagwieers
Copy link
Contributor

Users rejoice !

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

No branches or pull requests

5 participants