Nokia Corp Authentication

generated: '2026-11-04'
method: searched
source:
- openapi/nokia-corp-network-as-code-openapi.yml
- https://raw.githubusercontent.com/nokia-steward/network-as-code-sdks/main/openapi/Single-NaC-API-OAS.yaml
- https://networkascode.nokia.io/docs/getting-started
- https://networkascode.nokia.io/docs/general-concepts/consent-identity-mgmt
- https://networkascode.nokia.io/docs/general-concepts/network-as-code-client
docs: https://networkascode.nokia.io/docs/general-concepts/consent-identity-mgmt
name: Nokia Network as Code authentication
summary:
  types:
  - apiKey
  - openIdConnect
  api_key_in:
  - header
  note: 'Developer authentication is an application API key sent through the RapidAPI gateway; end-user
    consent for device-specific APIs is handled by the NaC Authorization Server (OIDC: CIBA transparently,
    or the Authorization Code flow where a user must act). The consolidated provider contract declares
    an openIdConnect scheme with a placeholder discovery URL (https://example.com/.well-known/openid-configuration).'
schemes:
- name: ApiKeyAuth
  type: apiKey
  in: header
  parameter: x-rapidapi-key
  description: Your RapidAPI key
  sources:
  - openapi/nokia-corp-network-as-code-openapi.yml
  docs_detail: The docs call it the "application key" (or "token application key") created per application
    in the console Dashboard; the SDK is instantiated with api_key=<key> and rapidapi_host="network-as-code.nokia.rapidapi.com",
    which the gateway expects as the x-rapidapi-host header. Treat keys as secrets; organization keys
    are required for devices authorized to an organization (401/403 otherwise).
- name: openId
  type: openIdConnect
  openIdConnectUrl: https://example.com/.well-known/openid-configuration
  description: OpenID Connect authentication (declared in Single-NaC-API-OAS.yaml; discovery URL is a
    placeholder)
  sources:
  - https://raw.githubusercontent.com/nokia-steward/network-as-code-sdks/main/openapi/Single-NaC-API-OAS.yaml
  flows:
  - name: Client Initiated Backchannel Authentication (CIBA)
    description: 'Network as Code handles end-user authorization transparently for most APIs: access to
      the device is guarded by an Authorization Server that NaC polls until a response is produced; the
      developer calls the APIs normally with the application key.'
  - name: Authorization Code
    description: 'Used when the end user must take positive action (e.g. Number Verification): the application
      builds an authorization URL at the NaC authorization server with its own redirect URI, the user
      consents, an operator code is returned to the redirect URI and exchanged for a single-use access
      token passed with the subsequent request.'
  authorization_server_operations:
  - get_well_known_oidc_openid_configuration_get (GET /.well-known/openid-configuration)
  - get_well_known_oauth_oauth_authorization_server_get (GET /.well-known/oauth-authorization-server)
  - get_jwks_apps__nac_app_ref___well_known_jwks_json_get (GET /oauth2/v1/apps/{nac_app_ref}/.well-known/jwks.json)
  - get_client_credentials (GET /oauth2/v1/auth/clientcredentials)
  purpose: Purpose values follow the W3C Data Privacy Vocabulary (DPV), e.g. dpv:FraudPreventionAndDetection
    and dpv:RequestedServiceProvision; the purpose declared at application registration must match the
    purpose sent at runtime (Number Verification and Consent Info take it per call, prefixed to the scope).
consent_management:
  docs: https://networkascode.nokia.io/docs/general-concepts/consent-identity-mgmt
  b2b: An organization admin submits a Consent & Authorization form (device, scope, authorized party,
    operator, revocation date) which the NaC Admin validates with the operators before the authorized
    party can call the scoped APIs on those devices.
docs_pages:
- https://networkascode.nokia.io/docs/getting-started#get-your-first-api-key
- https://networkascode.nokia.io/docs/general-concepts/consent-identity-mgmt