Login without DB UI intervention?

You guys ROCK! I had read that post earlier and the guys' inability to listen made me miss the key part. To summarize for Oauth1 (until we get v2 for objC) you run a connect using linkfromController and then dump the MPOAuthCredentialConcreteStore creds for the userid of the dropbox you want to connect to. First you have to get the real userid by making a request for the account info via the loadAccountInfo method (at first I thought it was the name or email addy), then you call the credentialStoreForUserId method to extract the creds from the local SDK framework.

Take the stored token and secret returned in the creds and stuff them into the sharedSession via the updateAccessToken:accessTokenSecret:forUserId method in the future and VOILA you are linked. In fact the isLinked method of DBSession only looks to see if there is an entry in the creds array internally so it is then ready to rock.

As you guys pointed out storing the token and secret in the app is a security risk (whose extent also depends on the nature of the data being stored). A smart developer might fetch these from his own website using other secure means so as to keep the app secure and to enable the developer to reissue the credential periodically without breaking the app.

Thanks again for helping me see the light! Hopefully the v2 interfaces for objC will not be drastically different than the v1 when they come? I am quite pleased with how easy the integration is compared to the other cloud storage services.

One final question on the topic. If I wanted to use this technique as a sideband storage to our own dropbox silently AND to enable users with the regular auth cycle for their datastorage I am guessing I need to setup 2 DBSessions? Perhaps put the user's dropbox on the shared Session and do our sideband transmissions to our own dropBox on another DBsession?