### eInnsyn Client Log - Application Started

Source: https://docs.digdir.no/docs/eInnsyn/einnsyn_install_tjeneste

Example log message indicating that the eInnsyn client application has started successfully and is running. This message is typically found in the einnsyn-klient.out log file.

```json
{"@timestamp":"2017-11-30T12:22:42.812+01:00","@version":1,"message":"Splitting took 0 ms","logger_name":"no.difi.einnsyn.sender.service.AsyncDataSplittingService","thread_name":"main","level":"DEBUG","level_value":10000}
{"@timestamp":"2017-11-30T12:22:42.812+01:00","@version":1,"message":"Splitting serialization took 0 ms","logger_name":"no.difi.einnsyn.sender.service.AsyncDataSplittingService","thread_name":"main","level":"DEBUG","level_value":10000}
{"@timestamp":"2017-11-30T12:22:42.812+01:00","@version":1,"message":"ConversationId \"57e0477e-cec1-476c-9e49-e45734bfc736\"","logger_name":"ipclient_transactionlogger","thread_name":"main","level":"INFO","level_value":20000}
{"@timestamp":"2017-11-30T12:22:42.812+01:00","@version":1,"message":"Create message http://localhost:9093<{\"receiverId\":\"991825827\",\"serviceIdentifier\":\"DPE_DATA\",\"conversationId\":\"57e0477e-cec1-476c-9e49-e45734bfc736\",\"customProperties\":{\"orgnumber\":\"971277882\",\"data_type\":\"journaldata\"}},{Content-Type=[application/json]}>","logger_name":"directorylistener_transactionlogger","thread_name":"main","level":"INFO","level_value":20000}
{"@timestamp":"2017-11-30T12:22:42.828+01:00","@version":1,"message":"Post url http://localhost:9093","logger_name":"ipclient_transactionlogger","thread_name":"main","level":"INFO","level_value":20000}
{"@timestamp":"2017-11-30T12:22:42.828+01:00","@version":1,"message":"Upload message http://localhost:9093/out/messages/57e0477e-cec1-476c-9e49-e45734bfc736
```

--------------------------------

### Install and Start eInnsyn Client Service

Source: https://docs.digdir.no/docs/eInnsyn/einnsyn_install_tjeneste

Commands to install and start the eInnsyn client as a Windows service. These commands should be executed in an administrator command prompt after configuring the einnsyn-klient.xml file.

```bash
einnsyn-klient.exe install
einnsyn-klient.exe start
```

--------------------------------

### Download eInnsyn Client Files

Source: https://docs.digdir.no/docs/eInnsyn/einnsyn_install_forutsetninger_verktoy

This snippet lists the essential files required for installing the eInnsyn client. These files include the client application JAR, the executable, and the configuration file.

```text
sender-%versjonsnr%.jar (Klientapplikasjon)
einnsyn-klient.exe (Klientapplikasjon)
einnsyn-klient.xml (Konfigurasjonsfil for klient)
```

--------------------------------

### Install and Start Integration Point Service

Source: https://docs.digdir.no/docs/eFormidling/installasjon/Eksempel/start_og_stopp

This snippet demonstrates how to install and start the eFormidling integration point as a Windows service using the Winsw.exe utility. It requires administrator privileges and assumes the necessary executable and configuration files are in place.

```Shell
integrasjonspunkt-service.exe install
integrasjonspunkt-service.exe start
```

--------------------------------

### Prepare eFormidling Integration Point Installation

Source: https://docs.digdir.no/docs/eFormidling/installasjon/forberede_installasjon

This section details the prerequisites for installing the eFormidling integration point. It involves ordering access, obtaining business certificates, and configuring the environment for secure and efficient operation.

