-
Notifications
You must be signed in to change notification settings - Fork 1
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Enable sfo tests and create the adfs feature
Tests where added to the ADFS and SFO test suites. Covering successfull and failing GSSP and Built in (yubikey) authtentications
- Loading branch information
Showing
4 changed files
with
174 additions
and
15 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,30 @@ | ||
Feature: As an institution that uses ADFS support on the second factor only feature | ||
In order to do ADFS second factor authentications | ||
I must be able to successfully authenticate with my second factor tokens | ||
|
||
Scenario: A user logs in using ADFS parameters | ||
Given a service provider configured for second-factor-only | ||
When I visit the ADFS service provider | ||
And I verify the "yubikey" second factor | ||
Then I am logged on the service provider | ||
|
||
Scenario: A user logs in using ADFS parameters with a gssp token | ||
Given a user "jane-a-ra" identified by "urn:collab:person:institution-a.example.com:jane-a-ra" from institution "institution-a.example.com" with UUID "00000000-0000-4000-8000-000000000001" | ||
And the user "urn:collab:person:institution-a.example.com:jane-a-ra" has a vetted "demo-gssp" with identifier "gssp-identifier123" | ||
And a service provider configured for second-factor-only | ||
When I start an ADFS authentication for "urn:collab:person:institution-a.example.com:jane-a-ra" | ||
And I verify the "demo-gssp" second factor | ||
Then I am logged on the service provider | ||
|
||
Scenario: A user cancels ADFS authn with a gssp token | ||
And a service provider configured for second-factor-only | ||
When I start an ADFS authentication for "urn:collab:person:institution-a.example.com:jane-a-ra" | ||
And I cancel the "demo-gssp" second factor authentication | ||
Then I see an ADFS error at the service provider | ||
|
||
Scenario: A user cancels ADFS authn with a yubikey token | ||
Given a service provider configured for second-factor-only | ||
When I visit the ADFS service provider | ||
And I cancel the "yubikey" second factor authentication | ||
Then I see an ADFS error at the service provider | ||
|
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,12 +1,30 @@ | ||
@SKIP | ||
# Skipped awaiting a fix of the SSP, allowing for SFO authentications | ||
Feature: A user authenticates with a service provider configured for second-factor-only | ||
In order to login on a service provider | ||
As a user | ||
I must verify the second factor without authenticating with an identity provider | ||
|
||
Scenario: A user logs in using SFO | ||
Scenario: A user logs in using SFO using a GSSP token | ||
Given a service provider configured for second-factor-only | ||
When I visit the service provider | ||
And a user "jane-a-ra" identified by "urn:collab:person:institution-a.example.com:jane-a-ra" from institution "institution-a.example.com" with UUID "00000000-0000-4000-8000-000000000001" | ||
And the user "urn:collab:person:institution-a.example.com:jane-a-ra" has a vetted "demo-gssp" with identifier "gssp-identifier123" | ||
When I start an SFO authentication for "urn:collab:person:institution-a.example.com:jane-a-ra" | ||
And I verify the "demo-gssp" second factor | ||
Then I am logged on the service provider | ||
|
||
Scenario: A user cancels SFO authn with a gssp token | ||
And a service provider configured for second-factor-only | ||
When I start an SFO authentication for "urn:collab:person:institution-a.example.com:jane-a-ra" | ||
And I cancel the "demo-gssp" second factor authentication | ||
Then I see an error at the service provider | ||
|
||
Scenario: Admin logs in using SFO using a Yubikey token | ||
Given a service provider configured for second-factor-only | ||
When I start an SFO authentication for "urn:collab:person:dev.openconext.local:admin" | ||
And I verify the "yubikey" second factor | ||
Then I am logged on the service provider | ||
|
||
Scenario: Admin user cancels SFO authn with a Yubikey token | ||
And a service provider configured for second-factor-only | ||
When I start an SFO authentication for "urn:collab:person:dev.openconext.local:admin" | ||
And I cancel the "yubikey" second factor authentication | ||
Then I see an error at the service provider |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters