Supported Identity Service verification after December 15 API-key retirement

We are migrating following your November 11 notice. Two read-only Identity Service operations remain unresolved:

- POST api.identity.nrfcloud.com/.../verify-jwt authenticates nRF9151 modem identity JWTs for our own CoAP/DTLS receiver.

- POST api.identity.nrfcloud.com/.../verify-attestation verifies a nonce-bearing device proof before our customer gateway-assignment workflow.

Both currently use a legacy API key. Current verification documentation still describes that authentication, while the live REST transition guide does not list replacement Identity endpoints. Please confirm:

1. Will these endpoints and legacy-key authentication remain available after December 15, 2026? If so, until when?

2. What supported endpoints and OAT permissions replace them? Can an OAT authenticate the existing Identity host, and is organisation/project scoping required?

3. Do token formats and verification response fields remain unchanged, including the verified device UUID and attestation nonce?

We need verification without claiming, onboarding, transferring or otherwise modifying a device. The new device-creation endpoint performs additional operations, so it does not replace these standalone proof checks. Please provide the supported API contract or migration guidance for both uses.

Parents
  • Hi Doug,

    We will update the API documentation and transition guide to include these verify API calls. I will let you know once these are online.

    We would like all our customers to move to OAT based authentication as soon as possible.

    OAT brings additional security benefits and we are in a process of deprecating all legacy API key based API calls.

    Having said that, we will make sure that you have enough time to migrate your existing code to be OAT-based.

    Best regards,

    Markku Lehto

Reply
  • Hi Doug,

    We will update the API documentation and transition guide to include these verify API calls. I will let you know once these are online.

    We would like all our customers to move to OAT based authentication as soon as possible.

    OAT brings additional security benefits and we are in a process of deprecating all legacy API key based API calls.

    Having said that, we will make sure that you have enough time to migrate your existing code to be OAT-based.

    Best regards,

    Markku Lehto

Children
No Data
Related