By: Maxim Samoussenko user 21 Jan 2019 at 10:55 a.m. CST

2 Responses
Maxim Samoussenko gravatar
**Docker edition.** ``` Request URL: https://mygluuinstallation.net/oxauth/restv1/token Request Method: OPTIONS Status Code: 401 Unauthorized Remote Address: 34.229.34.229:443 Referrer Policy: no-referrer-when-downgrade Request Headers Provisional headers are shown Access-Control-Request-Headers: authorization Access-Control-Request-Method: POST Origin: http://myresourceserver.com:4444 Referer: http://myresourceserver.com:4444/trading User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/71.0.3578.98 Safari/537.36 ``` We have another installation (not docker) on Ubuntu where the same `OPTIONS` request works like a charm: ``` Request URL: https://mygluuinstallation.net/oxauth/restv1/token Request Method: OPTIONS Status Code: 200 OK Remote Address: 10.10.10.10:443 Referrer Policy: no-referrer-when-downgrade Response Headers Access-Control-Allow-Credentials: true Access-Control-Allow-Headers: authorization,origin,x-requested-with,access-control-request-headers,content-type,access-control-request-method,accept Access-Control-Allow-Methods: POST Access-Control-Allow-Origin: http://myresourceserver.com:4444 Access-Control-Max-Age: 1800 Connection: Keep-Alive Content-Length: 0 Date: Mon, 21 Jan 2019 16:46:19 GMT Keep-Alive: timeout=5, max=100 Server: Jetty(9.4.12.v20180830) Strict-Transport-Security: max-age=31536000; includeSubDomains X-Content-Type-Options: nosniff X-Xss-Protection: 1; mode=block Request Headers Provisional headers are shown Access-Control-Request-Headers: authorization Access-Control-Request-Method: POST Origin: http://myresourceserver:4444 Referer: http://myresourceserver:4444/trading User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/71.0.3578.98 Safari/537.36 ``` Original Request: ``` Request URL: https://mygluuinstallation.net/oxauth/restv1/token Request Method: POST Status Code: 200 OK Remote Address: 10.10.87.61:443 Referrer Policy: no-referrer-when-downgrade Response Headers Access-Control-Allow-Credentials: true Access-Control-Allow-Origin: http://myresourceserver.com:4444 Cache-Control: no-store Connection: Keep-Alive Content-Length: 1048 Content-Type: application/json Date: Mon, 21 Jan 2019 16:46:19 GMT Keep-Alive: timeout=5, max=99 Pragma: no-cache Server: Jetty(9.4.12.v20180830) Strict-Transport-Security: max-age=31536000; includeSubDomains X-Content-Type-Options: nosniff X-Xss-Protection: 1; mode=block Request Headers Provisional headers are shown Accept: application/json, text/plain, */* Authorization: bearer XXX Content-Type: application/x-www-form-urlencoded Origin: http://myresourceserver.com:4444 Referer: http://myresourceserver.com:4444/trading User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/71.0.3578.98 Safari/537.36 Form Data client_id: @!2B8A.FE82.4F52.84B6!0001!23E4.EB75!0008!BD2E.B40E.D457.D759 redirect_uri: http://myresourceserver.com:4444/assets/signin.html grant_type: refresh_token refresh_token: 38e567ec-8dab-4a0f-bc38-8cbb31dd9216 ``` Please suggest what could be the reason for such difference?

By Mohib Zico Account Admin 25 Jan 2019 at 7:49 a.m. CST

Mohib Zico gravatar
The organization you selected is wrong. Please use your own organization.

By Bastien Gibrat user 13 Aug 2020 at 6:58 a.m. CDT

Bastien Gibrat gravatar
Hi everyone, i'm facing the same issue, what do you mean about using own organization ? Regards.