Hi,
I've been following the Twitter's official sign-in implementation (https://dev.twitter.com/web/sign-in/implementing) and wanted to confirm whether a few steps occur when creating credentials within Tweetinvi.
My sign-in process is the typical flow seen most everywhere -> user clicks sign in button, obtain redirect url via GetAuthorizationURLForCallback(), redirect user, analyze params sent to callback, obtain access token.
Within the second step - obtaining the URL, Twitter says we should store auth_token oauth_token_secret for verification within step 4 - analyzing params. Does tweetinvi do a before and after verification anywhere, in particular within GetCredentialsFromCallbackURL() ?
Thanks!
I've been following the Twitter's official sign-in implementation (https://dev.twitter.com/web/sign-in/implementing) and wanted to confirm whether a few steps occur when creating credentials within Tweetinvi.
My sign-in process is the typical flow seen most everywhere -> user clicks sign in button, obtain redirect url via GetAuthorizationURLForCallback(), redirect user, analyze params sent to callback, obtain access token.
Within the second step - obtaining the URL, Twitter says we should store auth_token oauth_token_secret for verification within step 4 - analyzing params. Does tweetinvi do a before and after verification anywhere, in particular within GetCredentialsFromCallbackURL() ?
Thanks!