```text
1. Bestille tilganger
2. Bestille virksomhetssertifikat
3. Tilgjengeliggjøre virksomhetssertifikatet i eFormidlings sertifikatkatalog
4. Tilgjengeliggjøre virksomhetssertifikatet for virksomhetens integrasjonspunkt
5. Velg hvordan integrasjonspunktet skal kjøres
6. Sett av nødvendige ressurser for integrasjonspunktet
7. Planlegg sikring av integrasjonspunktet
8. Konfigurer brannmur dersom nødvendig
9. Konfigurer tidssynkronisering dersom det mangler
10. Neste steg
```

--------------------------------

### Full Service Configuration Example (XML)

Source: https://docs.digdir.no/docs/eFormidling/installasjon/Eksempel/start_og_stopp

An example of a complete service configuration for the integration point, including logging, service details, and executable arguments. This demonstrates how the log rotation configuration is integrated within the service definition.

```XML
<service>
            <id>einnsyn-integrasjonspunkt</id>
            <name>einnsyn-integrasjonspunkt</name>
            <description>Klient for opplasting av journaldata og nedlasting av innsynskrav</description>
            <argument>-Xmx2048m</argument>
            <argument>-jar</argument>
            <argument>integrasjonspunkt-2.0.7.jar</argument>
            <argument>--app.logger.enableSSL=false</argument>
            <logpath>%BASE%/integrasjonspunkt-logs</logpath>
            <log mode="roll-by-size">
                <sizeThreshold>10240</sizeThreshold>
                <keepFiles>8</keepFiles>
            </log>
            <executable>java</executable>
</service>
```

--------------------------------

### Order Access for eFormidling

Source: https://docs.digdir.no/docs/eFormidling/installasjon/forberede_installasjon

Before using eFormidling, you must order the necessary access to eFormidling and the message services you intend to use. Separate test accesses are required for the test environment.

```text
Før en kan ta i bruk eFormidling må en bestille nødvendige tilganger til eFormidling og de meldingstjenestene som ønskes brukt.
Merk at dersom en ønsker å ta i bruk eFormidling i testmiljø så må det bestilles egne test-tilganger:
  * Testing

Se Samarbeidsportalen for hva som skal til for å få nødvendige tilganger til eFormidling og meldingstjenestene som brukes av eFormidling:
  * Ta i bruk eFormidling (ekstern lenke)

Enkelte av meldingstjenestene krever at virksomheten oppretter en bruker med brukernavn og passord:
  * Opprette bruker for Altinn Formidling (nødvendig for å bruke eFormidlings meldingstjeneste)
  * Opprette bruker for KS SvarUt og SvarInn
  * Opprette bruker for Altinn Digital Post

Ta kontakt med vår servicedesk ved behov:
  * servicedesk@digdir.no
```

--------------------------------

### Configure einnsyn-klient.xml

Source: https://docs.digdir.no/docs/eInnsyn/einnsyn_install_forutsetninger_verktoy

This section details the configuration file for the eInnsyn client, which is essential for setting up its operational parameters. The file is typically edited using standard text editors.

```xml
<configuration>
  <!-- Configuration settings for einnsyn-klient -->
</configuration>
```

--------------------------------

### Manage Integration Point Service (Command Line)

Source: https://docs.digdir.no/docs/eFormidling/installasjon/Eksempel/start_og_stopp

Commands to stop, uninstall, install, and start the integration point when it is running as a Windows service. These commands are used to update the service after changing the version number in the configuration file.

```Batch
integrasjonspunkt-service.exe stop
integrasjonspunkt-service.exe uninstall
integrasjonspunkt-service.exe install
integrasjonspunkt-service.exe start
```

--------------------------------

### Start Integration Point for Production (Command Line)

Source: https://docs.digdir.no/docs/eFormidling/installasjon/Eksempel/start_og_stopp

Command to start the integration point for production environments. It specifies JVM memory allocation and the JAR file to execute.

```Shell
java -Xmx2048m -jar integrasjonspunkt-[versjon].jar
```

--------------------------------

### Integration Point Log - Message Sent

