IBM Support

Load balanced ClearQuest systems may return an error '401: invalid_expired_token' when attempting to establish a project relationship



When using the administration pages of an OSLC consumer to establish a project relationship with an IBM Rational ClearQuest database in a load balanced system, a '401: invalid_expired_token' might be displayed after supplying valid ClearQuest credentials from the authorization window.


In a load balanced Rational ClearQuest environment, the Oauth consumer key required to authorize creation of a project relationship is not defined or is not yet loaded on the server that handles the operation. The consumer key registry on the failing server might not be synchronized with the current content in the ClearQuest repository.

Resolving The Problem

To resolve authentication problems caused by invalid Oauth consumer keys, use one of the following methods.

Method 1:

Initiate creation of the new project relationship from the ClearQuest Web client. This approach assumes that the ClearQuest server acts as both an OSLC consumer and an OSLC provider for the peer product. See the ClearQuest Information Center topic Configuring project relationships for help establishing project relationships using the ClearQuest Web client.

Method 2:

After adding an OSLC friendship to a schema repository for a ClearQuest Web server in a load balanced environment, synchronize the OSLC configuration settings for all ClearQuest Web servers in the load-balanced environment with those saved in the ClearQuest repository by logging into each ClearQuest Web server.


In a load balanced ClearQuest system lbcq that includes three active server nodes lbcq_1, lbcq_2, and lbcq_3, you complete the following steps in Rational Team Concert to add an OSLC friendship for a ClearQuest schema.

  1. Logon as an administrator to a Rational Team Concert server and establish a friendship to cqschema hosted on the load balanced system using the following discovery URL:


  2. Click the Rational Team Concert link to Grant access for the provisional key. When prompted, provide ClearQuest administrator credentials to authorize the provisional key.

After completing these steps, a new Oauth consumer key is saved in memory on the ClearQuest server that handles the request and in the cqschema ClearQuest repository. In this case, the load balanced system includes three ClearQuest servers, but the new Oauth consumer key is only available on the server that processed the initial friendship request.

To refresh OSLC configuration settings on all of the servers in the load balanced system, log in to each server individually. You can log in by using any ClearQuest user id that is subscribed to cqschema. In this example, you would log in to the cqschema repository on each of the ClearQuest web servers:


During the log in operation, the OSLC registry settings for cqschema repository are refreshed from the repository contents if necessary. After synchronizing OSLC configuration settings on all servers in the load balanced system, you should be able to complete the task of establishing a project relationship from Rational Team Concert.

See technote 1644559 for ideas about keeping OSLC configuration settings synchronized in a load balanced ClearQuest Web environment.

[{"Product":{"code":"SSSH5A","label":"Rational ClearQuest"},"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Component":"Integrations: 3rd Party","Platform":[{"code":"PF002","label":"AIX"},{"code":"PF010","label":"HP-UX"},{"code":"PF016","label":"Linux"},{"code":"PF027","label":"Solaris"},{"code":"PF033","label":"Windows"}],"Version":"","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
16 June 2018