
663sr (663sr) asked a question.
Hi, I am tying to install the OPA Gateway on a linux-server and everything went fine. But the server is not getting registered as a gateway in OPA. When checking the logs I am getting the following:
Jul 8 13:26:20 OPA-Gateway sft-gatewayd[9331]: 2024-07-08T13:26:20.937Z*011INFO*011sft-gatewayd service starting*011{"version": "1.82.0"}
Jul 8 13:26:20 OPA-Gateway sft-gatewayd[9331]: 2024-07-08T13:26:20.937Z*011INFO*011Loaded config file*011{"path": "/etc/sft/sft-gatewayd.yaml"}
Jul 8 13:26:20 OPA-Gateway sft-gatewayd[9331]: 2024-07-08T13:26:20.938Z*011INFO*011Attempting platform configuration
Jul 8 13:26:21 OPA-Gateway sft-gatewayd[9331]: 2024-07-08T13:26:21.818Z*011ERROR*011Failed to setup OAuth Private Key Token Source*011{"error": "oauth2: cannot fetch token: 404 Not Found\nResponse: {\n \"type\": \"resource_does_not__exist\",\n \"code\": 404,\n \"message\": \"Client ID not found\"\n}\n", "token_url": "[OUR URL]", "client_id": "[SEEMS LIKE WRONG CLIENTID]"}
Jul 8 13:26:21 OPA-Gateway sft-gatewayd[9331]: 2024-07-08T13:26:21.818Z*011ERROR*011Platform configuration failed*011{"error": "error fetching token source: oauth2: cannot fetch token: 404 Not Found\nResponse: {\n \"type\": \"resource_does_not_exist\",\n \"code\": 404,\n \"message\": \"Client ID not found\"\n}\n"}
Jul 8 13:26:21 OPA-Gateway sft-gatewayd[9331]: 2024-07-08T13:26:21.818Z*011ERROR*011Service entering failed state, shutting down
Any ideas of what this problem could be? 🙂

it seems the client id is not correct
Do you know where the client ID is defined? Could it be changed manually?