Source: https://docs.digdir.no/docs/eInnsyn/einnsyn_install_tjeneste

Example log messages from the integration point's application.log file, showing the creation of a conversation resource and the successful sending of a message to the service bus.

```log
2017-12-11 11:01:19.538  INFO 14932 --- [ qtp10823740-24] n.d.m.nextmove.MessageOutController      : Created new conversation resource [id=b32ef599-4a2f-41ab-b641-ca29d0d63715, serviceIdentifier=DPE_DATA]
2017-12-11 11:01:20.211  INFO 14932 --- [ qtp10823740-31] AUDIT                                    : Message [id=b32ef599-4a2f-41ab-b641-ca29d0d63715, serviceIdentifier=DPE_DATA] sent to service bus
```

--------------------------------

### Start Integration Point for Testing (Command Line)

Source: https://docs.digdir.no/docs/eFormidling/installasjon/Eksempel/start_og_stopp

Command to start the integration point for testing environments. It specifies JVM memory allocation and the active Spring profile.

```Shell
java -Xmx2048m -jar -Dspring.profiles.active=staging integrasjonspunkt-[versjon].jar
```

--------------------------------

### ServiceRegistry 2.1.1 Plugin Example

Source: https://docs.digdir.no/docs/eFormidling/Oppgradering/endringslogg

Introduces support for plugins in ServiceRegistry to enable the integration point to be used in a four-corner model. An example project is provided for reference.

```Java
https://github.com/felleslosninger/efm-ip-plugin-example
```

--------------------------------

### Get Conversation by ID

Source: https://docs.digdir.no/docs/eFormidling/Utvikling/integrasjonspunkt_eformidling2_api_restdocs

Retrieves a specific conversation using its unique ID. This example demonstrates a successful GET request and the expected JSON response.

```curl
$ curl 'http://localhost:8080/api/conversations/49' -i -X GET \
    -H 'Accept: application/json'
```

--------------------------------

### Get Subscription by ID (cURL)

Source: https://docs.digdir.no/docs/eFormidling/Utvikling/integrasjonspunkt_eformidling2_api_restdocs

Retrieves a specific subscription using its unique identifier. This example demonstrates the cURL command to make the GET request and the expected JSON response for a successful retrieval.

```bash
$ curl 'http://localhost:8080/api/subscriptions/84' -i -X GET \
    -H 'Accept: application/json'
```

--------------------------------

### ID-porten Front-Channel Logout Call Example

Source: https://docs.digdir.no/docs/idporten/oidc/oidc_func_sso

An example of a GET request initiated by ID-porten to a client's logout URI during a front-channel logout event. It includes the issuer ('iss') and session identifier ('sid') parameters.

```HTTP
GET https://client.example.com/myapp/logout
     ?iss=https://idporten.no/
     &sid=D8Fgz-jEXG7JXP_VAORmAm1sKB0LjZyA3wAy-rVyMYc=
```

--------------------------------

### Kjøre integrasjonspunktet fra kommandovindu

Source: https://docs.digdir.no/docs/eFormidling/installasjon/automatisk_oppgradering

Instruksjoner for å starte og stoppe eFormidlings integrasjonspunkt manuelt ved hjelp av kommandolinjen.

```bash
java -jar integrasjonspunkt.jar
```

--------------------------------

### Using Test vs. Production Certificates

Source: https://docs.digdir.no/docs/Maskinporten/maskinporten_autentisering

Specifies that test environments require a test enterprise certificate, also obtainable from Buypass and Commfides, and provides links for ordering.

```URL
https://www.buypass.no/produkter/virksomhetssertifikat-esegl
```

```URL
https://www.commfides.com/bestilling-av-testsertifikatseid20/
```

--------------------------------

### Get Organization Capabilities by Process (Curl)

Source: https://docs.digdir.no/docs/eFormidling/Utvikling/integrasjonspunkt_eformidling2_api_restdocs

This example shows how to use curl to make a GET request to the Digdir API to retrieve capabilities for a specific organization identified by its ID and filtered by a particular process. It includes the request headers and the expected JSON response.

```curl
$ curl 'http://localhost:8080/api/capabilities/987654321?process=admin-process' -i -X GET \
    -H 'Accept: application/json'
```

```http
GET /api/capabilities/987654321?process=admin-process HTTP/1.1
Accept: application/json
Host: localhost:8080
```

```json
HTTP/1.1 200 OK
Vary: Origin
Vary: Access-Control-Request-Method
Vary: Access-Control-Request-Headers
Content-Type: application/json
X-Content-Type-Options: nosniff
X-XSS-Protection: 1; mode=block
Cache-Control: no-cache, no-store, max-age=0, must-revalidate
Pragma: no-cache
Expires: 0
X-Frame-Options: DENY
Content-Length: 732

{
  "capabilities" : [ { 
    "process" : "urn:no:difi:profile:arkivmelding:planByggOgGeodata:ver1.0",
    "serviceIdentifier" : "DPO",
    "documentTypes" : [ { 
      "type" : "arkivmelding",
      "standard" : "urn:no:difi:arkivmelding:xsd::arkivmelding"
    } ]
  }, { 
    "process" : "urn:no:difi:profile:arkivmelding:response:ver1.0",
    "serviceIdentifier" : "DPO",
    "documentTypes" : [ { 
      "type" : "arkivmelding_kvittering",
      "standard" : "urn:no:difi:arkivmelding:xsd::arkivmelding_kvittering"
    }, { 
      "type" : "status",
      "standard" : "urn:no:difi:arkivmelding:xsd::status"
    }, { 
      "type" : "feil",
      "standard" : "urn:no:difi:arkivmelding:xsd::feil"
    } ]
  } ]
}
```

--------------------------------

### Get Conversation by Message ID (Curl)

Source: https://docs.digdir.no/docs/eFormidling/Utvikling/integrasjonspunkt_eformidling2_api_restdocs

Retrieves a specific conversation using its unique message ID. This example demonstrates the GET request using cURL, including necessary headers like 'Accept'. It also shows the expected HTTP request and a successful JSON response.

```Shell
$ curl 'http://localhost:8080/api/conversations/messageId/ecfd35a3-3006-4757-b521-8524c56d0702' -i -X GET \
    -H 'Accept: application/json'
```

```HTTP
GET /api/conversations/messageId/ecfd35a3-3006-4757-b521-8524c56d0702 HTTP/1.1
Accept: application/json
Host: localhost:8080
```

```JSON
{
  "id" : 49,
  "conversationId" : "ea1d7c23-7df9-4ae7-81c5-5c9f73c316b9",
  "messageId" : "ecfd35a3-3006-4757-b521-8524c56d0702",
  "senderIdentifier" : "0192:910077473",
  "receiverIdentifier" : "0192:910075918",
  "processIdentifier" : "urn:no:difi:profile:arkivmelding:planByggOgGeodata:ver1.0",
  "messageReference" : "system-12463",
  "messageTitle" : "A message title",
  "serviceCode" : "4255",
  "serviceEditionCode" : "10",
  "lastUpdate" : "2019-03-25T12:38:23+01:00",
  "finished" : false,
  "expiry" : "2019-04-25T12:38:23+01:00",
  "direction" : "INCOMING",
  "serviceIdentifier" : "DPO",
  "messageStatuses" : [ {
    "id" : 76,
    "lastUpdate" : "2019-11-05T12:04:34+02:00",
    "status" : "INNKOMMENDE_MOTTATT",
    "description" : "INNKOMMENDE_MOTTATT"
  } ]
}
```

--------------------------------

### JSON-LD Compact Example for eInnsyn

Source: https://docs.digdir.no/docs/eInnsyn/publisering_til_einnsyn

