Hello @jeff.kenyon
Thank you for your participation in the forum. Is the reply below satisfactory in resolving your query?
If yes, please click the 'Accept' text next to the reply. This will guide all community members who have a similar question. Otherwise please post again offering further insight into your question.
Thanks,
AHS
Update from Jeff.
The problem is now resolved. It seems to be an issue from the HTTPS proxy on the windows server.
We change it from
HTTPS_PROXY=https://webproxy.XXXX.services:xxx
To:
HTTPS_PROXY=http://webproxy.XXXXXX.services:xxx
Now the test RDP script now connects, and the curl call works:
* Uses proxy env variable https_proxy == 'http://webproxy.XXXX.services:XXX'
* Trying XXXXXX:XXX...
* Connected to webproxy.pln.corp.services (xx.xx.xx.xx) port xx (#0)
* allocate connect buffer!
* Establish HTTP proxy tunnel to api.edp.thomsonreuters.com:443
> CONNECT api.edp.thomsonreuters.com:443 HTTP/1.1
> Host: api.edp.thomsonreuters.com:443
> User-Agent: curl/7.73.0
> Proxy-Connection: Keep-Alive
>
< HTTP/1.0 200 Connection established
<
* Proxy replied 200 to CONNECT request
* CONNECT phase completed!
* ALPN, offering h2
* ALPN, offering http/1.1
* successfully set certificate verify locations:
* CAfile: D:\curl-7.73.0-win64-mingw\bin\curl-ca-bundle.crt
* CApath: none
* TLSv1.3 (OUT), TLS handshake, Client hello (1):
* CONNECT phase completed!
* CONNECT phase completed!
* TLSv1.3 (IN), TLS handshake, Server hello (2):
* TLSv1.2 (IN), TLS handshake, Certificate (11):
* TLSv1.2 (IN), TLS handshake, Server key exchange (12):
* TLSv1.2 (IN), TLS handshake, Server finished (14):
* TLSv1.2 (OUT), TLS handshake, Client key exchange (16):
* TLSv1.2 (OUT), TLS change cipher, Change cipher spec (1):
* TLSv1.2 (OUT), TLS handshake, Finished (20):
* TLSv1.2 (IN), TLS handshake, Finished (20):
* SSL connection using TLSv1.2 / ECDHE-RSA-AES128-GCM-SHA256
* ALPN, server accepted to use h2
* Server certificate:
* subject: C=US; postalCode=10036; ST=NY; L=New York; street=3 Times Square; O=
Thomson Reuters Inc; OU=EDS Request Response; CN=api.refinitiv.com
* start date: Jul 29 00:00:00 2019 GMT
* expire date: Jul 28 23:59:59 2021 GMT
* subjectAltName: host "api.edp.thomsonreuters.com" matched cert's "api.edp.tho
* issuer: C=GB; ST=Greater Manchester; L=Salford; O=COMODO CA Limited; CN=COMOD
O RSA Organization Validation Secure Server CA
* SSL certificate verify ok.
* Using HTTP2, server supports multi-use
* Connection state changed (HTTP/2 confirmed)
* Copying HTTP/2 data in stream buffer to connection buffer after upgrade: len=0
* Using Stream ID: 1 (easy handle 0x3a68c98af0)
> POST /auth/oauth2/v1/token HTTP/2
> Host: api.edp.thomsonreuters.com
> user-agent: curl/7.73.0
> accept: application/json
> content-type: application/x-www-form-urlencoded
> content-length: 105
>
* Connection state changed (MAX_CONCURRENT_STREAMS == 128)!
* We are completely uploaded and fine
< HTTP/2 400
< date: Tue, 17 Nov 2020 17:55:11 GMT
< content-type: application/json
< content-length: 204
< access-control-allow-origin: *
< server: edsgw
< x-amzn-trace-id: Root=XXXXXXXXXXXXXXXXXXXXXXXXXX
< x-served-by: region=us-east-1; cid=
< x-tr-requestid: XXXXXXXXXXXXXXXXXXXXXXXXXX
<
{"error":{"id":"XXXXXXXXXXXXXXXXXXXXXXXXX","code":"400","message":"Va
lidation error","status":"Bad Request","errors":[{"key":"grant_type","reason":"M
issing required parameter 'grant_type'"}]}}
* Connection #0 to host webproxy.XXXXXXXXXXXXXXXXXXXX.services left intact
A bit confusing, I understand that you can run the same app from your laptop, but the problem found when running the python codes on the windows server. Is this correct?
curl --data-urlencode "username=<user>&password=<password>&grant_type=password≻ope=trapi" -X POST -H "Accept: application/json" -H "Content-Type: application/x-www-form-urlencoded" -v https://api.edp.thomsonreuters.com/auth/oauth2/v1/token