Do I need to provide the same identifying information in the NRL v3 JWTs as I used to in the NRL v2.8 JWTs?
No - NRL v3.0 doesn’t require the same identifying information in the JWT as was required in NRL v2.8.
When creating pointers using NRL v.3.0., you will need to provide your Accredited System Identifier (ASID) in the ‘context.related’ section of the pointer body. Your ASID is not required in the JWT when interacting with the NRL v3 APIs. However, it is required when attempting to retrieve the actual document via Spine Secure Proxy (SSP) - Specifically, this is the ASID that is used by consuming applications when they try and retrieve documents. It allows SSP to verify the endpoint providing the document matches the registration.
For more information on differences between the legacy and replacement NRL services, please see our migration guidance.