Skip to content

Client

The NAIS platform provides support for simple declarative provisioning of a client that your application may use to integrate with Maskinporten, and in turn consume services and APIs served by external agencies.

The client allows your application to leverage Maskinporten for authentication and authorization when performing service-to-service requests to external agencies. To achieve this, your application must:

When a client requests a token from Maskinporten:

  • Maskinporten validates the validity of the JWT and its signature (Runtime JWK Secret used to sign the JWT).
  • If the client has access to the requested list of scopes, an access_token will be returned to the client. The token can be used for authentication to the intended external service.

Danger

Make sure that the relevant service providers have pre-registered NAV's organization (number: 889640782) as a valid consumer of any scopes that you define. Provisioning of client will fail otherwise.

NAV´s pre-registered scopes can be found with proper access rights in Digdir selvbetjening.

Getting Started

Access Policies

Maskinporten is a third-party service outside of our clusters, which is not reachable by default like most third-party services.

Google Cloud Platform (GCP)

The following outbound external hosts are automatically added when enabling this feature:

  • ver2.maskinporten.no in development
  • maskinporten.no in production

You do not need to specify these explicitly.

On-premises

You must enable and use webproxy for external communication.

Spec

See the NAIS manifest.

Configuration

spec:
  maskinporten:
    enabled: true 
    scopes:
      consumes:
        - name: "skatt:some.scope"
        - name: "nav:some/other/scope"

  # required for on-premises only
  webproxy: true

Usage

Runtime Variables and Credentials

The following environment variables and files (under the directory /var/run/secrets/nais.io/maskinporten) are available at runtime:


MASKINPORTEN_CLIENT_ID

Note

Client ID that uniquely identifies the application in Maskinporten.

Example value: e89006c5-7193-4ca3-8e26-d0990d9d981f


MASKINPORTEN_SCOPES

Note

The scopes registered for the client at Maskinporten as a whitepace-separated string. See JWT grants for more information.

Example value: nav:first/scope nav:another/scope


MASKINPORTEN_CLIENT_JWK

Note

Private JWK containing an RSA key belonging to your client. Used to sign client assertions during client authentication.

{
  "use": "sig",
  "kty": "RSA",
  "kid": "jXDxKRE6a4jogcc4HgkDq3uVgQ0",
  "alg": "RS256",
  "n": "xQ3chFsz...",
  "e": "AQAB",
  "d": "C0BVXQFQ...",
  "p": "9TGEF_Vk...",
  "q": "zb0yTkgqO...",
  "dp": "7YcKcCtJ...",
  "dq": "sXxLHp9A...",
  "qi": "QCW5VQjO..."
}

MASKINPORTEN_WELL_KNOWN_URL

Note

The well-known URL for the OAuth 2.0 authorization server (in this case, Maskinporten) metadata document.

Example value: https://ver2.maskinporten.no/.well-known/oauth-authorization-server


MASKINPORTEN_ISSUER

Note

issuer from the metadata discovery document.

Example value: https://ver2.maskinporten.no/


MASKINPORTEN_JWKS_URI

Note

jwks_uri from the metadata discovery document.

Example value: https://ver2.maskinporten.no/jwk


MASKINPORTEN_TOKEN_ENDPOINT

Note

token_endpoint from the metadata discovery document.

Example value: https://ver2.maskinporten.no/token


Consuming an API

Refer to the documentation at DigDir.

You may skip any step involving client registration as this is automatically handled when enabling this feature.

Legacy

Info

This section only applies if you have an existing client registered at the IaC repository

Migration guide to keep existing Maskinporten client (NAIS application only)

The following describes the steps needed to migrate a client registered in IaC repository.

Step 1 - Update your client description in the IaC repository

  • Ensure the description of the client registered in the IaC repository follows the naming scheme:
<cluster>:<metadata.namespace>:<metadata.name>

Step 3 - Deploy your NAIS application with Maskinporten provisioning enabled

Step 4 - Delete your application from the IaC repository

  • Verify that everything works after the migration
  • Delete the application from the IaC repository in order to maintain a single source of truth.

Last update: 2022-05-18
Created: 2021-08-13