[Pidgin] #9974: Instructions for building libpurple without certain protocols, passing authentication through pam?

[Pidgin]

#9974: Instructions for building libpurple without certain protocols, passing
authentication through pam?
-------------------------+--------------------------------------------------
 Reporter:  mwsealey     |        Owner:           
     Type:  enhancement  |       Status:  pending  
Milestone:               |    Component:  libpurple
  Version:  2.6.1        |   Resolution:           
 Keywords:               |  
-------------------------+--------------------------------------------------
Changes (by darkrain42):

  * status:  new => pending


Comment:

 This would have been better addressed on the support@ or devel@ mailing
 lists.

 Replying to [ticket:9974 mwsealey]:
 > Hi,
 >
 > We have a couple of requirements for a custom build of Pidgin for a
 commercial product. Of course it will be fully open-source but I am
 wondering of the best ways to go about two things..
 >
 > 1) build pidgin and libpurple with a limited set of protocols. It's
 possible to do this on Windows by hacking around in the makefiles but
 there are no configure options for Linux for this. We basically just want
 to support Jabber and provide server side support for the rest.

 Look at `./configure --help | less`. There is indeed a configure option
 for this.

 > 2) pass through authentication of the account (i.e. automatic username
 perhaps with password confirmation) - this may be through pam_http or some
 other API on user login to Linux, but basically they will already have a
 "ticket" on our server, and Google OAuth/SAML/OpenID login can be
 automatically gained through this. We would like to streamline the
 experience as much as possible for users by not requiring them to enter
 their passwords or do any account setup too much.

 You will need to patch the XMPP prpl to allow for this authentication or
 integrate it using GSSAPI/Kerberos (I think. I actually have little
 experience with this, but it's been used to do SSO on Windows with XMPP
 servers).

  > Are these tasks easy? We could forego the second option with a simple
 setup UI or an automated script that fixed the Pidgin configuration on
 login, but the first - stripping Pidgin down and not allowing plugins or
 external code for security and simplicity reasons - is very important to
 us. We have gotten so far and now we need some advise.

-- 
Ticket URL: <http://developer.pidgin.im/ticket/9974#comment:1>
Pidgin <http://pidgin.im>
Pidgin