Skip to content

Maskinporten Client

Status: Opt-In Open Beta

This feature is only available in team namespaces



Maskinporten is a service provided by DigDir that allows API providers - in this case, external agencies - to securely enforce server-to-server authorization of their exposed APIs using OAuth 2.0 JWT grants, inspired by Google's System Accounts.

With Maskinporten, API providers may model access policies by using scopes based on the organization number of the consumer.

The NAIS platform provides support for simple declarative provisioning of a Maskinporten 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 implement JWT grants.


Getting Started

    enabled: true
      - name: "nav:some/scope"

  # required for on-premises only
  webproxy: true


See the NAIS manifest.

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:

  • in development
  • in production

You do not need to specify these explicitly.


You must enable and use webproxy for external communication.


Maskinporten allows API providers to define access to their APIs, modeled as scopes and based on the consumer's organization number.

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).
  • When client has access to the requested list of scopes, an access_token will be returned to the client and which can be used for authentication to the intended external service.


Make sure that the relevant service providers have pre-registered NAV 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.


Runtime Variables and Credentials

The following environment variables and files (under the directory /var/run/secrets/ are available at runtime:


Maskinporten client ID. Unique ID for the application in Maskinporten.

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


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


The well-known URL for the OIDC metadata discovery document for Maskinporten.

Example value:


Private JWK containing the private RSA key for creating signed JWTs when using the JWT grants.

"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..."

Consume 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.



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:

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.


See ID-porten internals.

Permanently deleting a client


Permanent deletes are irreversible. Only do this if you are certain that you wish to completely remove the client from DigDir.

When an MaskinportenClient resource is deleted from a Kubernetes cluster, the client is not deleted from DigDir.


The Application resource owns the MaskinportenClient resource, deletion of the former will thus trigger a deletion of the latter.

If the MaskinportenClient resource is recreated, the client will thus retain the same client ID.

If you want to completely delete the client from DigDir, you must add the following annotation to the MaskinportenClient resource:

kubectl annotate maskinportenclient <app>

When this annotation is in place, deleting the MaskinportenClient resource from Kubernetes will trigger removal of the client from DigDir.