iThenticate Plagiarism Detector Plugin EULA Issue

jorgelpolanco
Tue, 03 Mar 2026 00:37:16 +0000
Software Support

Describe the issue or problem
Hi everyone,

I am currently reviewing the EULA (End User License Agreement) acceptance workflow in our installation and have run into a specific issue.
For our specific setup, we need to keep the autosubmit feature disabled. However, based on my testing and findings so far, the mechanism that prompts users to review and accept the EULA appears to be directly tied to the autosubmit process.

Because autosubmit is turned off, our journal editors do not get the prompt, leaving us without a clear native pathway for them to formally sign or agree to the EULA within the system.

Question: Is there an alternative interface, setting, or recommended workflow where editors can review and sign the EULA when autosubmit is disabled? Any guidance or workarounds you could share would be greatly appreciated.

Thanks in advance!

Best regards,
Jorge

Steps I took leading up to the issue
Installed and activated the iThenticate plugin.

Configured the plugin settings through the web interface.

Set the option “disableAutoSubmission = On” (or enabled the “Disable automatic submission” checkbox) via the administration UI.

Prepared a document/submission and, as an editor, attempted to submit it to iThenticate in workflow, submission.

What application are you using?
OJS 3.4

Additional information
Error en la bitácora: [Mon Mar 02 17:57:46.XXXXXX 2026] [php:notice] [pid XXXXXXX] [client [INTERNAL_IP]] iThenticate API request to https://[INSTITUTION].turnitin.com/api/v1/submissions for POST method failed with options Array
(
[headers] => Array
(
[X-Turnitin-Integration-Name] => Plagiarism plugin for OJS/OMP/OPS
[X-Turnitin-Integration-Version] => 1.0.8.3
[Authorization] => Bearer [REDACTED_TOKEN]
[Content-Type] => application/json
)

[json] => Array
    (
        [owner] => author_XXXXX
        [title] => [REDACTED_ARTICLE_TITLE]
        [submitter] => user_1
        [owner_default_permission_set] => USER
        [submitter_default_permission_set] => ADMINISTRATOR
        [metadata] => Array
            (
                [owners] => Array
                    (
                        [0] => Array
                            (
                                [id] => author_XXXXX
                                [given_name] => [AUTHOR_NAME]
                                [family_name] => [AUTHOR_SURNAME]
                                [email] => [AUTHOR_EMAIL]
                            )
                    )

                [submitter] => Array
                    (
                        [id] => user_1
                        [given_name] => [ADMIN_USER]
                        [family_name] => [ADMIN_USER]
                        [email] => [INSTITUTIONAL_EMAIL]
                    )

                [original_submitted_time] => 2026-03-02T17:57:45-06:00
            )
    )
[verify] =>
[exceptions] =>

)
, referer: https://[OJS_DOMAIN]/index.php/[JOURNAL]/workflow/index/5736/1

[Mon Mar 02 17:57:46.XXXXXX 2026] [php:notice] [pid XXXXXXX] [client [INTERNAL_IP]] {“success”:false,“status”:451,“code”:“UNAVAILABLE_FOR_LEGAL_REASONS”,“reference”:“[REFERENCE_ID]”,“debug_message”:“user_1 has not accepted a EULA”,“message”:“user_1 has not accepted a EULA”}, referer: https://[OJS_DOMAIN]/index.php/[JOURNAL]/workflow/index/5736/1

[Mon Mar 02 17:57:46.XXXXXX 2026] [php:notice] [pid XXXXXXX] [client [INTERNAL_IP]] iThenticate submission 5736 failed: Error de procesamiento de iThenticate para el envío 5736: No se pudo crear el envío en iThenticate para el ID del archivo de envío: 33673, referer: https://[OJS_DOMAIN]/index.php/[JOURNAL]/workflow/index/5736/1

2 posts - 2 participants