Yes, but make sure to keep account name general since it will be in the metadata (under data source name on the ORCID record).
This can happen when the Journal Manager has enabled the ORCID Profile Plugin but did not configure it with the journal’s ORCID API information. Go to Website Settings > Plugins, find the ORCID Profile Plugin, and open the Settings link below it. If required fields are blank, you need to follow the steps in Enable and Configure the ORCID Profile Plugin in OJS.
If you are using a version of OJS earlier than 3.1.1 and the link starts with “https” instead of “http” the last number in the link will get cut off. ORCiD previously explicitly required the use of http, but now they permit (and recommend) https. Support for this was added in OJS 3.1.1.
You can resolve this issue by upgrading your OJS install to 3.1.1 or later, or by removing the “s” from “https” in the ORCID link.
You will need to register a redirect_uri in your ORCID account developer tools. The ORCID redirect URI should be your public OJS URL.
For more information, see: https://support.orcid.org/hc/en-us/articles/360006972513-How-do-redirect-URIs-work
This error is usually caused by entering a production API client and not a Sandbox API client. To fix this, update the settings in your ORCID Plugin to the non-Sandbox option [link to section above].
Search for answers to your technical questions or post questions on the PKP Community Support Forum