API Calls in SSH / Access for Infrastructure tutorial out of date

[wuyang-oss]

Existing documentation URL(s)

Example URL(s)
https://developers.cloudflare.com/cloudflare-one/connections/connect-networks/use-cases/ssh/ssh-infrastructure-access/#7-configure-ssh-server

What changes are you suggesting?

In section 7 - 7. Configure SSH server, the API calls listed in order to make a POST/GET for generating a Cloudflare SSH CA are listed as follows

curl "https://api.cloudflare.com/client/v4/accounts/$ACCOUNT_ID/access/gateway_ca"
--request POST
--header "Authorization: Bearer $CLOUDFLARE_API_TOKEN"

curl "https://api.cloudflare.com/client/v4/accounts/$ACCOUNT_ID/access/gateway_ca"
--request GET
--header "Authorization: Bearer $CLOUDFLARE_API_TOKEN"

The correct calls should be (for POST and GET), as listed here https://developers.cloudflare.com/api/resources/zero_trust/subresources/access/subresources/gateway_ca/

curl https://api.cloudflare.com/client/v4/accounts/$ACCOUNT_ID/access/gateway_ca
-X POST
-H "X-Auth-Email: $CLOUDFLARE_EMAIL"
-H "X-Auth-Key: $CLOUDFLARE_API_KEY"

curl https://api.cloudflare.com/client/v4/accounts/$ACCOUNT_ID/access/gateway_ca
-H "X-Auth-Email: $CLOUDFLARE_EMAIL"
-H "X-Auth-Key: $CLOUDFLARE_API_KEY"

Additional information

Additional information
We tested this and the calls listed in the api documentation seems to be the correct ones. Using the call listed in the docs produces a 7003 error {"result":null,"success":false,"errors":[{"code":7003,"message":"Could not route to /client/v4/accounts/$ACCOUNTID/access/gateway_ca, perhaps your object identifier is invalid?"}],"messages":[]}%

[nikitacano]

According to my reproduction, this API end-point supports both global API key (X-Auth-Email) as well as user-owned API tokens and account-owned API tokens (Authorization: Bearer).

Could not route to ..., perhaps your object identifier is invalid? with code 7003 suggests that the issue is with the account tag referenced in the API call. As such, I would start with double checking that the affected API calls had correct account tag in the URL.

@asamborski and @kennyj42 for visibility.

[wuyang-oss]

On second inspection I think you are correct. I just tried to repro again and wasn't given the error so misdiagnosed it.

Reviewed initial error and our customer/user was bracketing their ID which might've led to the 7003

The api documentation lists /accounts/{account_id}/access/gateway_ca as part of the URL that needs to be referenced, so we thought it was necessary to bracket the ID at first and it led to a typo. Sorry for the false alarm.

[ranbel]

BTW the API examples in docs are generated from the API schema (e.g. https://github.com/cloudflare/cloudflare-docs/blob/production/src/content/partials/cloudflare-one/ssh/ssh-proxy-ca.mdx?plain=1#L15), so the API docs and dev docs should always be in sync.