-
Notifications
You must be signed in to change notification settings - Fork 0
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
LinkedIn Connector #141
Comments
@srenault-meeds @margondicco please check for functional requirements. It's similar to Twitter connector. |
Thanks. Feedbacks/questions:
|
I meant the connector. fixed.
connections only (followers does not seem available in the APIs so far) |
@srenault-meeds @margondicco mockups added |
Ok for me. I let @margondicco check it as well |
|
Work in Progress
Work in Progress
Work in Progress
feat: Linkedin Connector - Meeds-io/MIPs#141
Work in Progress
fix: Linkedin Connector - Meeds-io/MIPs#141
Work in Progress
Work in Progress
fix: Linkedin Connector - Meeds-io/MIPs#141
Work in Progress
feat: Linkedin Connector - Meeds-io/MIPs#141
Work in Progress
feat: Linkedin Connector - Meeds-io/MIPs#141
Work in Progress
Work in Progress
feat: Linkedin Connector - Meeds-io/MIPs#141
Work in Progress
feat: Linkedin Connector - Meeds-io/MIPs#141
Work in Progress
feat: Linkedin Connector - Meeds-io/MIPs#141
Rationale
LinkedIn is a major platform for all work organizations to meet workers. Many Web3 projects and Web2 brands and companies use it to reach an audience and promote their organization, products, or services. Meeds can help design fair and equitable incentives for contributors who support their organizations on LinkedIn.
1. Functional Requirements
Contributor
User Settings
>Other Apps
Program Owner
Like
Comment
Repost
Mention
Follow
Work For
Hub Administrator
As a Hub administrator, I should configure the LinkedIn connector to let users connect their LinkedIn account to their Meeds profile

As a Hub administrator, I may configure the LinkedIn connector to use my oAuth Application credentials (
Client ID
andClient Secret
)Impacts
Gamification
Notifications
Analytics
Unified Search
2. Technical Requirements
Expected Volume & Performance
Security
The oAuth tokens SHOULD NOT be stored in the Meeds database; they should only be used to validate user accounts on external providers.
LinkedIn's API key (secret) to transmit triggered events into the Meeds server MUST be generated by the hub administrator using a specific UI in the Gamification administration UI inside LinkedIn connector settings. This Meeds API Key has to be encrypted using
CodecInitializer
before being stored in the database.The Hub administrator MUST provide LinkedIn oAuth Client and Secret keys in a dedicated UI. Those oAuth Keys must be encrypted using
CodecInitializer
before being stored in the database. These keys will be used to validate the oAuth token provided by the user from the Meeds Server to the LinkedIn Server.Extensibility
Configurability
Upgradability
Existing Features
Feature Flags
Other Non-Functional Requirements
3. Impacts
Documentation
Training
4. Software Architecture
Security
Access
Services & processing
Data and persistence
Clustering
Multitenancy
Integrations
The connector will use Community Management APIs
Migration strategy
5. Annexes
The text was updated successfully, but these errors were encountered: