Exchange a CSR for a signed certificate
POST/v1/claim/verify
Exchanges a device-generated CSR for a certificate signed by the deployment's claiming CA, and binds it to the node's IoT Thing.
The CSR contributes only its public key; its subject is discarded and
the certificate Common Name is rebuilt from the reservation, so the
caller cannot influence the identity it receives. capabilities must
be re-supplied on a re-claim, since they are applied to the new
certificate; tags are never accepted from the request.
Available only on deployments with assisted claiming enabled; check for
the rmng-claim-core AssistedClaiming output in the published outputs
(absent when the claim group is not deployed). When it is not deployed
these routes do not exist, so a request is rejected at the API Gateway
rather than reaching the service. The 404 below is the service's own
response when claiming is inactive.
Request
Responses
- 201
- 400
- 401
- 403
- 404
- 500
Certificate issued and bound to the node
Bad request
Unauthorized - Invalid or missing authentication
No reservation for this caller and device
Not found - the resource does not exist, or the feature is not enabled on this deployment. For username lookups the message is deliberately generic — it does not reveal whether an address is registered.
Internal server error