Clarity PPM - REST API calls using Bearer Tokens do not release DB Connections after serving request
Article ID: 186979
Clarity PPM On PremiseClarity PPM SaaS
STEPS TO REPRODUCE: 1. Go into the Modern UX -> Administration -> API Keys -> Clients. Define a client that can be used 2. Go into "API Keys" from the top right corner of any page in Modern UX and create an API Key
3. Restart the app service and make note of the connections open using the following URL. Do not let any other user login to the application. http://HOST_NAME/niku/apache?alias=clarity&level=less&pool=less
4. Use the API Key generated in Step 2 along with Client defined in Step 1 as headers, to make a GET Call of the format shown below: http://HOST_NAME/ppm/rest/v1/projects?limit=5&offset=0&sort=_internalId 5. Make note of the total ACTIVE connections using the same URL as in Step 3 6. Repeat Step 4 7. Make note of the total ACTIVE connections using the same URL as in Step 3
6. Restart the app service again
7. Now, instead of the Bearer Token, use Basic Authentication to make the GET call from Step 4 8. Make note of the total ACTIVE connections using the same URL as in Step 3 9. Repeat Step 7 10. Make note of the total ACTIVE connections using the same URL as in Step 3
Expected Result: Count of ACTIVE connections does not increase in Steps 5, 7, 8, 10 Actual Result: Count of ACTIVE connections increases in Steps 5 and 7. They do not increase in Steps 8 and 10
Version: 15.7, 15.7.1, 15.8
This is a known defect, DE54038.
This is fixed in Clarity version 18.104.22.168, 22.214.171.124, 15.8.1.
WORKAROUND: If possible, use Basic Authentication for the time being, while using REST API. Make sure to secure the password if doing this