Issue Summary

Login redirect loop happened when the logged in user has been deleted from connected Jira Internal Directory.

This is reproducible on Data Center: yes

Steps to Reproduce

Confluence: 7.13.7
Jira: 8.13.25

• Use two browser, Browser A and B.
  • Browser A is for the user to be deleted from Jira Internal Directory.
  • Browser B is for Administrator in Jira and Confluence.

1. Step 0: (Confluence) Connect Jira Internal Directory from Confluence.
2. Step 1: (Confluence) Login Confluence with the user in Jira Internal Directory(Browser A).
3. Step 2: (Jira) Delete the user from Jira Internal Directory(Browser B).
4. Step 3: (Confluence) Sync Jira Internal Directory, and check the user will be deleted(Browser B).
5. Step 4: (Confluence) Reload the browser(Browser A).
6. Step 5: (Confluence) Login redirect loop is happened(Browser A).

• sample directoryConfigurationSummary.txt

  === Directories configured ===
  
  Directory ID: 6062081
  Name: Jira Server
  Active: true
  Type: CROWD
  Created date: Wed Sep 21 03:15:44 UTC 2022
  Updated date: Wed Sep 21 23:54:55 UTC 2022
  Allowed operations: [CREATE_ROLE, DELETE_USER, UPDATE_ROLE_ATTRIBUTE, DELETE_ROLE, UPDATE_ROLE, UPDATE_USER_ATTRIBUTE, UPDATE_USER, CREATE_GROUP, DELETE_GROUP, CREATE_USER, UPDATE_GROUP, UPDATE_GROUP_ATTRIBUTE]
  Implementation class: com.atlassian.crowd.directory.RemoteCrowdDirectory
  Encryption type: null
  Attributes: 
  	crowd.sync.incremental.enabled: true
  	application.password: Sanitized by Support Utility
  	crowd.server.url: http://host.docker.internal:13538
  	com.atlassian.crowd.directory.sync.laststartsynctime: 1663804495111
  	crowd.sync.group.membership.after.successful.user.auth.enabled: true
  	directory.cache.synchronise.interval: 3600
  	com.atlassian.crowd.directory.sync.lastdurationms: 581
  	useNestedGroups: false
  	com.atlassian.crowd.directory.sync.issynchronising: false
  	application.name: confluence
  
  Directory ID: 98305
  Name: Confluence Internal Directory
  Active: true
  Type: INTERNAL
  Created date: Thu Mar 29 07:12:15 UTC 2018
  Updated date: Thu Mar 29 07:12:15 UTC 2018
  Allowed operations: [CREATE_ROLE, DELETE_USER, UPDATE_ROLE_ATTRIBUTE, DELETE_ROLE, UPDATE_ROLE, UPDATE_USER_ATTRIBUTE, UPDATE_USER, CREATE_GROUP, DELETE_GROUP, UPDATE_GROUP, CREATE_USER, UPDATE_GROUP_ATTRIBUTE]
  Implementation class: com.atlassian.crowd.directory.InternalDirectory
  Encryption type: atlassian-security
  Attributes: 
  	user_encryption_method: atlassian-security
  

Expected Results

Redirect to login page without redirect loop.

Actual Results

Login redirect loop happened like Step 5.
The user will be redirected to the following urls with loop.

{baseUrl}/login.action?os_destination=%2Findex.action&permissionViolation=true#all-updates
{baseUrl}/index.action

Workaround

• Confluence is able to Read/Write to Jira Internal Directory
  • Delete the user from Confluence user management screen. In this case, the redirect loop doesn't happen.
• Confluence is able to only Read to Jira Internal Directory
  • Currently there is no known workaround for this behavior. A workaround will be added here when available