JSON Web Token format
Stay organized with collections
Save and categorize content based on your preferences.
JSON Web Tokens ( JWTs
) are used
by the SAS Portal API in two ways:
- To aid with CPI identity validation.
- To allow non-CPIs to help install CBSDs that require CPI installation.
During CPI identity validation
, the CPI is asked to create a JWT from a secret generated by the SAS
Portal API. In this case, the CPI uses their private key to create the JWT.
Alternatively, non-CPIs may use the SAS Portal API to create a device configuration from a JWT
created by a CPI. In this case, the JWT contains CBSD registration parameters and the CPI uses their
private key to create the JWT.
The JSON Web Signature (JWS) standard is defined in RFC 7515
, and the SAS Portal API supports the ES256 and RS256 signature algorithms.
Except as otherwise noted, the content of this page is licensed under the Creative Commons Attribution 4.0 License
, and code samples are licensed under the Apache 2.0 License
. For details, see the Google Developers Site Policies
. Java is a registered trademark of Oracle and/or its affiliates.
Last updated 2023-12-05 UTC.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Missing the information I need","missingTheInformationINeed","thumb-down"],["Too complicated / too many steps","tooComplicatedTooManySteps","thumb-down"],["Out of date","outOfDate","thumb-down"],["Samples / code issue","samplesCodeIssue","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2023-12-05 UTC."],[[["\u003cp\u003eThe SAS Portal API utilizes JSON Web Tokens (JWTs) for CPI identity validation and to enable non-CPIs to assist in CBSD installations requiring CPI involvement.\u003c/p\u003e\n"],["\u003cp\u003eDuring CPI identity validation, the CPI generates a JWT using a secret from the SAS Portal API and their private key.\u003c/p\u003e\n"],["\u003cp\u003eNon-CPIs can utilize the SAS Portal API to create device configurations from a CPI-generated JWT containing CBSD registration parameters, signed with the CPI's private key.\u003c/p\u003e\n"],["\u003cp\u003eThe SAS Portal API adheres to the JSON Web Signature (JWS) standard (RFC 7515) and supports ES256 and RS256 signature algorithms.\u003c/p\u003e\n"]]],["JWTs are used within the SAS Portal API for CPI identity validation and to enable non-CPIs to assist with installing CBSDs requiring CPI installation. CPIs create JWTs using their private keys for both purposes. During identity validation, they create a JWT from a SAS Portal API-generated secret. For non-CPI assistance, they create JWTs containing CBSD registration parameters. The API utilizes the JWS standard (RFC 7515) and supports ES256 and RS256 signature algorithms.\n"],null,["# JSON Web Token format\n\nJSON Web Tokens ([JWTs](https://jwt.io)) are used\nby the SAS Portal API in two ways:\n\n- To aid with CPI identity validation.\n- To allow non-CPIs to help install CBSDs that require CPI installation.\n\nDuring [CPI identity validation](https://developers.google.com/spectrum-access-system/guides/validation-of-cpi-identity), the CPI is asked to create a JWT from a secret generated by the SAS\nPortal API. In this case, the CPI uses their private key to create the JWT.\n\nAlternatively, non-CPIs may use the SAS Portal API to create a device configuration from a JWT\ncreated by a CPI. In this case, the JWT contains CBSD registration parameters and the CPI uses their\nprivate key to create the JWT.\n\nThe JSON Web Signature (JWS) standard is defined in [RFC 7515](https://tools.ietf.org/html/rfc7515), and the SAS Portal API supports the ES256 and RS256 signature algorithms."]]
