You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
One question, does OAuth header regenerated after 'GetRequestToken' method execution?
var tokenResponse = await authorizer.GetRequestToken("https://api.some_app.com/v0/oauth/initiate");
I meant, for instance, first, when we compute the hash, we did it during app start. We create signature key as key=encode('consumerSecret&') and buffer as Request method&link&blablabla.
But after we get request token, the signature key should be renew as: key=encode('consumerSecret&requestToken.Secret') and buffer as usual.
So, seems like, signature key after getting of request token do not renewed and when we try to navigate by authorize url
authorizer.BuildAuthorizeUrl("https://api.some_app.com/v0/oauth/authorize", requestToken);
we will have response like '< title >Authorization error</ title >'.
error: Invalid token or something went wrong. Please, return to application page and try to authorize once more.
Is it possible to force regenerate a signature, but at the same time keep 'auth_nonce' and 'oauth_timestamp' old values. Or even does it make sense?
The text was updated successfully, but these errors were encountered:
Hello,
One question, does OAuth header regenerated after 'GetRequestToken' method execution?
var tokenResponse = await authorizer.GetRequestToken("https://api.some_app.com/v0/oauth/initiate");
I meant, for instance, first, when we compute the hash, we did it during app start. We create signature key as key=encode('consumerSecret&') and buffer as Request method&link&blablabla.
But after we get request token, the signature key should be renew as: key=encode('consumerSecret&requestToken.Secret') and buffer as usual.
So, seems like, signature key after getting of request token do not renewed and when we try to navigate by authorize url
authorizer.BuildAuthorizeUrl("https://api.some_app.com/v0/oauth/authorize", requestToken);
we will have response like '< title >Authorization error</ title >'.
error: Invalid token or something went wrong. Please, return to application page and try to authorize once more.
Is it possible to force regenerate a signature, but at the same time keep 'auth_nonce' and 'oauth_timestamp' old values. Or even does it make sense?
The text was updated successfully, but these errors were encountered: