oAuth client credentials - error

when i try to create connected system to use linkedin api by using oAuth client credential, getting the below error message.

Token Request Endpoint :

www.linkedin.com/.../accessToken

OAuthResultMessage

Authorization unsuccessful. We could not connect to the token request endpoint. Check the configuration and confirm that it matches what you registered with the protected resource.

Any suggestions?

  Discussion posts and replies are publicly visible

Parents Reply
  • 0
    Certified Senior Developer
    in reply to Steven Miccile

    Hi  , hopefully a quick question on this. With the Authorisation Link, when I authorise via the login prompt I can access data no problem via the API's without using anything in the header or body. However, when I then access via the mobile interface I need to sign in again - is this because it is stored on the client side?

    Also, how do you access the token to allow it to be stored after using the Authorisation Link? I am assuming access to the token and then refreshing in the background would then prevent having to re-log in once authenticated?

    p.s - I am using the FitBit API's as a demo authentication project for learning

Children
  • It sounds like you are using OAuth 2.0 Authorization Code within your Connected System. The user's token is stored within the Appian Database and you cannot programmatically access it although you can see it if you test the integration object and look at the HTTP request details. Web vs mobile should not affect the functionality, but the token will expire eventually based on FitBit's settings and the user would need to re-authenticate. The best way to check if you need to re-authenticate is to try to make an integration call as the user and if it is unsuccessful, show the user the a!authorizationLink. Remember - the tokens for Auth Code grant type are at a per-user level, meaning each Appian user needs to go through the authentication flow.