Reported by both Califa and Amigos.

When Paula attempts to push Salinas Public Library to production, she sees the error:

504 response from integration server: '\r\n\r\n\r\n
504 Gateway Time-out

Risa cannot find Salinas or any of the more recent Califa testing libraries in the registry.

Amigos has a thorough testing of the error:

"We have encountered errors attempting to register two additional libraries with the Library Registry in testing mode. We aren’t certain whether the failure involves only an issue on our side, an issue on the Library Registry side, or a combination of both—but if we are reading errors and logs correctly, it appears to be a bug in code on one side or the other. We are hoping someone at NYPL can review Library Registry service logs and perhaps help us resolve the issue.

The two libraries involved, each one on a separate Circulation Manager (CM), are:

• Allan Shivers (CM version 3.1.3; https://simplye-tsl1.amigos.org/admin/txallan)
• Arizona State Library (originally CM version 3.1.2, now v3.1.3; https://simplye.amigos.org/admin/)

Each attempt to register these encountered the same error(s):

• The first attempt to register failed after a wait and returned a 504 error in the Admin interface:
• 

• Any subsequent attempts to register return a 500 error in the Admin interface (502 when viewing the Network panel of Developer Tools):
• 

I suspect the “integration server” means the Library Registry (remote) server in this case, but I’m not certain. Given the logs in the attached “azstate-registration-process” Excel file, it does look like the testing registration request is posted to the CM and the CM communicates with the Registry. There are both a subsequent GET of the library’s authentication document and a GET of the initial group feed for the library (successfully returned) as is usual from the Registry.

Also, later in the logs (shortly after the registration process) I see a series of a single repeated error. The error message: Short Client Token configuration for Arizona State Library, Archives and Public Records is present but not working. This may be cause for concern. Original error: Short Client Token configuration is incomplete. vendor_id (NYPL), username (https://azlibrary.gov/), password (None) and Library website_url (None) must all be defined. It seems like this may be referencing the data seen on the Registry server; the library website is definitely configured correctly in the CM (see the attached azstate configuration settings file). Interestingly, its value is shown in the error statement as the username value. The registration fails, so a username and password from the Registry is never supplied back to the CM to be saved. Could the order of the fields have changed in the code on one side or the other?"

Acceptance criteria:

When a hosting service uses their own circulation manager to promote a library to the library registry for inclusion in SimplyE, they should see a response that their submission to the registry has been successful.

Assigning to Leonard to determine cause with Nick.