Browser authenication cookie


#1

So my question sounds weird I know…I have a successful WP8 tweetsharp integration. I authenticate, authorize and store the verification. I later in a separate operation use this verification code to reinitialise the TweetSharp service and post successfully.

However, if I set my callback url to twitter.com instead of my own xyz.com I expected to be logged in to twitter as the browser is the same browser that performed all those successful operations above…just like OAuth for facebook. But it doesn’t, it directs to the mobile.twitter.com/signup url and I seemingly have no web session, so I guess no cookie is created.

So

  1. Is there a way around this in TweetSharp like setting the UserAgent property or something like that?
  2. Is my architecture incorrect and is there an alternative approach that will authenticate both my app and the browser in said app?

Thanks for any input
Michael