This example shows the structure of a JSON-LD file in compact format for eInnsyn, including context definitions and a sample 'Saksmappe' object with an ID. It demonstrates how to define namespaces and base URIs.

```json
{
"@context":{
  "@base":"http://data_test.einnsyn.no/",
  "arkiv":"http://www.arkivverket.no/standarder/noark5/arkivstruktur/",
  "xsd":"http://www.w3.org/2001/XMLSchema#"
},
"@graph":[{
  "@id":"692650f3-f090-4ab0-a2ee-d564adb5644f",
  "@type":"arkiv:Saksmappe",.....
}
```

--------------------------------

### Configure Legacy BEST/EDU Interface

Source: https://docs.digdir.no/docs/eFormidling/installasjon/installasjon

Configure connection details for the legacy BEST/EDU interface, including endpoint URL, system type, and authentication credentials for older archival systems.

```properties
difi.move.noarkSystem.endpointURL=http://localhost:8088/testExchangeBinding
difi.move.noarkSystem.type=P360
difi.move.noarkSystem.username=myuser
difi.move.noarkSystem.password=mypassword
difi.move.noarkSystem.domain=MYUSERDOMAIN
```

--------------------------------

### Reinstallere einnsyn-klient tjeneste

Source: https://docs.digdir.no/docs/eInnsyn/einnsyn_oppdatere_tjeneste

Disse kommandoene brukes for å stoppe, avinstallere, installere og starte einnsyn-klienten på nytt. Dette er nødvendig etter endringer i `einnsyn-klient.xml`.

```bash
einnsyn-klient.exe stop
einnsyn-klient.exe uninstall
einnsyn-klient.exe install
einnsyn-klient.exe start
```

--------------------------------

### Configure Minimum Integration Point Settings

Source: https://docs.digdir.no/docs/eFormidling/installasjon/installasjon

This snippet shows the essential properties required to configure the integration point, including organization number, keystore alias, password, path, type, and enabling/disabling eInnsyn. These properties are typically set in a configuration file or as Java parameters.

```properties
difi.move.org.number=991825827
difi.move.org.keystore.alias=myalias
difi.move.org.keystore.password=mypassword
difi.move.org.keystore.path=file:c:/integrasjonspunkt/keystore.p12
difi.move.org.keystore.type=PKCS12
difi.move.feature.enableDPE=false
```

--------------------------------

### Incoming DPO Message Request Example (HTTP)

Source: https://docs.digdir.no/docs/eFormidling/Utvikling/integrasjonspunkt_eformidling2_api_restdocs

This snippet illustrates the HTTP request format for searching incoming DPO messages. It details the GET method, path, query parameters, and headers.

```http
GET /api/messages/in?serviceIdentifier=DPO HTTP/1.1
Accept: application/json
Host: localhost:8080
```

--------------------------------

### Configure KS SvarUt/SvarInn Basic Setup

Source: https://docs.digdir.no/docs/eFormidling/installasjon/installasjon

This snippet demonstrates the basic configuration for enabling KS SvarUt and SvarInn, including setting up usernames and passwords for both sending and receiving functionalities. It also shows how to disable error email notifications.

```properties
difi.move.feature.enableDPF=true
difi.move.fiks.inn.username=myusername
difi.move.fiks.inn.password=mypassword
difi.move.fiks.ut.username=myusername2
difi.move.fiks.ut.password=mypassword2
difi.move.fiks.inn.mailOnError=false
```

--------------------------------

### Get All Individual Capabilities (Curl)

Source: https://docs.digdir.no/docs/eFormidling/Utvikling/integrasjonspunkt_eformidling2_api_restdocs

This example demonstrates how to use curl to fetch all capabilities associated with an individual, identified by their unique ID. The request specifies JSON as the accepted response format and includes the necessary headers.

```curl
$ curl 'http://localhost:8080/api/capabilities/01017012345' -i -X GET \
    -H 'Accept: application/json'
```

