Can AI agents automate ID-porten?

ID-porten is automatable today as a national OpenID Connect authentication service, not as a line-of-business application. Digdir documents the authorization-code flow as the preferred integration: a pre-registered relying party redirects the end user to /authorize, exchanges the code at /token, and receives an ID token plus optional access and refresh tokens. Client authentication at the token endpoint is client_secret_basic, client_secret_post, or the recommended private_key_jwt signed with a Norwegian virksomhetssertifikat. Only response_type=code is supported. Clients must implement single logout and front-channel logout. The ID token carries a pairwise sub and a proprietary pid national-identifier claim. Client registration is available through Samarbeidsportalen self-service, a self-service API, or a service-desk request. This record is the identity provider; Altinn, Maskinporten, Ansattporten, Feide and BankID as a standalone eID are outside the product boundary. Vendor documentation does not settle first-party MCP ownership. No official SDK, general CLI or computer-use probe was established.

Best path today: api · Overall automatability: 7/10