dspace log has nothing about it
tomcat log has this for every authentification attempt
127.0.0.1 - - [03/Dec/2023:10:05:29 +0200] "GET 
/server/api/authn/orcid?code=KNOI5s HTTP/1.1" 302 -


субота, 2 грудня 2023 р. о 20:49:40 UTC+2 Andrew K пише:

> Probably worth metnioning that the return URL in browser is 
> https://my.dspace.website/error?status=401&code=orcid.generic-error
> I.e., that might be another error not related to the account email address.
>
> And I use public API key.
>
>
> субота, 2 грудня 2023 р. о 20:20:00 UTC+2 Andrew K пише:
>
>> Hey guys!
>>
>> I'm having exactly the same problem in 7.6
>>
>> 401unauthorized
>> An error occurred during login via ORCID. Make sure you have shared your 
>> ORCID account email address with DSpace. If the error persists, contact the 
>> administrator
>>
>> My orcid.cfg :
>>
>> #------------------------------------------------------------------#
>> #--------------------ORCID GENERIC CONFIGURATIONS------------------#
>> #------------------------------------------------------------------#
>> # Configuration with which it is established which user can disconnect a 
>> profile from orcid (none, only the admin, only the owner or both).
>> # Allowed values are disabled, only_admin, only_owner or admin_and_owner
>> orcid.disconnection.allowed-users = admin_and_owner
>>
>> #------------------------------------------------------------------#
>> #--------------------ORCID CLIENT CONFIGURATIONS-------------------#
>> #------------------------------------------------------------------#
>> # ORCID API (
>> https://github.com/ORCID/ORCID-Source/tree/master/orcid-api-web#endpoints
>> )
>> #orcid.domain-url= https://sandbox.orcid.org
>> orcid.domain-url= https://orcid.org
>> orcid.authorize-url = ${orcid.domain-url}/oauth/authorize
>> orcid.token-url = ${orcid.domain-url}/oauth/token
>> orcid.api-url = https://api.orcid.org/v3.0
>> orcid.public-url = https://pub.orcid.org/v3.0
>> orcid.redirect-url = ${dspace.server.url}/api/authn/orcid
>>
>> # ORCID Credentials
>> # Your public or member API Credentials, see
>> # https://orcid.org/content/register-client-application-0
>> # 
>> https://info.orcid.org/register-a-client-application-sandbox-member-api/
>> orcid.application-client-id = APP-XXXXXXXXXXXX
>> orcid.application-client-secret = xxxxx-xxxxx-xxx-xxxxxxxxxx
>>
>> # The scopes to be granted by the user during the login on ORCID (see 
>> https://info.orcid.org/faq/what-is-an-oauth-scope-and-which-scopes-does-orcid-support/
>> )
>> orcid.scope = /authenticate
>> #orcid.scope = /read-limited
>> #orcid.scope = /activities/update
>> #orcid.scope = /person/update
>>
>> I also tried setting email visible to Everyone.
>> Interesting that I see in ORCID trusted parties *Access type: Get your 
>> ORCID iD* while other trusted parties might have *Access type: Read your 
>> information with visibility set to Trusted Parties*.
>>
>> I.e. that looks like DSpace doesn't even ask for the email, right?
>>
>> WBR,
>> Andrew
>>
>>

-- 
All messages to this mailing list should adhere to the Code of Conduct: 
https://www.lyrasis.org/about/Pages/Code-of-Conduct.aspx
--- 
You received this message because you are subscribed to the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to dspace-tech+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/dspace-tech/ad35b2a1-8146-47f0-95b8-f38ce33bf0a8n%40googlegroups.com.

Reply via email to