Bug #10126

Fetching AtoM 2.3 Levels of Description error (API key required)

Added by Hector Akamine almost 6 years ago. Updated almost 6 years ago.

Status:VerifiedStart date:07/13/2016
Priority:MediumDue date:
Assignee:Sarah Romkey% Done:

0%

Category:Access
Target version:Release 1.5.1
Google Code Legacy ID: Pull Request:https://github.com/artefactual/archivematica/pull/472
Sponsored:No Requires documentation:

Description

dashboard: Administration > AtoM DIP upload > "Levels of Description" button > "Fetch from AtoM" button press -> "Error Retrieving Levels of Description from AtoM" error window
Tested on:
AM: apricotjelly (stable/1.5.x)
AtoM: atom-qa-23x.artefactual.com

History

#1 Updated by Hector Akamine almost 6 years ago

Requests from archivematica are getting 401 from AtoM. AtoM nginx log:

162.243.159.20 - demo@example.com [13/Jul/2016:12:47:26 -0400] "GET /api/taxonomies/34?culture=en HTTP/1.1" 401 5 "-" "python-requests/2.7.0 CPython/2.7.6 Linux/3.13.0-85-generic"

#2 Updated by Hector Akamine almost 6 years ago

AtoM API key reference:
https://www.accesstomemory.org/en/docs/2.3/dev-manual/api/api-intro/

when the API key is included in the request, getting a 200 OK from the same AtoM server:

root@apricotjelly:~# curl -v -H "REST-API-Key: xxxxxxxxx" https://atom-qa
-23x.artefactual.com/api/taxonomies/34?culture=en
...
*        SSL certificate verify ok.
> GET /api/taxonomies/34?culture=en HTTP/1.1
> User-Agent: curl/7.35.0
> Host: atom-qa-23x.artefactual.com
> Accept: */*
> REST-API-Key: xxxxxxxxx
> 
< HTTP/1.1 200 OK
* Server nginx/1.10.0 is not blacklisted
< Server: nginx/1.10.0
< Date: Wed, 13 Jul 2016 16:49:11 GMT
< Content-Type: application/json; charset=utf-8
< Transfer-Encoding: chunked
< Connection: keep-alive
< Set-Cookie: symfony=c1t44v4fu497vt9opqqa91kpq5; path=/; secure; HttpOnly
< Expires: Thu, 19 Nov 1981 08:52:00 GMT
< Cache-Control: no-store, no-cache, must-revalidate
< Pragma: no-cache
< Strict-Transport-Security: max-age=15768000
< 
* Connection #0 to host atom-qa-23x.artefactual.com left intact
[{"name":"Collection"},{"name":"File"},{"name":"Fonds"},{"name":"Item"},{"name":
"Page"},{"name":"Part"},{"name":"Series"},{"name":"Subfonds"},{"name":"Subseries
"}]

#3 Updated by Sarah Romkey almost 6 years ago

  • Category set to Access
  • Assignee set to Nick Wilkinson

Hi Nick- if at all possible it would be great to include this is the 1.5.1 release- could a dev take a look at it?

#4 Updated by Nick Wilkinson almost 6 years ago

  • Assignee changed from Nick Wilkinson to Jesús García Crespo

Hi Jesús, can you please take a look at this when you're back?

#5 Updated by Sarah Romkey almost 6 years ago

  • Target version set to Release 1.5.1

#6 Updated by Jesús García Crespo almost 6 years ago

  • Status changed from New to In progress
  • Pull Request set to https://github.com/artefactual/archivematica/pull/472

#7 Updated by Jesús García Crespo almost 6 years ago

  • Status changed from In progress to QA/Review
  • Assignee changed from Jesús García Crespo to Sarah Romkey

AtoM 2.3 is finally not going to deprecate basic authentication (#10135) so I don't think the work that I did in pull request 472 is required anymore. This means that the issue reported in this ticket should be solved if you are using the latest version of stable/2.3.x or the 2.3.0 tarball (as I speak, not released yet).

#8 Updated by Jesús García Crespo almost 6 years ago

I've updated apricotjelly pointing to atom-qa-23x.artefactual.com again and verified that fetching level of description works again, using stable/2.3.x.

#9 Updated by Sarah Romkey almost 6 years ago

  • Status changed from QA/Review to Verified

I tested this locally and on apricotjelly, is working. Thanks!

Also available in: Atom PDF