```http
GET /api/capabilities/01017012345 HTTP/1.1
Accept: application/json
Host: localhost:8080
```

```json
HTTP/1.1 200 OK
Vary: Origin
Vary: Access-Control-Request-Method
Vary: Access-Control-Request-Headers
Content-Type: application/json
X-Content-Type-Options: nosniff
X-XSS-Protection: 1; mode=block
Cache-Control: no-cache, no-store, max-age=0, must-revalidate
Pragma: no-cache
Expires: 0
X-Frame-Options: DENY
Content-Length: 1269

{
  "capabilities" : [ { 
    "process" : "urn:no:difi:profile:digitalpost:info:ver1.0",
    "serviceIdentifier" : "DPI",
    "postAddress" : {
      "name" : "Kari Nordmann",
      "street" : "Utsikten 1",
      "postalCode" : "2900",
      "postalArea" : "FJELLHEIMEN",
      "country" : "Norway"
    },
    "returnAddress" : {
      "name" : "Kari Nordmann",
      "street" : "Utsikten 1",
      "postalCode" : "2900",
      "postalArea" : "FJELLHEIMEN",
      "country" : "Norway"
    },
    "documentTypes" : [ { 
      "type" : "digital",
      "standard" : "urn:no:difi:digitalpost:xsd:digital::digital"
    } ]
  }, { 
    "process" : "urn:no:difi:profile:digitalpost:vedtak:ver1.0",
    "serviceIdentifier" : "DPI",
    "postAddress" : {
      "name" : "Kari Nordmann",
      "street" : "Utsikten 1",
      "postalCode" : "2900",
      "postalArea" : "FJELLHEIMEN",
      "country" : "Norway"
    },
    "returnAddress" : {
      "name" : "Kari Nordmann",
      "street" : "Utsikten 1",
      "postalCode" : "2900",
      "postalArea" : "FJELLHEIMEN",
      "country" : "Norway"
    },
    "documentTypes" : [ { 
      "type" : "digital",
      "standard" : "urn:no:difi:digitalpost:xsd:digital::digital"
    } ]
  } ]
}
```

--------------------------------

### View API Access

Source: https://docs.digdir.no/docs/Maskinporten/maskinporten_sjolvbetjening_api

Example of retrieving the access list for a specific scope using a GET request. This returns a JSON array detailing which organizations have been granted access, their state, and associated timestamps.

```HTTP
GET /scopes/access?scope=difi:api3 HTTP/1.1


```

--------------------------------

### Logg inn i Azure CLI

Source: https://docs.digdir.no/docs/eFormidling/installasjon/Eksempel/installasjon_aks

Kommando for å logge inn i Azure CLI. Ingen spesifikk kode er gitt, kun en placeholder.

```bash
$
```

--------------------------------

### API Request with DPoP Authorization

Source: https://docs.digdir.no/docs/idporten/oidc/oidc_func_dpop

This example demonstrates an API request using the GET method to a protected resource. It includes the 'Authorization' header with the DPoP access token and the 'DPoP' header containing the DPoP proof.

```http
GET /protectedresource HTTP/1.1
Host: resource.example.org
Authorization: DPoP Kz~8mXK1EalYznwH-LC-1fBAo.4Ljp~zsPE_NeO.gxU
DPoP: eyJ0eXAiOiJkcG9wK2p3dCIsImFsZyI6IkVTMjU2IiwiandrIjp7Imt0eSI6Ik
VDIiwieCI6Imw4dEZyaHgtMzR0VjNoUklDUkRZOXpDa0RscEJoR04yVVFVZldWQVdCR
 nMiLCJ5IjoiOVZFNGpmX09rX282NHpiVFRsY3VOSmFqSG10NnY5VERWclUwQ2R2R1JE
 QSIsImNydiI6IlAtMjU2In19.eyJqdGkiOiJlMWozVl9iS2ljOC1MQUVCIiwiaHRtIj
 oiR0VUIiwiaHR1IjoiaHR0cHM6Ly9yZXNvdXJjZS5leGFtcGxlLm9yZy9wcm90ZWN0Z
 WRyZXNvdXJjZSIsImlhdCI6MTU2MjI2MjYxOCwiYXRoIjoiZlVIeU8ycjJaM0RaNTNF
 c05yV0JiMHhXWG9hTnk1OUlpS0NBcWtzbVFFbyJ9.2oW9RP35yRqzhrtNP86L-Ey71E
 OptxRimPPToA1plemAgR6pxHF8y6-yqyVnmcw6Fy1dqd-jfxSYoMxhAJpLjA
```

