Describe the issue or problem
When setting ORCID member credentials at the site level, our ORCID client secret is exposed in the journal settings. Are we missing a configuration setting somewhere? ![]()
Steps I took leading up to the issue
We recently upgraded our journals from 3.3 to 3.5.0-5. While setting up the new ORCID configuration we noticed that when we use site settings to “Enable ORCID functionality site-wide,” our institutional ORCID client secret (in addition to the Client ID), is visible in each of the individual journal sites in Settings → Users and Roles → ORCID instead of being hashed out. We have temporarily resolved this by setting up ORCID for each journal rather than using the site settings, but have some multi-site instances that would benefit from managing this at the site level rather than at the journal level.
What application are you using?
OJS 3.5.0-5