Mantenha tudo organizado com as coleções
Salve e categorize o conteúdo com base nas suas preferências.
De acordo com os requisitos da WInnForum, alguns CBSDs exigem que um instalador profissional
certificado (CPI) valide os parâmetros de instalação antes de serem enviados para o SAS.
Figura 1. Fluxo de validação da identidade do CPI
Na API SAS Portal, precisamos validar se um determinado usuário tem uma certificação de CPI válida antes
de chamar o método
SignDevice(). Para isso, usamos o seguinte método de validação em duas etapas:
Um usuário com o papel role_cpi chama o método GenerateSecret(), que retorna um secret.
O usuário assina a chave secreta com a chave privada e usa o método ValidateInstaller() para enviar a versão codificada de volta como um JWT, além do ID do CPI e da chave secreta original. Para mais detalhes sobre a criação de tokens, consulte
Formato JSON Web Token.
Os privilégios do CPI entram em vigor somente depois que um usuário com o papel role_cpi
conclui o fluxo de validação do CPI.
[null,null,["Última atualização 2025-07-25 UTC."],[[["\u003cp\u003eCertain CBSDs require Certified Professional Installer (CPI) validation before installation parameters are sent to the Spectrum Access System (SAS).\u003c/p\u003e\n"],["\u003cp\u003eCPI validation is a two-step process involving secret generation and JWT-based signature validation using the CPI's private key.\u003c/p\u003e\n"],["\u003cp\u003eUsers with the \u003ccode\u003erole_cpi\u003c/code\u003e role must successfully complete the CPI validation flow to gain CPI privileges within the SAS Portal API.\u003c/p\u003e\n"]]],["Certified Professional Installers (CPIs) must validate installation parameters for certain CBSDs. The process involves two steps via the SAS Portal API: First, a user with `role_cpi` obtains a secret using `GenerateSecret()`. Second, they sign the secret with their private key and submit it via `ValidateInstaller()`, along with their CPI ID, using a JWT. This validates the CPI's identity, granting them CPI role privileges, enabling them to use the `SignDevice()` method. The user must be logged in and use HTTPS.\n"],null,["# Validation of CPI identity\n\nAccording to the WInnForum requirements, certain CBSDs require that a Certified Professional\nInstaller (CPI) validates the installation parameters before they are sent to the SAS.\n**Figure 1.** CPI identity validation flow\n\nIn the SAS Portal API, we need to validate that a given user has a valid CPI certification before\nthey can call the\n[`SignDevice()`](/spectrum-access-system/reference/rest/customers.devices/signDevice)\nmethod. We achieve this with the following two-step validation method:\n\n1. A user with the `role_cpi` role calls the [`GenerateSecret()`](/spectrum-access-system/reference/rest/customers.devices/generateSecret) method, which returns a secret.\n2. The user signs the secret with their private key and uses the [`ValidateInstaller()`](/spectrum-access-system/reference/rest/customers.devices/validate) method to send the encoded version back as a [JWT](https://jwt.io/), along with their CPI ID and the original secret. For more details about token creation, see [JSON Web Token format](/spectrum-access-system/guides/json-web-token-format).\n\n| **Note:** For the prior steps, it's assumed that the user is logged in with their Google Account, and the traffic uses HTTPS.\n\nThe CPI role privileges become effective only after a user with the `role_cpi` role\nsuccessfully completes the CPI validation flow."]]
