Anonymizing user with REST API throws warning

XMLWordPrintable

    • Type: Bug
    • Resolution: Unresolved
    • Priority: Low
    • None
    • Affects Version/s: 9.4.8
    • None
    • 9.04
    • 3
    • Severity 3 - Minor

      Issue Summary

      During user anonymization using REST API the below warning is thrown although the user anonymization completes successfully:

      "warnings": {
      "com.riadalabs.jira.plugins.insight:rlabs-user-key-handler": {
      "errorMessages": [
      "There was a SQL exception thrown by the Active Objects library:\nDatabase:\n\t- name:Oracle\n\t- version:Oracle Database 19c Standard Edition 2 Release 19.0.0.0.0 - Production\nVersion 19.8.0.0.0\n\t- minor version:0\n\t- major version:19\nDriver:\n\t- name:Oracle JDBC driver\n\t- version:19.3.0.0.0\n\njava.sql.SQLSyntaxErrorException: ORA-00932: inconsistent datatypes: expected - got CLOB\n"
      ],
      

      This warning happens because during the anonymization process, Jira is trying to update a field in AO_8542F1_IFJ_OBJ_ATTR_VAL table and finds a disparity that throws the warning.

      This is reproducible on Data Center: (yes)

      Steps to Reproduce

      1. Install Jira 9.4.8 with Oracle 12c or 19c
      2. Install REST API plugin from marketplace Atlassian REST API Browser
      3. Create sample test users
      4. Use the REST API interface to anonymize the test user.

      Expected Results

      No errors or warning in the logs

      Actual Results

      Warning as shown in the log excerpt
      The below exception is thrown in the xxxxxxx.log file:

      Caused by: Error : 932, Position : 378, Sql = SELECT OAV."INTEGER_VALUE",OAV."ADDITIONAL_VALUE",OAV."TEXT_VALUE",OAV."DATE_VALUE",OAV."ID",OAV."BOOLEAN_VALUE",OAV."OBJECT_ATTRIBUTE_ID",OAV."DOUBLE_VALUE" FROM "AO_8542F1_IFJ_OBJ_ATTR_VAL" OAV JOIN "AO_8542F1_IFJ_OBJ_ATTR" OA ON OA."ID" = OAV."OBJECT_ATTRIBUTE_ID" JOIN "AO_8542F1_IFJ_OBJ_TYPE_ATTR" OTA ON OTA."ID" = OA."OBJECT_TYPE_ATTRIBUTE_ID" WHERE OTA."TYPE" = :1  AND OAV."TEXT_VALUE" = :2 , OriginalSql = SELECT OAV."INTEGER_VALUE",OAV."ADDITIONAL_VALUE",OAV."TEXT_VALUE",OAV."DATE_VALUE",OAV."ID",OAV."BOOLEAN_VALUE",OAV."OBJECT_ATTRIBUTE_ID",OAV."DOUBLE_VALUE" FROM "AO_8542F1_IFJ_OBJ_ATTR_VAL" OAV JOIN "AO_8542F1_IFJ_OBJ_ATTR" OA ON OA."ID" = OAV."OBJECT_ATTRIBUTE_ID" JOIN "AO_8542F1_IFJ_OBJ_TYPE_ATTR" OTA ON OTA."ID" = OA."OBJECT_TYPE_ATTRIBUTE_ID" WHERE OTA."TYPE" = ? AND OAV."TEXT_VALUE" = ?, Error Msg = ORA-00932: inconsistent datatypes: expected - got CLOB
      
              at oracle.jdbc.driver.T4CTTIoer11.processError(T4CTTIoer11.java:498)
              ... 115 more
      2023-10-10 14:21:30,997+0000 JiraTaskExecutionThread-1 INFO admin     [c.a.j.user.anonymize.UserPropertyChangeManager] Ending task (error) for handler: com.riadalabs.jira.plugins.insight:rlabs-user-key-handler, (Errors: {}
          Error Messages: [There was a SQL exception thrown by the Active Objects library:
          Database:
              - name:Oracle
              - version:Oracle Database 12c Enterprise Edition Release 12.2.0.1.0 - 64bit Production
              - minor version:2
              - major version:12
          Driver:
              - name:Oracle JDBC driver
              - version:12.2.0.1.0
      
          java.sql.SQLSyntaxErrorException: ORA-00932: inconsistent datatypes: expected - got CLOB
          ]), took 17.16 ms
      2023-10-10 14:21:30,997+0000 JiraTaskExecutionThread-1 INFO admin     [c.a.j.user.anonymize.UserPropertyChangeManager] Starting task for handler: com.atlassian.servicedesk:servicedesk-user-key-change-handler
      2023-10-10 14:21:31,006+0000 JiraTaskExecutionThread-1 INFO admin     [c.a.j.user.anonymize.UserPropertyChangeManager] Ending task (success) for handler: com.atlassian.servicedesk:servicedesk-user-key-change-handler, took 8.138 ms
      2023-10-10 14:21:31,007+0000 JiraTaskExecutionThread-1 INFO admin     [c.a.j.u.anonymize.operations.UserNameChangeOperationStep] Changing username test
      2023-10-10 14:21:31,008+0000 JiraTaskExecutionThread-1 INFO admin     [c.a.j.user.anonymize.UserPropertyChangeService] Starting task for handler: Anonymizing: Username
      2023-10-10 14:21:31,065+0000 JiraTaskExecutionThread-1 WARN admin     [c.a.r.internal.settings.RateLimitModificationSettingsService] No RL settings found for user: [JIRAUSER10100] - can't delete!!
      2023-10-10 14:21:31,224+0000 JiraTaskExecutionThread-1 INFO admin     [c.a.j.user.anonymize.UserPropertyChangeService] Ending task (success) for handler: Anonymizing: Username
      2023-10-10 14:21:31,224+0000 JiraTaskExecutionThread-1 INFO admin     [c.a.j.u.anonymize.operations.UserNameChangePluginPointsOperationStep] Changing username in extension points for UserPropertyChangeParameter{original='test', target='jirauser10100'}
      

      Workaround

      Currently, there is no known workaround for this behavior. A workaround will be added here when available. This warning can be ignored since the user anonymization is completed successfully.

            Assignee:
            Unassigned
            Reporter:
            Didi (Inactive)
            Votes:
            2 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated: