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

Badge Request: LinkedIn #7177

Closed
arnonrdp opened this issue Oct 20, 2021 · 1 comment
Closed

Badge Request: LinkedIn #7177

arnonrdp opened this issue Oct 20, 2021 · 1 comment
Labels
service-badge Accepted and actionable changes, features, and bugs

Comments

@arnonrdp
Copy link

📋 It would be nice if we had a LinkedIn badge showing our number of connections.

🔗 I found something related to the API on the Microsoft website and on Stack Overflow there is a lot of stuff, but I'm not sure how this call would work:

@arnonrdp arnonrdp added the service-badge Accepted and actionable changes, features, and bugs label Oct 20, 2021
@arnonrdp arnonrdp changed the title LinkedIn Badge Request: LinkedIn Oct 20, 2021
@calebcartwright
Copy link
Member

Thanks for reaching out and doing some digging on the auth. However, I'm going to close this given those supported auth mechanisms which would not be viable for our consumption model.

In order for Shields to be able to fetch data from an upstream service, our servers have to be able to retrieve the data via anonymous requests, or when authentication is required, we have to be able to use a standard, static authentication mechanisms that are global/non-user specific.

It seems the Connections API only supports explicitly user-authorized applications which necessitate that 3-legged OAuth flow, which simply could not work in the Shields ecosystem.

For anyone that does want this type of badge, the only option I could think of would be to utilize our Custom Endpoint feature, where it'd be your responsibility to go through the OAuth flow to generate the access token and deploy that token with your custom endpoint, and to then refresh your access token every 60 days.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
service-badge Accepted and actionable changes, features, and bugs
Projects
None yet
Development

No branches or pull requests

2 participants