Repository navigation
Spotify social identity provider #8555
Replies: 3 comments 2 replies
|
@JiriHartikka Thanks for the proposal. We are always looking forward to new integrations. However, we need to run automated tests to make sure the integration do not break. For that, we have a FYI, we have a long-standing PR for Apple ID integration [1]. It is a very popular integration but we could not figure out yet how to have the tests running for it. This is really a blocker, I hope Spotify works differently and we can easily use a test account for running tests. [1] #7323 |
|
I don't think using Spotify as a identity provider is a commonly enough wanted capability to warrant adding it out of the box. An alternative would be to deliver it as an extension and register it here https://www.keycloak.org/extensions.html. |
|
Works for me too. Also aligned with the idea of baking extensions first in
the community before having them in the codebase.
…On Wed, Oct 20, 2021 at 3:25 AM Stian Thorgersen ***@***.***> wrote:
I don't think Spotify makes any sense to add directly to Keycloak. Would
be better to have as an extension and register it on the website in case
anyone else is interested.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#8555 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAIXFDPZJOJTRAMPDWCMMJ3UHZOE7ANCNFSM5FVK3BSQ>
.
Triage notifications on the go with GitHub Mobile for iOS
<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
or Android
<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
|
|
Anything I can do to help get this pushed through as an extension? |
|
@thebalaa After you are done with the repository, I think we can just send a PR to our website repository to provide some metadata about your extension. See https://github.com/keycloak/keycloak-web/tree/main/extensions. |
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
I am implementing a social identity provider for Spotify as part of a hobby project I am working on. I am wondering if this is something that I should try to get merged to the upstream repository.
Spotify does not support openid connect, and as I want my Keycloak users to be able to login using Spotify, the only reasonable way to achieve this seems to be implementing another social idp.
I have a proof on concept implementation in this fork: https://github.com/JiriHartikka/keycloak/tree/spotify-social-idp. It is just a very simple extension of the AbstractOAuth2IdentityProvider.
I am willing to write the documentation and test cases for the idp if this is something of interest.
All reactions