--------------------------------

### Configure eInnsyn Message Service (DPE)

Source: https://docs.digdir.no/docs/eFormidling/installasjon/installasjon

This section covers the configuration for the eInnsyn message service (DPE). It includes properties for enabling DPE and optimizing performance with batch reading. An example shows how to enable the DPE service.

```properties
difi.move.feature.enableDPE=true
```

--------------------------------

### Get Authorizations with ID-porten Token

Source: https://docs.digdir.no/docs/idporten/oidc/oidc_api_autorisasjoner

This example demonstrates how to retrieve client authorizations using an ID-porten token. The request requires an 'Authorization' header with a Bearer token that has the 'idporten:authorizations' scope and a person identifier.

```HTTP
GET /clients/authorizations
Authorization: Bearer <idporten-token med idporten:authorizatons-scope og personidentifikator>
```

--------------------------------

### Configure eFormidling Message Service (DPO)

Source: https://docs.digdir.no/docs/eFormidling/installasjon/installasjon

This section details the configuration for the eFormidling message service (DPO), which is realized through Altinn Formidling. It outlines the properties required for enabling DPO, specifying username, password, message channel, and reportees. An example demonstrates setting these properties.

```properties
difi.move.feature.enableDPO=true
difi.move.dpo.username=1234
difi.move.dpo.password=mypassword
```

--------------------------------

### Certificate/Key Management Recommendations

Source: https://docs.digdir.no/docs/Maskinporten/maskinporten_autentisering

Strongly advises against sharing client registrations (with secrets/keys) across multiple installations. Recommends using asymmetric keys over enterprise certificates for providers with many integrations. For security reasons, providers should not manage customer certificates/keys.

--------------------------------

### Creating Asymmetric Keys

Source: https://docs.digdir.no/docs/Maskinporten/maskinporten_autentisering

Notes that software for creating asymmetric keys varies and will not be covered in the Digitalization Directorate's technical documentation.

--------------------------------

### Maskinporten Token Example

Source: https://docs.digdir.no/docs/Maskinporten/maskinporten_guide_apitilbyder

This JSON object represents a typical Maskinporten token, including claims like scope, issuer, token type, expiration time, and consumer information. It also shows optional supplier and delegation source claims.

```JSON
{
  "scope" : "difitest:test2",
  "iss" : "https://test.maskinporten.no/",
  "client_amr" : "virksomhetssertifikat",
  "token_type" : "Bearer",
  "exp" : 1584694565,
  "iat" : 1584693565,
  "jti" : "IYRtIEzOYb8fHiIMEaqVHq_tXYGWe6OEOjOdsK-P_30",
  "consumer" : {
    "authority" : "iso6523-actorid-upis",
    "ID" : "0192:991825827"
  }
}
```

--------------------------------

### Installer PostgreSQL med Helm

Source: https://docs.digdir.no/docs/eFormidling/installasjon/Eksempel/installasjon_aks

Eksempel på bruk av Helm for å installere en PostgreSQL-database. Viser Helm-kommandoen og en utskrift av tilgjengelige charts.

```bash
$install postgresql bitnami/postgresql
```

--------------------------------

### Obtain Business Certificate for eFormidling

Source: https://docs.digdir.no/docs/eFormidling/installasjon/forberede_installasjon

