From ce2a83561137cf258ddb51d90df53251c8d20c8e Mon Sep 17 00:00:00 2001 From: Michiel Kodde Date: Thu, 8 Feb 2024 15:51:03 +0100 Subject: [PATCH] Enable FGA use cases --- stepup/tests/behat/features/fga-use-case-a.feature | 1 - stepup/tests/behat/features/fga-use-case-b.feature | 1 - stepup/tests/behat/features/fga-use-case-c.feature | 8 ++++---- stepup/tests/behat/features/fga-use-case-d.feature | 1 - stepup/tests/behat/features/fga-use-case-e.feature | 1 - stepup/tests/behat/features/fga-use-case-f.feature | 1 - 6 files changed, 4 insertions(+), 9 deletions(-) diff --git a/stepup/tests/behat/features/fga-use-case-a.feature b/stepup/tests/behat/features/fga-use-case-a.feature index 4bf0234..feeac55 100644 --- a/stepup/tests/behat/features/fga-use-case-a.feature +++ b/stepup/tests/behat/features/fga-use-case-a.feature @@ -1,4 +1,3 @@ -@SKIP Feature: Use case A: Institutions with few (10-20) users using a third party vetting service For institutions with few users that are using Stepup, for which setting up and maintaining a local vetting structure is relatively expensive, we want to allow a third party to do the vetting whereby the RA's diff --git a/stepup/tests/behat/features/fga-use-case-b.feature b/stepup/tests/behat/features/fga-use-case-b.feature index 9a3cd36..d79f447 100644 --- a/stepup/tests/behat/features/fga-use-case-b.feature +++ b/stepup/tests/behat/features/fga-use-case-b.feature @@ -1,4 +1,3 @@ -@SKIP Feature: Use case B: Institutions sharing vetting locations Allow users from institutions that cannot easily visit the vetting location at the institution, e.g. because they work remotely or abroad, to use the RA services of another institution that is closer to their location. By diff --git a/stepup/tests/behat/features/fga-use-case-c.feature b/stepup/tests/behat/features/fga-use-case-c.feature index eb57441..69cac67 100644 --- a/stepup/tests/behat/features/fga-use-case-c.feature +++ b/stepup/tests/behat/features/fga-use-case-c.feature @@ -53,17 +53,17 @@ Feature: Use case C: Closely cooperating institutions And a user "RAA institution D" identified by "urn:collab:person:institution-d.example.com:joe-d-raa" from institution "institution-d.example.com" And the user "urn:collab:person:institution-d.example.com:joe-d-raa" has a vetted "yubikey" with identifier "00000005" And the user "urn:collab:person:institution-d.example.com:joe-d-raa" has the role "raa" for institution "institution-d.example.com" - And a user "Jane Jackson" identified by "urn:collab:person:institution-a.example.com:jane-a1" from institution "institution-a.example.com" + And a user "jane-a1" identified by "urn:collab:person:institution-a.example.com:jane-a1" from institution "institution-a.example.com" And the user "urn:collab:person:institution-a.example.com:jane-a1" has a vetted "yubikey" with identifier "00000006" - And a user "Joe Satriani" identified by "urn:collab:person:institution-d.example.com:joe-d1" from institution "institution-d.example.com" + And a user "joe-d1" identified by "urn:collab:person:institution-d.example.com:joe-d1" from institution "institution-d.example.com" And the user "urn:collab:person:institution-d.example.com:joe-d1" has a vetted "yubikey" with identifier "00000007" Scenario: The institution A RAA can promote identities from institution D Given I am logged in into the ra portal as "joe-a-raa" with a "yubikey" token When I visit the RA promotion page - Then I change the role of "Joe Satriani" to become "RA" for institution "institution-d.example.com" + Then I change the role of "joe-d1" to become "RA" for institution "institution-d.example.com" Scenario: The institution D RAA can promote identities from institution A Given I am logged in into the ra portal as "joe-d-raa" with a "yubikey" token When I visit the RA promotion page - Then I change the role of "Jane Jackson" to become "RA" for institution "institution-a.example.com" + Then I change the role of "jane-a1" to become "RA" for institution "institution-a.example.com" diff --git a/stepup/tests/behat/features/fga-use-case-d.feature b/stepup/tests/behat/features/fga-use-case-d.feature index 5e0a5e1..06b85cc 100644 --- a/stepup/tests/behat/features/fga-use-case-d.feature +++ b/stepup/tests/behat/features/fga-use-case-d.feature @@ -1,4 +1,3 @@ -@SKIP Feature: Use case D: Vetting users from a guest IdP Allow users from a "guest" IdP (i.e. an IdP for users that do not have a relation with an institution that warrants adding them to the institutional IdP) to be vetted. The RA(A)s to do this will necessarily need to belong to diff --git a/stepup/tests/behat/features/fga-use-case-e.feature b/stepup/tests/behat/features/fga-use-case-e.feature index edba74c..eac0893 100644 --- a/stepup/tests/behat/features/fga-use-case-e.feature +++ b/stepup/tests/behat/features/fga-use-case-e.feature @@ -1,4 +1,3 @@ -@SKIP Feature: Use case E: Institution that uses multiple SHOs An institution IdP that issues multiple SHOs, e.g. institution.org and some-related-part.institution.org. From the perspective of Stepup these would currently become multiple institutions, which each have and manage their own RA(A)s. diff --git a/stepup/tests/behat/features/fga-use-case-f.feature b/stepup/tests/behat/features/fga-use-case-f.feature index a4322f8..8f573db 100644 --- a/stepup/tests/behat/features/fga-use-case-f.feature +++ b/stepup/tests/behat/features/fga-use-case-f.feature @@ -1,4 +1,3 @@ -@SKIP Feature: Use case F: An institution that manages Stepup for a (a group of) sister and/or daughter institutions An institution that manages Stepup for (a group of) sister and/or daughter institutions. This use-case appears similar to use-case A. The differences lie in the relation that the managing institution has with the institutions being