Delivered-To: emorgan@nd.edu Received: by 2002:a17:906:1982:b0:993:f2d4:f8a with SMTP id g2csp7595612ejd; Thu, 20 Jul 2023 05:33:41 -0700 (PDT) X-Google-Smtp-Source: APBJJlFbfZdA+AhCBRZVJ0HAi7i8OwX1pIu8EhAQsYAMphZZIXl+BuY2ahxA+M0/8tr+S3oVeu3F X-Received: by 2002:a05:6214:32f:b0:62b:6999:ab7b with SMTP id j15-20020a056214032f00b0062b6999ab7bmr16767388qvu.16.1689856421548; Thu, 20 Jul 2023 05:33:41 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1689856421; cv=none; d=google.com; s=arc-20160816; b=pN1jyD7jZb3Ic9Az6IbM27dV4GekJE66AvaZ14ch5p8Kde5zPPfOLbxatHDLYkdhwh A0P1cHcS6aluakIJJfRoGYY0miHw/uCvDPPxGQfztBus/c0Wsbsi1bYhR65Ds4Zg4MYC oXtFgjMPjHnsysRP66k8+w8xeEjgJphtJE/DYetb4vN3DdQUp0fojs06ZirPr9HXDlcs Def1xhwVBptpw4Lm5egG9D/kqEnrkh8VUO2AH5ejO5lxOsKXhdAWJE6i2ke3ELCwj56C dzX3hwOzNXBZDoBj+5KcPLWdfIVmTUlpVHJCzjzKsL2U9S5Vypf5JKqYuATZ1z0Pz1ca s7gA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=dkim-signature:auto-submitted:content-transfer-encoding :mime-version:subject:references:in-reply-to:message-id:to:reply-to :from:date; bh=Y2Bvi0DmJGWFIKRvP9SseTtGgU/cHAeHSrazygxExb8=; fh=3fsjWVaXf/UAcbNry0wMlcv/oR5iTSAx6CApyH0CAis=; b=Veox7UGp7PdaY/LO3VnYTMPujEd+P8MOgTnVXZug6UfeEy4GsNYCIcOTIAnxwBKzKE a0yu3ydzyaCVJUh7kDVEKMsbSqgDSI/QkxqCj7+5CUiyGmRXu20BXCFDRGsEiZqz4jUA JeBL/Y7UYxZUw9JVF0SK5p2mddTBSI6avU63NqyuahEP3YWb356awkeo7ijJ07ZRr6fc d/HLknZZABn5U4NeA6azsfsQGEVgOHR9fnt14r5f5Sw6jEJsbYr9PvuDyiUUuBQWqdZ2 WdnJCAyJPrd0MNrHHp7nIO2sgqdHja5MsSk7bJoUwRRwp3yXwt5gYTkgWHrV1xmZwuLG M7Yw== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@orcid.org header.s=zendesk1 header.b=PZS7vCPk; spf=pass (google.com: domain of support@orcid.org designates 192.161.149.31 as permitted sender) smtp.mailfrom=support@orcid.org; dmarc=pass (p=QUARANTINE sp=QUARANTINE dis=NONE) header.from=orcid.org Return-Path: Received: from outbyoip1.pod23.use1.zdsys.com (outbyoip1.pod23.use1.zdsys.com. [192.161.149.31]) by mx.google.com with ESMTPS id f8-20020ad45408000000b0062dea52a69asi300308qvt.446.2023.07.20.05.33.41 for (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Thu, 20 Jul 2023 05:33:41 -0700 (PDT) Received-SPF: pass (google.com: domain of support@orcid.org designates 192.161.149.31 as permitted sender) client-ip=192.161.149.31; Authentication-Results: mx.google.com; dkim=pass header.i=@orcid.org header.s=zendesk1 header.b=PZS7vCPk; spf=pass (google.com: domain of support@orcid.org designates 192.161.149.31 as permitted sender) smtp.mailfrom=support@orcid.org; dmarc=pass (p=QUARANTINE sp=QUARANTINE dis=NONE) header.from=orcid.org Received: from zendesk.com (unknown [10.221.29.104]) by outbyoip1.pod23.use1.zdsys.com (Postfix) with ESMTP id 4R6Bts1LwQz14K2k for ; Thu, 20 Jul 2023 12:33:41 +0000 (UTC) Date: Thu, 20 Jul 2023 12:33:41 +0000 From: "Jordan Holt (Support)" Reply-To: Support To: emorgan Message-ID: In-Reply-To: <20230718203848.04acc275a2420661@info.orcid.org> References: <20230718203848.04acc275a2420661@info.orcid.org> <3D812405-5A6A-4479-AE81-BAA5E1A3FA0A@nd.edu> <2C7CCEBC-0375-46B6-A454-0165E64D9B8E@nd.edu> Subject: [ORCID Support] Re: Register a client application: Sandbox Member API navari family center for digital scholarship, hesburgh libraries, university of notre dame Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_64b929a517ed1_3c39f83907b4"; charset=utf-8 Content-Transfer-Encoding: 7bit X-Delivery-Context: event-id-16162443103895 Auto-Submitted: auto-generated X-Auto-Response-Suppress: All X-Mailer: Zendesk Mailer X-Zendesk-From-Account-Id: 7a74351 X-Zendesk-Email-Id: 01H5SMNATEAQ8MHC3HWCRYJ69W DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=orcid.org; q=dns/txt; s=zendesk1; t=1689856421; bh=Y2Bvi0DmJGWFIKRvP9SseTtGgU/cHAeHSrazygxExb8=; h=date:from:reply-to:to:message-id:in-reply-to:references:subject:mime-version:content-type:content-transfer-encoding; b=PZS7vCPkCPGc8PJwTTylngBBaT8Vz46QN3Ub4ApAFbaGhNixfWfgbkdvKvXyCovsDmOKnKPE3Xgp6FgZQPSJZS9rhOL63EJXjc7z29QB1fZJp4kob0I0HYVUgHY/hWo/7Sf3LupMfpfH9AxUX/BB1QGOHONBjKIAidxwv3TKraamo/27PxywIMFC87fMQdu+/v8dM0tDQevGLhJ2BLm2uiqSqYIPI4ASYcRwFw9bm5/A425S/4E8g7OY77G6iVjovYGmD4UgpxuHBLRZ0QRxSQBy9lB48TnPpuQVsQgXDixFlirIJw3ZTWw9tRKcHRy/ZNwuTIq6L5VGhQ4r4De7lA== ----==_mimepart_64b929a517ed1_3c39f83907b4 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable ##- Please type your reply above this line -## Your request (#495806) has been updated. To add additional comments, please= reply to this email or click the link below: https://www.google.com/url?q=3Dhttps://support.orcid.org/hc/requests/495806= &source=3Dgmail-imap&ust=3D1690461223000000&usg=3DAOvVaw39iNJcMwwM-28Vl_lC4= DmQ ---------------------------------------------- Jordan Holt, Jul 20, 2023, 08:33 EDT Hi Eric, Thanks for following up. As requested I've registered the two redirects URIs to your client applicat= ion. The redirect: https://www.google.com/url?q=3Dhttps://distantreader.org= /login/callback&source=3Dgmail-imap&ust=3D1690461223000000&usg=3DAOvVaw3NDg= PnC8Awox-EWoJb3ssk which was included in your application, was registered h= owever it was mistakenly omitted in my reply. > In my application I can now configure and send a user to ORCID for authen= tication, but the call back (redirect) URL points to a Google debugging too= l, and I need it to point to my application. The redirect location is defined in the authorization link which you build = by specifying your API credentials=E2=80=99 client ID and associated landin= g page (redirect URI). The Google OAuth playground allows you to exchange t= he authorization code for an access token - which cannot be done client sid= e - so it serves as a convenient tool when testing. However, you can certai= nly change the redirect as needed when testing by specifying the desired re= direct in the `redirect_uri` parameter of the authorization link: https://www.google.com/url?q=3Dhttps://sandbox.orcid.org/oauth/authoriz= e?client_id%3D%5BAPP-****************%5D%26response_type%3Dcode%26scope%3D/= read-limited%2520/activities/update%2520/person/update%26redirect_uri%3Dhtt= p://localhost:8080/login_callback&source=3Dgmail-imap&ust=3D169046122300000= 0&usg=3DAOvVaw3QCh3VNZg_6kvkfibjjpmV I've included a few resources you may find helpful as you begin testing the= API in our sandbox. The Hands-on tutorial provides a great introduction to= the API: - How do redirect URIs work? - Hands on with the ORCID API - Integration and API FAQ Please let me know if you have any questions. Best, Jordan Member Support Technical Specialist https://www.google.com/url?q=3Dhttps://orcid.org/0000-0002-5391-5437&source= =3Dgmail-imap&ust=3D1690461223000000&usg=3DAOvVaw09EXXmiawYgUvpNYoeBKqX Please add multiple emails to your ORCID record - to ensure you don't lose = access if you change institutions, and avoid setting up a duplicate record. ---------------------------------------------- emorgan, Jul 20, 2023, 08:05 EDT Again, thank you for the credentials, but now I need a call back URL that f= unctions in my application. In my application I can now configure and send a user to ORCID for authenti= cation, but the call back (redirect) URL points to a Google debugging tool,= and I need it to point to my application. How can you (or I) include one or both of the following URLs as possible ca= ll backs: * https://www.google.com/url?q=3Dhttp://localhost:8080/login_callback&sour= ce=3Dgmail-imap&ust=3D1690461223000000&usg=3DAOvVaw2i8lZX5C4mwsKHl-M4j4kM * https://www.google.com/url?q=3Dhttps://distantreader.org/stacks/indexes/= login_callback&source=3Dgmail-imap&ust=3D1690461223000000&usg=3DAOvVaw2_RP8= WQIXL92_wg5vq0Sbx -- Eric Morgan University of Notre Dame ---------------------------------------------- emorgan, Jul 19, 2023, 16:32 EDT Thank you for the prompt reply, but the content is a bit of surprise to me.= =20 The ID and secret make sense. Thank you. I don't understand the redirect URL. I thought I was expected to get a redi= rect URL that pointed to my domain. Did I miss something in the documentati= on? All the services there are Google-based. If I want to learn how to auth= enticate against ORCID, then do you want me to practice the Oauth thing lis= ted on https://www.google.com/url?q=3Dhttps://developers.google.com/oauthpl= ayground&source=3Dgmail-imap&ust=3D1690461223000000&usg=3DAOvVaw1_oPXMplmu1= GzRlL8PqOXZ? -- Eric Morgan ---------------------------------------------- Jordan Holt, Jul 19, 2023, 15:46 EDT Hello Eric, Thank you for your interest in the ORCID Registry. Your client credentials for the ORCID sandbox are as follows: **Client ID:** APP-2G0DPHEC44CY775V **Client secret:** 70690c3a-dcff-407b-b06f-0770b1be5055 Redirect URIs: https://www.google.com/url?q=3Dhttps://developers.google.com/oauthplaygroun= d&source=3Dgmail-imap&ust=3D1690461223000000&usg=3DAOvVaw1_oPXMplmu1GzRlL8P= qOXZ **Creating a testing user account:** In order to test the ORCiD API and API calls, such as a reading and adding = information to an ORCID record in the sandbox testing server, you will also= need to create a test ORCID record in the sandbox. This can be done throug= h the user interface, much like on the production ORCID Registry. Go to htt= ps://www.google.com/url?q=3Dhttps://sandbox.orcid.org/register&source=3Dgma= il-imap&ust=3D1690461223000000&usg=3DAOvVaw3Dm-yqLlEBUNw94T_j-3u2 and regis= ter for an account. **Receiving the verification email to validate the testing user account:** Please note that the sandbox is configured to send emails only to @mailinat= or.com addresses. Mailinator.com is a free inbox testing service; for more = information, see: Mailinator. In order to receive emails from the sandbox, please make the primary addres= s on your sandbox test account a @mailinator.com address. Process for a Mailinator email address. - Go to https://www.google.com/url?q=3Dhttps://mailinator.com&source=3Dgmai= l-imap&ust=3D1690461223000000&usg=3DAOvVaw32hCxw833WUCNbpi2_xICs - At the top of the screen, look for a text box - Enter the user name you would like to use (ex. orcid), click Go, this wil= l become your Mailinator email address, ex. orcid@mailinator.com **Populating a testing user account:** The sandbox testing server is a copy of the ORCID Registry software, and on= ly contains testing data. As such, please note the following: - You must add test data to the test user account - ORCID iDs registered in our production environment are not accessible in = the sandbox For more information on how to get started with the ORCID API, including se= tting up a test user account and data, please see the following tutorial: H= ands on with the ORCID API **Getting started with your integration:** Please ensure that you review our member support center documentation befor= e you start planning your integration. You can also find example calls and XML files in our GitHub repository. - Members Support Center - GitHub technical documentation - Integration best practices We also strongly recommend that you join the ORCID API listserv at ORCID AP= I Users Group, where you can connect with other developers and API users, a= s well as with the ORCID technical team. It is also the community support l= ocation for organizations that are not yet ORCID members. As a member of the ORCID US Community, you can get technical support for yo= ur integration from the consortia lead organization, Lyrasis. So if you hav= e any questions or problems with your API integration, please contact them = at orcidus@lyrasis.org. We work closely with them, and they will escalate a= ny complex questions or issues you may have to us so that we can help you d= irectly if needed. If you need to update your API credentials in future, please contact us wit= h the requested changes. For other questions or support issues relating to your ORCID integration, p= lease contact your consortia lead organization in the first instance, as no= ted above. Best regards, Jordan Member Support Technical Specialist https://www.google.com/url?q=3Dhttps://orcid.org/0000-0002-5391-5437&source= =3Dgmail-imap&ust=3D1690461223000000&usg=3DAOvVaw09EXXmiawYgUvpNYoeBKqX Please add multiple emails to your ORCID record - to ensure you don't lose = access if you change institutions, and avoid setting up a duplicate record. ---------------------------------------------- emorgan, Jul 18, 2023, 16:38 EDT Update existing credentials?: No Email address: emorgan@nd.edu Contact Name: eric lease morgan Name of your organization: navari family center for digital scholarship, he= sburgh libraries, university of notre dame What type of credentials would you like?: Basic: Trusted-Party (Read from/W= rite to records) Name of your client application: distantreader Short description of your client application: This client application is us= ed to authenticate people against the Distant Reader. URL of the home page of your application: https://www.google.com/url?q=3Dht= tps://distantreader.org/&source=3Dgmail-imap&ust=3D1690461223000000&usg=3DA= OvVaw10_SR6rfLSWWmq6ocnanrZ Redirect URI 1: https://www.google.com/url?q=3Dhttps://distantreader.org/st= acks/indexes/login/callback&source=3Dgmail-imap&ust=3D1690461223000000&usg= =3DAOvVaw0ZsUS9reyZwhTbeediDRmD Redirect URI 2: https://www.google.com/url?q=3Dhttps://distantreader.org/lo= gin/callback&source=3Dgmail-imap&ust=3D1690461223000000&usg=3DAOvVaw3NDgPnC= 8Awox-EWoJb3ssk ![](https://www.google.com/url?q=3Dhttp://email.info.orcid.org/o/eJw8yDEWw= iAMANDTlJEXQhLCwGEiDcoifaj3d-v6z6bGLhK8JdFaEhbU8GrsRpJVMteRh_qDzZ27JlPgCj3M= hoAZSlKErKQRyHrHwoaEIJIOgvkeK67d5xnXfobdPr_rWvt7ENz6DwAA__-OiSRc&source=3Dg= mail-imap&ust=3D1690461223000000&usg=3DAOvVaw02N-BBLfBHrp9zS-5SGaiD) Attachment(s): ninja-forms-submission.csv - https://www.google.com/url?q=3Dhttps://support= .orcid.org/attachments/token/ShJMyWaGdDI6WDjt3UybRkG7g/?name%3Dninja-forms-= submission.csv&source=3Dgmail-imap&ust=3D1690461223000000&usg=3DAOvVaw0CgwD= LVTK83qY-oR4_fsR9 -------------------------------- This email is a service from ORCID Support. [PYRM29-NPNL1] ----==_mimepart_64b929a517ed1_3c39f83907b4 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
##- Please type your reply above this li= ne -##

Your request (#495806) has been updated. To add additional comments, please rep= ly to this email or click the link below:
https://support.orcid.org/hc/requests/495806

=
3D""

<= strong>Jordan Holt (ORCID Support) =

Jul 20, 2023, 08:33 E= DT

Hi Eric,=C2=A0
=C2=A0
Thanks for following up.=C2=A0
=C2=A0
= As requested I've registered the two redirects URIs to your client appl= ication. The redirect: = https://distantreader.org/login/callback which was included in your app= lication, was registered however it was mistakenly omitted in my reply.=C2= =A0
=C2=A0

In my application I can now = configure and send a user to ORCID for authentication, but the call back (r= edirect) URL points to a Google debugging tool, and I need it to point to m= y application.

=C2=A0
The redirect location is defined i= n the authorization link which you build by specifying your API credentials= =E2=80=99 client ID and associated landing page (redirect URI). The Google = OAuth playground allows you to exchange the authorization code for an acces= s token - which cannot be done client side - so it serves as a convenient t= ool when testing. However, you can certainly change the redirect as needed = when testing by specifying the desired redirect in the redirect_uri parameter of the aut= horization link:
=C2=A0
https://sandbox.o=
rcid.org/oauth/authorize?client_id=3D[APP-****************]&response_ty=
pe=3Dcode&scope=3D/read-limited%20/activities/update%20/person/update&a=
mp;redirect_uri=3Dhttp://localhost:8080/login_callback
=C2=A0=C2=A0
I've included a few resources you may find helpful as you b= egin testing the API in our sandbox. The Hands-on tutorial provides a great= introduction to the API:
=C2=A0
=C2=A0
Please let me know if you have any questions.=C2=A0
=C2= =A0
Best,=C2=A0

Jordan

Member Support Tec= hnical Specialist

https://orcid.= org/0000-0002-5391-5437

Please add multiple emails to your ORCID rec= ord - to ensure you don't lose access if you change institutions, and a= void setting up a duplicate record.

=

= =
3D""

e= morgan

= Jul 20, 2023, 08:05 EDT

=

Again, thank you for the credentials, but= now I need a call back URL that functions in my application.

In my appl= ication I can now configure and send a user to ORCID for authentication, bu= t the call back (redirect) URL points to a Google debugging tool, and I nee= d it to point to my application.

How can you (or I) include one or both = of the following URLs as possible call backs:

* http://localhost:8080/login_call= back
* https://distantreader.org/stacks/indexes/login_cal= lback

--
Eric Morgan
University of Notre Dame

=

= = =
3D""

emo= rgan

= Jul 19, 2023, 16:32 EDT

=

Thank you for the prompt reply, but the con= tent is a bit of surprise to me.

The ID and secret make sense. Thank yo= u.

I don't understand the redirect URL. I thought I was expected to = get a redirect URL that pointed to my domain. Did I miss something in the d= ocumentation? All the services there are Google-based. If I want to learn h= ow to authenticate against ORCID, then do you want me to practice the Oauth= thing listed on https://developers.google.com/oauthplayground?

--Eric Morgan

=
3D""

Jordan Holt (ORCID Support) =

Jul 19, 2023, 15:46 ED= T

= sandbox are as follows:
=C2=A0
Client ID:
APP= -2G0DPHEC44CY775V
=C2=A0
Client secret:
70690c3a-= dcff-407b-b06f-0770b1be5055
=C2=A0
Redirect URIs:
https://developers.google.com/oaut= hplayground
=C2=A0
Creating a testing user account:
In order to test the ORCiD API and API calls, such as a reading and = adding information to an ORCID record in the sandbox testing server, you wi= ll also need to create a test ORCID record in the sandbox. This can be done= through the user interface, much like on the production ORCID Registry. Go= to https://sandbox.orcid.org= /register and register for an account.
=C2=A0
Receiving t= he verification email to validate the testing user account:
Ple= ase note that the sandbox is configured to send emails only to @mailinator.= com addresses. Mailinator.com is a free inbox testing service; for more inf= ormation, see: Mailinator.=C2=A0
= =C2=A0
In order to receive emails from the sandbox, please make the prim= ary address on your sandbox test account a @mailinator.com address.
=C2=A0
Process for a Mailinator email a= ddress.
  • Go to https://mailinator.com
  • At the top of the screen, = look for a text box
  • Ent= er the user name you would like to use (ex. orcid), click Go, this will bec= ome your Mailinator email address, ex. orcid@mailinator.com
=C2=A0
= Populating a testing user account:
The sandbox testing server i= s a copy of the ORCID Registry software, and only contains testing data.=C2=A0
As such, please note the following:
  • You must add test data to the te= st user account
  • ORCID i= Ds registered in our production environment are not accessible in the sandb= ox
=C2=A0
For more information on how to get started with the O= RCID API, including setting up a test user account and data, please see the= following tutorial: Hands on with the ORCID API
=C2=A0
Getting start= ed with your integration:
Please ensure that you review our mem= ber support center documentation before you start planning your integration= .
=C2=A0
You can also find example calls and XML files in our GitHub = repository.
=C2=A0
=C2=A0
We also strongly recommend= that you join the ORCID API listserv at ORCID API Users Group, where you can connect w= ith other developers and API users, as well as with the ORCID technical tea= m. It is also the community support location for organizations that are not= yet ORCID members.
=C2=A0
As a member of the ORCID US Community, you= can get technical support for your integration from the consortia lead org= anization, Lyrasis. So if you have any questions or problems with your API = integration, please contact them at orcidus@lyrasis.org. We work closely with them, and = they will escalate any complex questions or issues you may have to us so th= at we can help you directly if needed.
=C2=A0
If you need to update y= our API credentials in future, please contact us with the requested changes= .
For other questions or support issues relating to your ORCID integrati= on, please contact your consortia lead organization in the first instance, = as noted above.
=C2=A0
Best regards,=C2=A0

Member Support Technical Specialist

https://orcid.org/0000-0002-5391-5437

Please add mul= tiple emails to your ORCID record - to ensure you don't lose access if = you change institutions, and avoid setting up a duplicate record.

=

=
3D""

= emorgan

=

Jul 18, 2023, 16:38 EDT =

<= td>eric lease morganRedirect URI 2:3D""

Attachment(s)
= ninja-forms-submission.csv

=
Update exist= ing credentials?:No
Email address:= emorgan@nd.edu
Contact Name:
Name of your organizat= ion:navari family center for digital scholarship, hesburgh librari= es, university of notre dame
What type of c= redentials would you like?:Basic: Trusted-Party (Read from/Write t= o records)
Name of your client application:= distantreader
Short description of= your client application:This client application is used to authen= ticate people against the Distant Reader.
U= RL of the home page of your application:https://distantreader.org/
Redirect= URI 1:h= ttps://distantreader.org/stacks/indexes/login/callback
https://distantreader.org/login/callback
This email is a service from ORCID Support. Delivered by Zendesk
[PYRM29-NPNL1]
----==_mimepart_64b929a517ed1_3c39f83907b4--