Android OAuth:retrieveAccessToken() 上的异常

问题描述

我正在为我的 Android 应用设置 OAuth.为了测试它，我做了以下事情:将 signpost-core-1.2.1.1.jar 和 signpost-commonshttp4-1.2.1.1.jar 添加到我的项目中，添加变量CommonsHttpOAuthConsumer consumer"和CommonsHttpOAuthProvider provider"，并在单击按钮时执行以下操作:

I'm setting up OAuth for my Android app. To test it I did the following:Added signpost-core-1.2.1.1.jar and signpost-commonshttp4-1.2.1.1.jar to my project, added the variables "CommonsHttpOAuthConsumer consumer" and "CommonsHttpOAuthProvider provider" and did the following when the button is clicked:

consumer = new CommonsHttpOAuthConsumer("xxx", "yyy");
provider = new CommonsHttpOAuthProvider("https://api.twitter.com/oauth/request_token",
                    "https://api.twitter.com/oauth/access_token",
                    "https://api.twitter.com/oauth/authorize");

oauthUrl = provider.retrieveRequestToken(consumer, "myapp://twitterOauth");
persistOAuthData();
this.startActivity(new Intent(Intent.ACTION_VIEW, Uri.parse(oauthUrl)));

persistOAuthData() 执行以下操作:

persistOAuthData() does the following:

protected void persistOAuthData()
{
    try
    {
        FileOutputStream providerFOS = this.openFileOutput("provider.dat", MODE_PRIVATE);
        ObjectOutputStream providerOOS = new ObjectOutputStream(providerFOS);
        providerOOS.writeObject(this.provider);
        providerOOS.close();

        FileOutputStream consumerFOS = this.openFileOutput("consumer.dat", MODE_PRIVATE);
        ObjectOutputStream consumerOOS = new ObjectOutputStream(consumerFOS);
        consumerOOS.writeObject(this.consumer);
        consumerOOS.close();
    }
    catch (Exception e) { }
}

因此，在打开浏览器之前保存了消费者和提供者，如此处所述.

So, the consumer and the provider are saved before opening the browser, like described here.

在 onResume() 方法中，我加载提供者和消费者数据并执行以下操作:

In the onResume() method I load the provider and consumer data and do the following:

    Uri uri = this.getIntent().getData();
    if (uri != null && uri.getScheme().equals("myapp") && uri.getHost().equals("twitterOauth"))
    {
        verifier = uri.getQueryParameter(oauth.signpost.OAuth.OAUTH_VERIFIER);
        if (!verifier.equals(""))
        {
            loadOauthData();
            try
            {
                provider.retrieveAccessToken(consumer, verifier);
            }
            catch (OAuthMessageSignerException e) {
                e.printStackTrace();
            } catch (OAuthNotAuthorizedException e) {
                e.printStackTrace();
            } catch (OAuthExpectationFailedException e) {
                e.printStackTrace();
            } catch (OAuthCommunicationException e) {
                e.printStackTrace();
            }
        }
    }

那么，什么有效:1) 我确实得到了一个 requestToken 和一个 requestSecret.2) 我确实得到了 oauthUrl.3)我被定向到浏览器页面来授权我的应用程序4) 我被重定向到我的应用程序.5)我确实得到了验证者.但是调用retrieveAccessToken(consumer, verifier) 失败，并显示OAuthCommunicationException 说与服务提供者的通信失败:null".

So, what works:1) I do get a requestToken and a requestSecret.2) I do get the oauthUrl.3) I am directed to the browser page to authorize my app4) I am getting redirected to my app.5) I do get the verifier.But calling retrieveAccessToken(consumer, verifier) fails with an OAuthCommunicationException saying "Communication with the service provider failed: null".

有谁知道可能是什么原因?有些人似乎在获取 requestToken 时遇到问题，但效果很好.我想知道我的应用程序还包含了分段上传所需的 apache-mime4j-0.6.jar 和 httpmime-4.0.1.jar 是否可能是一个问题.

Does anyone know what might be the reason? Some people seem to have problems getting the requestToken, but that just works fine. I wonder if it might be a problem that my app has also included the apache-mime4j-0.6.jar and httpmime-4.0.1.jar which I need for multipart upload.

推荐答案

好的，我想通了.也许这对其他人有帮助:

Okay, I figured it out. Maybe this is helpful to others:

首先，您不需要保存整个消费者和提供者对象.您需要做的就是存储 requestToken 和 requestSecret.幸运的是，这些是字符串，所以你不需要将它们写入磁盘或任何东西.只需将它们存储在 sharedPreferences 或类似的东西中.

First of all, you do not need to save the whole consumer and provider object. All you need to do is store the requestToken and the requestSecret. Luckily, those are Strings, so you don't need to write them to disk or anything. Just store them in the sharedPreferences or something like that.

现在，当您被浏览器重定向并调用 onResume() 方法时，只需执行以下操作:

Now, when you get redirected by the browser and your onResume() method is called, just do the following:

//The consumer object was lost because the browser got into foreground, need to instantiate it again with your apps token and secret.
consumer = new CommonsHttpOAuthConsumer("xxx", "yyy");

//Set the requestToken and the tokenSecret that you got earlier by calling retrieveRequestToken.
consumer.setTokenWithSecret(requestToken, tokenSecret);

//The provider object is lost, too, so instantiate it again.
provider = new CommonsHttpOAuthProvider("https://api.twitter.com/oauth/request_token",
                                "https://api.twitter.com/oauth/access_token",
                                "https://api.twitter.com/oauth/authorize");
//Now that's really important. Because you don't perform the retrieveRequestToken method at this moment, the OAuth method is not detected automatically (there is no communication with Twitter). So, the default is 1.0 which is wrong because the initial request was performed with 1.0a.
provider.setOAuth10a(true);

provider.retrieveAccessToken(consumer, verifier);

就是这样，您现在可以使用 getToken() 和 getTokenSecret() 接收令牌和密钥.

That's it, you can receive the token and the secret with getToken() and getTokenSecret(), now.

这篇关于Android OAuth:retrieveAccessToken() 上的异常的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持！