A business certificate is mandatory for eFormidling to authenticate organizations securely. It's also used for end-to-end encryption, signing outgoing messages, and authenticating with third-party services. Both SEID v1 and v2 are supported, but not eSegl or SSL certificates.

```text
Før en virksomhet kan ta i bruk eFormidling må den ha fått utstedt et virksomhetssertifikat.
eFormidling krever virksomhetssertifikat for å autentisere virksomhetene som bruker tjenesten på en sikker måte. I tillegg brukes virksomhetssertifikatet til:
  * ende-til-ende kryptering av meldinger mellom virksomhetene i de tilfeller den underliggende meldingstjenesten støtter dette
  * signering av utgående meldinger i de tilfeller den underliggende meldingstjenesten støtter dette
  * autentisering av virksomheten mot enkelte tredjepartstjenester

En virksomhet på eFormidling kommuniserer i utgangspunktet som organisasjonen virksomhetssertifikatet er utstedt til, men det er også mulig for en organisasjon å opptre på vegne av andre organisasjoner.
eFormidling støtter virksomhetssertifikat av typene SEID v1 og v2, men ikke eSegl. SSL-sertifikater (inkludert wildcard-sertifikater) er ikke virksomhetssertifikater.
Merk at dersom en ønsker å ta i bruk eFormidlings testmiljø så må den få utstedt et eget test-virksomhetssertifikat.
En kan enten bruke et allerede utstedt virksomhetssertifikat eller bestille et nytt:
  * Bestill virksomhetssertifikat fra Buypass (ekstern lenke)
  * Bestill virksomhetssertifikat fra Commfides (ekstern lenke)
```

--------------------------------

### Configure Integrasjonspunkt as a Windows Service using Winsw

Source: https://docs.digdir.no/docs/eFormidling/installasjon/Eksempel/start_og_stopp

This configuration sets up the Integrasjonspunkt application to run as a Windows service using the winsw wrapper. It specifies the service ID, display name, description, the executable (Java), and arguments including the JAR file and Spring profiles. It also configures logging.

```xml
<service>
  
  <!-- ID of the service. It should be unique accross the Windows system-->
  <id>kosmossvc</id>
  <!-- Display name of the service -->
  <name>Kosmos Service</name>
  <!-- Service description -->
  <description>Keeps the integrasjonspunkt application up-to-date.</description>
  
  <!-- Path to the executable, which should be started -->
  <executable>java</executable>
    <arguments>-jar %BASE%\kosmos-X.Y.Z.jar --spring.profiles.active=production --spring.config.additional-location=file:%BASE%\integrasjonspunkt-local.properties</arguments>
  <logpath>%BASE%\kosmos-logs</logpath>
  
  <log mode="roll-by-size">
    <sizeThreshold>10240</sizeThreshold>
    <keepFiles>8</keepFiles>
  </log>
</service>
```

--------------------------------

### View Access to API Scope via Maskinporten API

Source: https://docs.digdir.no/docs/Maskinporten/maskinporten_guide_apitilbyder

This snippet demonstrates how to view existing access grants for a specific API scope using a GET request to the Maskinporten self-service API. The response is a JSON array detailing the scope, state, and consumer organization number.

```HTTP
GET /scopes/access?scope=difi:api3 HTTP/1.1
```

--------------------------------

### Get Authorizations with Maskinporten Token

Source: https://docs.digdir.no/docs/idporten/oidc/oidc_api_autorisasjoner

This example shows how to obtain client authorizations using a Maskinporten token. The request is similar to using an ID-porten token but requires a Maskinporten token with the 'idporten:authorizations' scope and includes a POST request body with the 'pid'. The response is the same as when using an ID-porten token.

```HTTP
POST /clients/authorizations
Authorization: Bearer <maskinporten med idporten:authorizatons-scope>
Content-Type: application/json

{
    "pid": "20914695016"
}
```