How to Correct Communication Issues with your Connector due to an expired token.
Background: Concur handles authentication via a mechanism called oAuth, or Open Authorization - this method of handling secure communication has a user enter their username and password to receive a security token that will allow applications to communicate without requiring a user enter their password each time.
These tokens expire, but should refresh automatically so long as the grant to communicate remains active. Concur occasionally will have scenarios arise where tokens expire and cause communication failures with your connector.
This article will describe how to correct failures communicating to Concur because of an expired token.
- Log into www.concursolutions.com with the wsadmin account (or one with similar privileges) and go to App Center.
Search for "Blackbox" to find the Expense and Invoice Connector listings (note, if you have Expense and Invoice you will have two Blackbox Connector for Concur instances that will need to be enabled). Click into the listing for the Expense or Invoice application, whichever you are connecting.
Click Connect
Check off all boxes required for the App and Click "I Agree"
In the new window, log into the Blackbox connector application if prompted
- Select the Connector Instance you are working with (NOTE: If you use Expense and Invoice, you must choose the correct instance to avoid issues with data synchronization). Be sure to check off the boxes for terms and conditions and the privacy policy, then click Continue.
- You should see a success response:
and in Concur the App will show as "Connected"
- Repeat this process for the other product you use (only if you use both Concur Invoice and Expense).
- Retry any missed jobs by clicking the corresponding button in Deltek.