What if stuck on interactive Confluence login?
When using interactive Confluence authentication, WikiTraccs opens Confluence in an automated web browser.
You log in to Confluence and WikiTraccs detects the login mainly by checking whether required cookies are available in the browser.
If a required cookie is missing, the browser window does not close automatically after login. WikiTraccs keeps waiting for the expected cookies, and the interactive login eventually times out.
Cookies
After you sign in, the browser stores authentication cookies and sends them back to Confluence on later requests. In Confluence Cloud, this is usually a small set of cookies such as cloud.session.token and tenant.session.token, while JSESSIONID appears to be phased out by Atlassian as of February 2026. WikiTraccs copies a whitelist of relevant cookies, and for a long time JSESSIONID was mandatory.
Solution for Confluence Cloud
If you are connecting to Confluence Cloud, open Settings and enable Make JSESSIONID cookie optional [interactive authentication, Cloud only]. For Cloud, this fixes the issue in nearly all cases.
Solution for other cookie issues
If the problem is caused by a different missing or unusual cookie, open the Advanced Confluence Authentication Settings dialog and enable Copy all browser cookies (bypass whitelist). Use this when your SSO sets cookies that are not covered by the default whitelist.