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

Port the remaining aspnet-contrib providers #1801

Open
1 task done
kevinchalet opened this issue Jun 18, 2023 · 1 comment
Open
1 task done

Port the remaining aspnet-contrib providers #1801

kevinchalet opened this issue Jun 18, 2023 · 1 comment

Comments

@kevinchalet
Copy link
Member

kevinchalet commented Jun 18, 2023

Confirm you've already contributed to this project or that you sponsor it

  • I confirm I'm a sponsor or a contributor

Describe the solution you'd like

Here's the complete list of providers currently supported by aspnet-contrib (note: providers supported only by OpenIddict - like Cognito or ADFS - are deliberately not listed here):

Provider name Still operating? Supported by OpenIddict?
AdobeIO
Alipay
Amazon
amoCRM
Apple
ArcGIS
Asana
Autodesk
Baidu
Basecamp
BattleNet
Beam (Mixer)
Bitbucket
Buffer ⚠️
CiscoSpark (Webex Teams)
Coinbase
DeviantArt
Deezer
DigitalOcean ⚠️
Discord
Dropbox
eBay
EVE Online ⚠️
ExactOnline
Feishu
Fitbit
Foursquare ⚠️
Gitee
GitHub
GitLab
Gitter
Harvest
HealthGraph (Runkeeper) ⚠️
Huawei
HubSpot
Imgur
Instagram
KakaoTalk
Keycloak
Kloudless
KOOK
Kroger
Lichess
Line
LinkedIn
MailChimp
MailRu
Mixcloud
Moodle
Myob
Naver
NetEase
Nextcloud
Notion
Odnoklassniki
Okta
Onshape
Patreon
Paypal
PingOne
QQ
QuickBooks
Reddit
Salesforce
ServiceChannel
Shopify
Slack
Smartsheet
Snapchat
SoundCloud ⚠️
Spotify
Stack Exchange
Strava
Streamlabs
SuperOffice
Trakt
Trovo
Twitch
Twitter
Untappd ⚠️
Vimeo
Visual Studio (Azure DevOps) ⚠️
Vkontakte
Weibo
Weixin (WeChat)
WordPress
WorkWeixin (WeCom)
Xero
Xumm (Xaman)
Yahoo
Yammer ⚠️
Yandex
Zalo
Zendesk ⚠️

Many popular services have already been ported but there's still providers that are not yet supported by the OpenIddict web providers companion package. Most of them have a complicated registration process (e.g phone number verification, manual approval, restricted submissions, documentation available only in Chinese, etc.), which is why they were not ported as part of the first batch.

We'll need to determine whether there's a community interest in seeing the remaining providers supported and if so, involve the community to help port them or provide test client credentials when necessary.

Note:

  • Beam/Mixer was shut down by Microsoft in 2020 (the aspnet-contrib package will be removed from the repo and unlisted on NuGet.org).
  • DigitalOcean requires registering a payment method and making a prepayment to be able to access the developer console.
  • EVE Online requires a paid account to be able to test their API.
  • Foursquare no longer supports OAuth 2.0 for their recent v3 API (see https://location.foursquare.com/developer/docs/using-oauth-authentication), so it will very likely not be ported.
  • Gitter stopped supporting OAuth 2.0/OpenID Connect when moving to Matrix so it will not be ported (the aspnet-contrib package will be removed from the repo and will be unlisted on NuGet.org).
  • Kloudless was merged into Netskope and all the APIs now return an HTTP 502 Bad Gateway error, so it's likely the OAuth 2.0 service is no longer working.
  • Buffer, SoundCloud, Runkeeper and Untappd still offer an OAuth 2.0 service but no longer allow creating new client applications, which makes porting these providers quite difficult as we'd need existing client credentials to test them.
  • Yammer is still operating, but it's unclear what will happen to the OAuth 2.0 service once it's replaced by Viva Engage.
  • The Azure DevOps/Visual Studio OAuth 2.0 service is still available, but the DevOps REST API now also accepts Azure AD access tokens. Given that Azure AD is already supported and much more standard-compliant, adding a VSO-specific provider is not necessary.
  • Zendesk restricts the ability to create integrations to paid accounts (and automatically locks test accounts very shortly after they are created anyway...)

If you're interested in helping or would like to see a specific provider supported, please add your voice here.

Additional context

No response

@kevinchalet
Copy link
Member Author

As explained in https://github.com/openiddict/openiddict-core/releases/tag/4.6.0, the remaining providers I could port myself have been added to 4.6.0: for the other providers (that are supported by aspnet-contrib but not by OpenIddict), community contributions will be required (e.g PRs or test credentials).

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

1 participant