AuthFlow.InitAuthentication Only Giving oauth_token

[DeliverPhilip]

I am working on Authentication code for Twitter using Teetinvi, but the authentication code shown in the documentation only ever gives back an oauth_token in the API response. I am using this code:

public string TwitterAuth()
        {
            var appCreds = new ConsumerCredentials(ConsumerKey, ConsumerSecretKey);

            // Specify the url you want the user to be redirected to
            var redirectURL = "http://" + HttpContext.Current.Request.Url.Authority + "/Clients/ValidateTwitter";
            if (redirectURL.Contains("localhost"))
                redirectURL = "http://" + "127.0.0.1" + "/Clients/ValidateTwitter";
            authenticationContext = AuthFlow.InitAuthentication(appCreds, redirectURL);

            return authenticationContext.AuthorizationURL;
        }

Where ValidateTwitter is an approved redirect in the Twitter App settings. ValidateTwitter runs this code:

public ActionResult ValidateTwitter()
        {
            var twitterHelper = new DeliverMedia.Web.Framework.TwitterHelper();
            var twitterWrapper = new DeliverMedia.TwitterServices.TwitterApiWrapper(twitterHelper.Consumer, twitterHelper.ConsumerSecret);
            twitterWrapper.ValidateTwitterAuth();

            return View();
        }`

And ValidateTwitterAuth is:

`public (string accessToken, string secretAccessToken) ValidateTwitterAuth()
        {
            // Get some information back from the URL
            var verifierCode = HttpContext.Current.Request.Params.Get("oauth_verifier");

            // Create the user credentials
            var userCreds = AuthFlow.CreateCredentialsFromVerifierCode(verifierCode, authenticationContext);

            // Do whatever you want with the user now!
            var creds = Tweetinvi.User.GetAuthenticatedUser(userCreds);
            return (creds.Credentials.AccessToken, creds.Credentials.AccessTokenSecret);
        }

I split ValidateTwitter and ValidateTwitterAuth because the project that has the TweetInvi code is separate from the project that has my webviews. The TweetInvi code is then called through helpers and wrappers in the webview project.

But authenticationContext in TwitterAuth() always only has an oauth_token parameter, while the documentation says it should have oauth_token, oauth_verifier and authorization_id.

I am using the newest version of TweetInvi

[linvi]

Hello there,

I am not sure I understand what you mean by:

I split ValidateTwitter and ValidateTwitterAuth because the project that has the TweetInvi code is separate from the project that has my webviews. The TweetInvi code is then called through helpers and wrappers in the webview project.

Effectively if you have the 2 parts of the application in 2 different processes Tweetinvi default authentication will not work out of the box.

Please read the following section : https://github.com/linvi/tweetinvi/wiki/Authentication#web-application-considerations

Also please note that Tweetinvi 5.0 should make things easier to follow up for the authentication process with the introduction of the AuthenticationRequestStore.

Read more here : https://linvi.github.io/tweetinvi/dist/authentication/authentication-url-redirect.html

[DeliverPhilip]

Thank you for the response! What I meant is my web views, and the code for them, are stored in a separate project than the TweetInvi code. The web view project then calls the TweetInvi project to access the TweetInvi code.

Is there any ETA on when 5.0 will become available? I just checked, and I am using TweetInvi 4.0.3, and it says it is the most up to date version available.

Thanks again for the help!

[linvi]

I am not usually good with ETA. But as mentioned my objective is to make it available by the end of the month.

What changes can happen between alpha and release:

• DateTime changed to DateTimeOffset: Use DateTimeOffset #1030 (likely)
• Methods renamed (unlikely)
• Properties renamed (unlikely)

Currently I am focusing on writing the documentation. As soon as this is done and the issue above is complete this will be pushed in beta.

The development stage of 5.0 is already very advanced and you can already start using the alpha from nuget.

https://www.nuget.org/packages/TweetinviAPI