OIDC profil - IdP för invånare
Profilen som följs: The Swedish OpenID Connect Profile Version: 1.0 - 2023-12-11
ATK | Krav | Eventuella avsteg |
|---|---|---|
Discovery/Well-known (OP/IdP) |
| |
1 | Följa kraven definierade under Final: OpenID Connect Discovery 1.0 incorporating errata set 2 |
|
2 | Required fält:
|
|
Client registration |
| |
5 | An OpenID Provider compliant with this profile MUST still be able to handle the client registration parameters specified in this section and in section 2 of [OpenID.Registration]. This means that if an OpenID Provider registers Relying Parties by other means, it MUST gather and maintain all required client information parameters in the following table.
| Inte response_types |
6 | Optional information gathered for client registration:
| Finns inte med i 3.2 |
Authentication request |
| |
8a | For requests toward the Required for RP i auth-request and required for OP/IdP to process:
|
|
9a | Additional parameters optional for RP to send but required for OP/IdP to handle:
|
|
9b | “request” parameter is optional for RP to send but required for OP/IdP to handle
| inte requirement och validering av iss/aud i samband med detta |
9c | I undantagsfallet då RP är av typen “public client” så är nedan nämnda parametrar REQUIRED i auth-request för att följa PKCE:
Regular Relying Parties (i.e., not Public Clients) SHOULD use the Proof Key for Code Exchange (PKCE) extension, [RFC7636] and include the A "Public Client", i.e., a browser-based web application or a native mobile app with no backend logic, MUST use PKCE and include the When PKCE is used, the code challenge method An OpenID Provider compliant with this profile MUST support the PKCE extension including support for the An OpenID Provider MUST NOT allow a Relying Party to use the | Inget sätt att indikera public client på, så ingen validering på detta |
10 | When processing a request: An OpenID Provider compliant with this profile MUST follow the requirements stated in section 3.1.2.2 of [OpenID.Core] and the requirements put in section 2.1 of this profile. |
|
11 | The OpenID Provider MUST NOT proceed with the authentication if the request contains a |
|
Authentication responses |
| |
14 | Entities compliant with this profile MUST follow the requirements regarding authentication error responses put in section 3.1.2.6 of [OpenID.Core]. OpenID Providers SHOULD limit the use of error codes to the sets defined in:
All error codes defined in the OpenID Connect and OAuth2 specifications except for |
|
15 | A non-completed authentication process may be caused by:
In the latter case the OpenID Provider MUST inform the user about the error that occurred before responding with an error response. In both above scenarios the |
|
Client auth |
| |
16 | OpenID Providers compliant with this profile MUST support the |
|
17 | A Relying Party SHOULD default to use the
|
|
Tokens |
| |
19a | A Token Request MUST have the |
|
19b | A Token Request MUST have the OBS! detta är ett avsteg från ATK 19a för att kunna stödja CIBA OpenID Connect Client-Initiated Backchannel Authentication Flow - Core 1.0 |
|
20 | If PKCE parameters were sent in the authentication request, see section 2.1.8 above, the Token Request MUST include the PKCE |
|
21 | The token response MUST include an access token (to be used to make UserInfo requests) and an ID Token |
|
22 | ID TokenRequired content:
Optional content:
Conditional content:
|
|
23 | The lifetime of an ID Token should be kept as short as possible, and MUST NOT exceed 5 minutes. Shorter times are RECOMMENDED when possible. |
|
24 | Regarding the “sub” claim of the ID token: An OpenID Provider compliant with this profile MUST support the In order to avoid privacy violations an OpenID Provider MUST NOT use an end-user attribute that reveals personal information about the end-user as the value for | Ingen support för public, endast pairwise |
25 | An OpenID Provider compliant with this profile MUST adhere to section 5.5.1.1 of [OpenID.Core] regarding issuance of the |
|
Security requirements |
| |
28 | All transactions MUST be protected in transit by TLS as described in [NIST.800-52.Rev2]. |
|
29 | All parties MUST conform to applicable recommendations in section 16, "Security Considerations" of [OAuth2.RFC6749] and those found in "OAuth 2.0 Threat Model and Security Considerations", [RFC6819]. | Behöver bekräfta några punkter |
30a | All entities compliant with this profile MUST follow the guidelines in [NIST.800-131A.Rev2] regarding use of algorithms and key lengths1. Specifically, for signature and encryption keys the following requirements apply:
|
|
30b | All entities compliant with this profile MUST follow the guidelines in [NIST.800-131A.Rev2] regarding use of algorithms and key lengths1. Specifically, for signature and encryption keys the following requirements apply:
|
|
31a | Entities conforming to this profile MUST support algorithms according to "JSON Web Algorithms (JWA)", [RFC7518], with the following additions:
The sender of a secure message MUST NOT use an algorithm that is not set as REQUIRED in [RFC7518] or in the listing above, unless it is explicitly declared by the peer in its metadata (Discovery document or Client Registration metadata). |
|
31b | Entities conforming to this profile MUST support algorithms according to "JSON Web Algorithms (JWA)", [RFC7518], with the following additions:
| Saknas |
32 | Entities compliant with this profile MUST follow the requirements from section section 10.1 of [OpenID.Core]. This section states the following:
In order to facilitate for rotation/update of asymmetric keys and to enable for the receiving entity to dynamically update the sender's JWK Set document entities compliant with this profile SHOULD include the |
|
33 |
|
|
34 | ID Tokens issued by OpenID Providers compliant with this profile MUST be signed and MAY be encrypted using the appropriate key of the requesting Relying Party |
|
Korrigerande extra krav (Logout) |
| |
35 | Återställ avsteget dokumenterat under https://inera.atlassian.net/wiki/spaces/ST/pages/5335319454/3.1+SAD+-+IdP+-+OIDC-Profil#Avsteg-fr%C3%A5n-arbetsunderlaget gällande id_token_hint där vi också stödjer att skicka in refresh och access-token. Se istället spec: id_token_hint RECOMMENDED. ID Token previously issued by the OP to the RP passed to the Logout Endpoint as a hint about the End-User's current authenticated session with the Client. This is used as an indication of the identity of the End-User that the RP is requesting be logged out by the OP. |
|
36 | Implementera “logout_hint” OPTIONAL. Hint to the Authorization Server about the End-User that is logging out. The value and meaning of this parameter is left up to the OP's discretion. For instance, the value might contain an email address, phone number, username, or session identifier pertaining to the RP's session with the OP for the End-User. (This parameter is intended to be analogous to the |
|
52 | OpenID Providers MUST support the use of the HTTP |
|