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

U2F Authentication with my own server #95

Closed
niravzaveri opened this issue Dec 2, 2015 · 4 comments
Closed

U2F Authentication with my own server #95

niravzaveri opened this issue Dec 2, 2015 · 4 comments

Comments

@niravzaveri
Copy link

Would it be possible that I can specify the U2F Registration/Authentication Server?
That way, I can integrate U2F Mechanism of this plugin with my common server.

This will be particularly helpful in achieving single sign-on mechanism.
This can also be helpful for people who manage more than one Wordpress sites.

@shield-9
Copy link
Collaborator

shield-9 commented Dec 2, 2015

Short Answer is "No."

There are no plan to support it at the moment.
But you can create "child plugin" of this plugin. Or pull request is welcome!

@kasparsd
Copy link
Collaborator

kasparsd commented Dec 2, 2015

@niravz Are you referring to something like https://github.com/Yubico/php-u2flib-server

You would need to create a custom second factor provider and replace validate_authentication() with something that makes REST call to validate the U2F response data from the token. Same with authentication_page() and the way it calls self::$u2f->getAuthenticateData( $keys );.

That kind of API approach seems to be vulnerable to a MITM attack where you only need to respond with {"touch": "\u0001", "counter": N} for the authentication to be considered successful.

@niravzaveri
Copy link
Author

Thanks @shield-9
@kasparsd
Thanks for the update on how I could do it.
What if I just modify the current plugin - U2F Provider's validate_authentication() and do_register() functions - and let my WP server act as a middle-layer between my client browser and the external server?

That way, I wouldn't do any changes in the authentication_page() functionality - and thereby won't be opening up any vulnerabilities, right?

Thanks.

@iandunn
Copy link
Member

iandunn commented Oct 20, 2022

U2F is deprecated and no longer works in Chrome, so the provider is being removed in #439 . Given that, there's probably no reason to keep this open anymore.

It seems like this feature is best left to an add-on plugin too.

@iandunn iandunn closed this as completed Oct 20, 2022
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

4 participants