-
Type:
Bug
-
Resolution: Unresolved
-
Priority:
Medium
-
None
-
Affects Version/s: 9.2.19, 10.2.11
-
Component/s: Core - Content REST APIs
-
2
-
Severity 3 - Minor
-
12
Issue Summary
401 error while using third party SSO token based authentication for rest API's post upgrade to 9.2.19.
Steps to Reproduce
- Create a script to capture Page content using Confluence Rest API.
- As a part of this script, use a third party SSO tokens + user for authentication(such as Kantega SSO tokens).
- Run the script/push in the request to get the page content and capture the JSESSIONID.
- Use this same JSESSIONID to push in further requests.
Expected Results
Request works fine till session expiry kicks in.
Actual Results
401 error is observed against this JSESSIONID.
Workaround
Use SSO token + user across all requests i.e. push in a new request each time.