Förväntade deltagare
DIGG: Jakob Melander - extern.jakob.melander@digg.se samt Henric Norlander
INERA: Rickard Plars - Rickard.Plars@inera.se
EHM: Isabella Lang eller Nicklas Dahlbäck - isabella.lang@ehalsomyndigheten.se eller ext.Niklas.Dahlback@ehalsomyndigheten.se
Internetstiftelsen: Rasmus Larsson - rasmus.larsson@internetstiftelsen.se , Stefan Halen stefan.halen@internetstiftelsen.se
09.00–09.30 | Uppstart och genomgång inför testerna
Genomgång av aktuella testfall och testernas omfattning (scope).
Avstämning kring hur testerna ska genomföras.
Genomgång av hur testresultaten ska dokumenteras och följas upp. Förslagsvis här i kolumnen för Sandbox: Testprotkoll - RU Identitet & Behörighet - Confluence
Diskussion kring respektive aktörs möjligheter att automatisera testerna.
Frågor och övriga funderingar inför teststart.
Under dagen | Tillgänglighet via chatt
Efter uppstartsmötet genomförs testerna självständigt av respektive aktör. Samtliga deltagare finns tillgängliga via en gemensam chatt under dagen för att snabbt kunna hantera eventuella problem, frågor eller behov av samordning.
Om problem uppstår som kräver vidare diskussion eller gemensamma beslut kan ett separat avstämningsmöte vid behov sammankallas.
Syftet är att skapa goda förutsättningar för att genomföra testerna effektivt utan att behöva binda upp samtliga deltagare under hela dagen.
13.00–13.15 | Kort avstämning
Uppföljning av hur testgenomförandet fortlöper.
Avstämning kring eventuella hinder eller problem.
Bedömning av om vi behöver prioritera om, justera testomfattningen eller vidta andra åtgärder inför eftermiddagen.
14.30–15.00 | Genomgång av testresultat
Gemensam genomgång av genomförda tester och dokumenterade resultat.
Avstämning av testutfall: OK eller NOK.
Diskussion kring eventuella avvikelser och kvarstående frågor.
Övriga frågor.
Avslut av mötet.
Testspecifikationer version 0.2.0 (draft), test-specifications/. Testfallen är grupperade per Entity och sedan per funktion.
Testspecifikationerna utgår från BAS Federationsregelverk: BAS Federation Specifications
Alla testfall för Trust Anchor: ta_overview.md.
| Testfall | Beskrivning |
|---|---|
| TA-BAS-005 Verifying that the metadata policy matches the published BAS policy | Assert that the TA applies exactly the metadata policy that the federation has published, to all Entities resolved through it. |
| TA-BAS-006 Verifying client authentication and algorithm constraints in the policy | Assert that the policy enforces the single client authentication method of BAS and the signature algorithms that every Entity validates, so that any Client can authenticate at any Authorization Server. |
| TA-BAS-007 Verifying the values that the policy assigns | Assert that the only values the BAS policy assigns, rather than constrains, are values that follow from the BAS requirements, as the Swedish profile requires (see TA-OS-035). |
| TA-OS-034 Verifying that the metadata policy is well-formed | Assert that the metadata policy can be resolved by any compliant implementation without producing a policy error. |
| Testfall | Beskrivning |
|---|---|
| TA-BAS-008 Verifying the Entity Types admitted in BAS | Assert that the Trust Anchor only admits the Entity Types that BAS covers, and that its Immediate Subordinates are the Federation Registration Entities. |
| Testfall | Beskrivning |
|---|---|
| TA-BAS-001 Verifying the federation keys against the BAS rules | Assert that the Trust Anchor's Federation Entity Keys meet the requirements that apply to them in BAS. [BAS.Security] does not apply to Federation Entity Keys. For them, Section 9 of [BAS.Rules] makes Section 6 of [OIDC.Sweden.Federation] apply. |
| TA-BAS-002 TLS configuration | Assert that all TA endpoints are protected by TLS according to the federation's security requirements. |
Alla testfall för Federation Registration Entity: fre_overview.md.
| Testfall | Beskrivning |
|---|---|
| FRE-BAS-003 Verifying organization parameters | Assert that the FRE assigns the verified name and identifier of the organization that owns the Entity, so that peers can see which organization an Entity is registered for. |
| Testfall | Beskrivning |
|---|---|
| FRE-BAS-012 Changing a verified value in the Entity Configuration | Assert that an Entity cannot change a verified value by changing its own Entity Configuration. |
| Testfall | Beskrivning |
|---|---|
| FRE-BAS-007 Verifying the Resolved Metadata of registered Entities | Assert that every Entity the FRE publishes meets the BAS requirements, so that the registration, seen as a black box, has admitted only Entities that meet them. |
| Testfall | Beskrivning |
|---|---|
| FRE-BAS-004 Verifying language-tagged values | Assert that the Federation Registration Entity assigns a value without a language tag, holding the Swedish value, for human-readable parameters, so that implementations without language tag support can use them. |
| FRE-BAS-005 Verifying that the FRE sets no other values | Assert that the Federation Registration Entity only sets the values that [BAS.Metadata] assigns to it, since all other assigned or constrained values are controlled by the Federation Operator through the Trust Anchor. |
| Testfall | Beskrivning |
|---|---|
| FRE-BAS-001 Verifying the federation keys against the BAS rules | Assert that the FRE's Federation Entity Keys meet the requirements that apply to them in BAS. [BAS.Security] does not apply to Federation Entity Keys. For them, Section 9 of [BAS.Rules] makes Section 6 of [OIDC.Sweden.Federation] apply. |
| FRE-BAS-002 TLS configuration | Assert that all FRE endpoints, and any hosted Entity Configurations, are protected by TLS according to the federation's security requirements. |
Alla testfall för Federation Resolver: resolver_overview.md.
| Testfall | Beskrivning |
|---|---|
| RES-BAS-007 Entities that break requirements the policy cannot express | Find out how the resolver handles metadata that breaks BAS requirements that the policy cannot express. Peers MUST NOT use Resolved Metadata that breaks the issuer or resource binding. How a peer acts on other deviations is left to the peer. |
| Testfall | Beskrivning |
|---|---|
| RES-BAS-004 Organization parameters in Resolved Metadata | Assert that the resolver delivers the verified organization values that the Federation Registration Entity has set, which is the primary purpose of BAS metadata. |
| RES-BAS-002 Resolved Metadata of an Authorization Server | Assert that the resolver applies the BAS policy to an Authorization Server, so that peers only see the client authentication method and algorithms that BAS permits, while grant types that the Authorization Server supports outside BAS remain visible. |
| RES-BAS-003 Resolved Metadata of a Client | Assert that the resolver applies the BAS policy and the values set by the Federation Registration Entity to a Client. |
| Testfall | Beskrivning |
|---|---|
| RES-BAS-005 Entities that fail the BAS policy | Assert that the resolver applies the essential, superset_of and one_of checks of the BAS policy, for Clients, Authorization Servers and Protected Resources (see RES-OS-025). |
| Testfall | Beskrivning |
|---|---|
| RES-BAS-010 Entity Type not admitted in BAS | Assert that the resolver applies the allowed_entity_types constraint that the Trust Anchor sets, so that peers do not see metadata of Entity Types that BAS does not admit. |
| Testfall | Beskrivning |
|---|---|
| RES-BAS-001 TLS configuration | Assert that the resolve endpoint is protected by TLS according to the federation's security requirements. |