-
Notifications
You must be signed in to change notification settings - Fork 9
Unable to get access token to save. #26
Comments
Got the error message when tried to retrieve... Even with the latest snap shot. flow that has been tried...<objectstore: |
could you paste what you are trying to achieve? |
Hi Fernandez, Thanks for your response. Below it the piece of code that i have tried, I am calling object store immediately after authorize. But it is giving error as mentioned above. <flow name="authorize_flow" doc:name="authorize_flow"
doc:description="This flow takes care of Authentication of User">
<http:inbound-endpoint exchange-pattern="request-response"
host="${mule.host}" port="${mule.port}" path="fb_authorize" doc:name="HTTP" />
<facebook:authorize config-ref="Facebook"
doc:name="Facebook" />
<objectstore:store key="OAuthAccessToken"
value-ref="#[header:INBOUND:OAuthAccessToken]" />
<objectstore:store key="OAuthAccessTokenSecret"
value-ref="#[header:INBOUND:OAuthAccessTokenSecret]" />
<flow-ref name="getUser" doc:name="Flow Reference" />
</flow>
|
Sorry, xml is getting formatted in the comment. Precisely, i am calling authorize with the connector and then calling object store to save access token. Then i got the error as mentioned in my first comment. |
Hi, If you are using the latest version of facebook-connector (which relays on DevKit 3.5.x) DevKit will use a different mechanism to save/restore the tokens. Take a look at http://blogs.mulesoft.org/oauth-2-just-got-a-bit-easier/ and http://blogs.mulesoft.org/mule-oauth2-support-even-easier-still/ for some deep knowledge on what has changed HTH, |
Hi,
I need to save Access token for the logged in user. But, facebook connector is giving wrong access token in authorize response. How could I get the correct access token that is being used and save it.?
The text was updated successfully, but these errors were encountered: