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

Chrome - U2F API invalid after 02.2022, use Web Authentication AP #17754

Closed
uli-heller opened this issue Nov 22, 2021 · 3 comments
Closed

Chrome - U2F API invalid after 02.2022, use Web Authentication AP #17754

uli-heller opened this issue Nov 22, 2021 · 3 comments
Labels
issue/duplicate The issue has already been reported.

Comments

@uli-heller
Copy link
Contributor

Gitea Version

1.15.6

Operating System

Ubuntu-20.04

Browser Version

Chrome-96

Can you reproduce the bug on the Gitea demo site?

No

Description

I'm using a FIDO device to authenticate against gitea. Probably since upgrading to chrome 96, a warning like this shows up:

image1

It is German and it says that the U2F API will not be available after February 2022.
Here is a similar tochet for another project: authelia/authelia#2615

There it says:

We're working on adding the Web Authentication API.

Chrome is the only browser deprecating support at the moment. It was deprecated since version 95, will be disabled by default in February 2022 (version 98), and finally removed in March 2022 (version 100).

So maybe we need something similar for gitea?

Screenshots

image1

@wxiaoguang
Copy link
Contributor

Oh, maybe this problem can be considered together with

@silverwind
Copy link
Member

Related: #6892.

@lunny
Copy link
Member

lunny commented Nov 22, 2021

Let's continue in #6892

@lunny lunny closed this as completed Nov 22, 2021
@lunny lunny added the issue/duplicate The issue has already been reported. label Nov 22, 2021
@go-gitea go-gitea locked and limited conversation to collaborators Apr 28, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
issue/duplicate The issue has already been reported.
Projects
None yet
Development

No branches or pull requests

4 participants