ORCID client secret exposed to journal manager when set at site level

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? :grimacing:

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

Hello @Sonya_Betz . Thank you for bringing this to our attention. I looked into it and was able to reproduce the problem. This was resolved for 3.6 as part of a larger effort to encrypt various credential fields. I have created a ticket to get it into the next 3.5.0-6 release. You can follow it here : #13336

Hola, ¿cómo se puede hacer para ingresar el ORCID manualmente como en el 3.4 sin tener que pagar una membresía como editor en ORCID? Admás de agregar la biografía del autor específica para un articulo en particular manualmente sin tener en cuenta la Biografia cargada en ORCID