endpoint: /innreach/v2/oauth2/token produces 500

Description

A POST call to
https://edge-<customer>.folio.ebsco.com/innreach/v2/oauth2/token?grant_type=client_credentials&scope=innreach_tp

returns a 500 error.  This error is logged:

2022-09-29T13:13:02.677Z 13:13:02 [] [] [] [] INFO  JwtTokenVerifyFilter JWT token verification isn't needed, since requested URI /innreach/v2/oauth2/token is in the ignore URIs list
2022-09-29T13:13:02.839Z 13:13:02 [] [] [] [] ERROR ceptionHandlerFilter Request failed!
2022-09-29T13:13:02.839Z feign.RetryableException: Connection refused (Connection refused) executing POST http://localhost:9130/authn/login
2022-09-29T13:13:02.839Z     at feign.FeignException.errorExecuting(FeignException.java:268) ~[feign-core-11.7.jar!/:?]

Brooks can provide the entire log.

The POST includes basic authentication using the "localServerKey" and "localServerSecret".

 

CSP Request Details

None

CSP Rejection Details

None

Potential Workaround

None

Attachments

5

Checklist

hide

TestRail: Results

Activity

Show:

Michelle SuranofskySeptember 30, 2022 at 11:57 AM

We ended up adding okapi_url as its own environmental variable (not as part of JAVA_ARG) and that fixed it.  thank you  

Michelle SuranofskySeptember 30, 2022 at 9:48 AM

- thank you.  We did try this and still experienced the problem.  I'll send you the details.

 

Gurleen Kaur1September 30, 2022 at 7:01 AM
Edited

,

Can you please check and confirm the value set for the variable okapi_url in the deployed environment. If it is not set then the default value is used as localhost:9130 and since at this location the server is not up and running the system throws an error connection refused.

2022-09-29T13:13:02.839Z feign.RetryableException: Connection refused (Connection refused) executing POST http://localhost:9130/authn/login

More Info – https://github.com/folio-org/edge-inn-reach#system-properties

CC: , , ,  

Tim AugerSeptember 29, 2022 at 10:24 PM

This is preventing us from moving forward with INN-Reach requesting (and, hence, circulation) validation of the D2IR API. Definitely a P1. we should assume this needs to be backported to Lotus. This and the other record contribution issue has effectively stopped the INN-Reach certification process until resolved. There are a number of logs that should help. 

https://ebscoind-my.sharepoint.com/:u:/g/personal/msuranofsky_corp_epnet_com/EeAcZ2z4zxVPisYnqEsvQXYByLLonO_o2ZEEiYiWgoK3pg 

https://ebscoind-my.sharepoint.com/:u:/g/personal/msuranofsky_corp_epnet_com/EfpoHUYFeGVDnXw9jVGn49IBXaO2AikvG9lCLQOjqBLTtQ 

https://ebscoind-my.sharepoint.com/:u:/g/personal/msuranofsky_corp_epnet_com/EZA20bTPpAROlLdGk40objABjcYXCMIBX0LpXrXdNUpfrA 

https://ebscoind-my.sharepoint.com/:u:/g/personal/msuranofsky_corp_epnet_com/EW78T2w0QyFBnrE42ruyXuIBRAUlmfHHffRFUG0V7Ntiew 

 

Done

Details

Assignee

Reporter

Priority

Development Team

Volaris

RCA Group

TBD

TestRail: Cases

Open TestRail: Cases

TestRail: Runs

Open TestRail: Runs

Created September 29, 2022 at 10:13 PM
Updated September 30, 2022 at 11:58 AM
Resolved September 30, 2022 at 11:58 AM
TestRail: Cases
TestRail: Runs