CRM icon indicating copy to clipboard operation
CRM copied to clipboard

Social Platform integration

Open rakess70 opened this issue 9 years ago • 9 comments

Just wondering your thoughts on pulling pictures and other user information from facebook.

At the least it might be good to add fields to store social media profiles in the person data. ie. Facebook, twitter, LinkedIn, Google+

We might also be able to tie in signing in with Facebook account.

rakess70 avatar Feb 16 '16 20:02 rakess70

https://developers.facebook.com/docs/graph-api/reference/user/picture/

rakess70 avatar Feb 16 '16 20:02 rakess70

I'd make the issue title more general. The standard social platforms that we could support are

  • Facebook
  • Google+
  • Twitter
  • LinkedIn

dschwen avatar Feb 17 '16 20:02 dschwen

done

rakess70 avatar Feb 17 '16 20:02 rakess70

We might also be able to tie in signing in with Facebook account.

I've been thinking a lot about SAML and OATH for ChurchCRM.

It really could function as a SAML IdP, or an RP given its unique role in the church.

It's a RP in the sense that people log into it, and they may already have some form of account with the church (Active Directory, LDAP, SQL Account Somewhere).

It's an IdP in the sense that it's an authoritative directory of all of the members, with email addresses, and supports enabling the people as users for login.

In short, ChurchCRM could depend on an external auth source like AD, or it could be an auth source for other systems that church members may want to log into.

crossan007 avatar Feb 27 '16 04:02 crossan007

I see the sign in issue as separate from the image capture issue. Any ideas on either front? should these be split into 2 separate requests?

rakess70 avatar Feb 27 '17 18:02 rakess70

yes. separate requests.

crossan007 avatar Feb 27 '17 18:02 crossan007

Additionally -

Using OpenID and JWT for authentication would be really nice, then the site could be integrated into a Single-Sign-On ecology of applications.

crossan007 avatar Mar 10 '18 13:03 crossan007

This is not as useful as it would have been a few years ago. There's also a lot more restrictions in place.

As a result there is not only less information available, but it's harder to set up. Even if it is available in ChurchCRM, the person hosting ChurchCRM would have to apply for (and sometime pay for) API access.

respencer avatar May 03 '24 16:05 respencer

I agree

DawoudIO avatar May 03 '24 18:05 DawoudIO