search

ory / kratos

Next-gen identity server replacing your Auth0, Okta, Firebase with hardened security and PassKeys, SMS, OIDC, Social Sign In, MFA, FIDO, TOTP and OTP, WebAuthn, passwordless and much more. Golang, headless, API-first. Available as a worry-free SaaS with the fairest pricing on the market!
https://www.ory.sh/kratos/?utm_source=github&utm_medium=banner&utm_campaign=kratos
Apache License 2.0
11.04k stars 949 forks source link

Social sign in with Twitter #517

Closed romcok closed 6 months ago

romcok commented 4 years ago

Is your feature request related to a problem? Please describe.

Hi, we want to use the sign in with Twitter, but I don't know how to configure it.

This is written in the documentation: The oidc method uses OpenID Connect, or OAuth2 where OpenID Connect is not supported, to authenticate identities using a third-party identity provider, such as Google, Microsoft, GitHub - or any other OAuth2 / OpenID Connect provider..

Twitter is the OAuth2 provider, so I hope it will work somehow 🙏

aeneasr commented 4 years ago

Twitter is not OAuth2 but the older OAuth1, so we will need a dedicated strategy to deal with Twitter! By searching on Google it appears that there's at least one library able to deal with Twitter's OAuth (1.0) protocol: https://github.com/kkdai/twitter

romcok commented 4 years ago

Oh, now I see. They have OAuth2 only for application-only authentication. https://developer.twitter.com/en/docs/basics/authentication/oauth-2-0

Twitter is quite a big player and a lot of people come to us from there, it would be good to have it as an option.

marcinkoziej commented 3 years ago

Hello @aeneasr ! What is the hour estimate to add this functionality to Kratos? Could we sponsor such work to be done by You or someone form Ory team? (you can also mail me at marcin@fixthestatusquo.org)

aeneasr commented 3 years ago

Someone from out team will reach out to you in the next days!

lanphan commented 2 years ago

https://github.com/dghubble/oauth1 is a better lib to use, imho.

mfzl commented 2 years ago

Twitter is not OAuth2 but the older OAuth1, so we will need a dedicated strategy to deal with Twitter! By searching on Google it appears that there's at least one library able to deal with Twitter's OAuth (1.0) protocol: https://github.com/kkdai/twitter

Are you suggesting another strategy along with oidc and password. What would it be called for example oauth1 or twitter?

aeneasr commented 2 years ago

No, this can be dealt with in the normal oidc strategy. You just need to use a different library to complete it, and not our generic OIDC provider!

mfzl commented 2 years ago

@aeneasr Is this being developed? If not I'd like to take this up

aeneasr commented 2 years ago

Noone is working on it afaik :) Please do pick it up! :)

vinckr commented 2 years ago

And let me know if I can support you in any way with this :-). Feel free to ping me in our Community Chat.

ghost commented 1 year ago

Twitter is not OAuth2 but the older OAuth1, so we will need a dedicated strategy to deal with Twitter! By searching on Google it appears that there's at least one library able to deal with Twitter's OAuth (1.0) protocol: https://github.com/kkdai/twitter

They are OAuth2 now. Just letting you know ...

https://developer.twitter.com/en/docs/authentication/oauth-2-0

aeneasr commented 1 year ago

Awesome!! If anyone is up for contributing this I would appreciate it a lot!