Websudo is disabled after migration from JIRA cloud to JIRA server
Platform notice: Server and Data Center only. This article only applies to Atlassian products on the Server and Data Center platforms.
Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.
*Except Fisheye and Crucible
Platform Notice: Server, Data Center, and Cloud By Request - This article was written for the Atlassian server and data center platforms but may also be useful for Atlassian Cloud customers. If completing instructions in this article would help you, please contact Atlassian Support and mention it.
Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.
*Except Fisheye and Crucible
Problem
After migrating from JIRA Cloud to JIRA Server, Secure Administrator Sessions are disabled. When you go to the administrator page section it does not ask for your password again.
Diagnosis
- Run below SQL query. This will return one entry if exist in JIRA database, list down the ID # which will be needed under workaround section. If no results return, DO NOT perform the workaround. NOTE: Even editing the jira-config.properties file with jira.websudo.is.disabled = false (or toggling it between false and true) does not enable the Secure Administrator session login prompt.
select * from propertyentry where property_key like '%websudo%';Example Output:
id | entity_name | entity_id | property_key | propertytype
-------+-----------------+-----------+--------------------------+--------------
10044 | jira.properties | 1 | jira.websudo.is.disabled | 1Cause
JIRA database data came from cloud instance will have this entry jira.websudo.is.disabled property and propertytype set to 1(True) in DB propertyentry table.
Workaround
Always back up your data before performing any modifications to the database. If possible, test any alter, insert, update, or delete SQL commands on a staging server first.
Perform below steps if you get a result from above SQL query and propertytype is 1.
- Shutdown JIRA
Run below SQL query to update the propertytype value from 1 (T) to 0 (F). Replace <ID> below with the correct ID(above example would be 10044).
UPDATE propertyentry set propertytype=0 where id=<ID>;- Start JIRA
- Log-in to JIRA and verify the change under Administration -> System Info page, search for jira.websudo.is.disabled property and value should show as false.
Reference:
JRA-44554 - Cannot enable Secure Administrator Sessions after Cloud Migration.