How's this different than storing the information in a database w/ appropriate access controls? Either way, you need something (database auth credentials vs a pub/priv key pair) available by which the apps can authenticate to get the real data you want.
But otherwise, yeah, you could front-end the database with some rpc/api too. :) On Mon, Apr 6, 2009 at 3:53 PM, konqi <[email protected]> wrote: > My idea of a nice way to do this would be to use a webservice. > 1. Client requests authentication data using its public key. > 2. Server checks pubkey against stored pubkey in its database (simple > authentication). > 3. Server uses public key to encrypt the authentication data and sends > back XML-Response. > 4. Client can decrypt the data using its private key and continue. > Server uses a Database with a (neat) user interface. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google Apps APIs" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/google-apps-apis?hl=en -~----------~----~----~----~------~----~------~--~---
