authelia/test/features/forward-headers.feature

Feature: User and groups headers are correctly forwarded to backend
  @need-authenticated-user-john
  Scenario: Custom-Forwarded-User and Custom-Forwarded-Groups are correctly forwarded to protected backend
    When I visit "https://public.example.com:8080/headers"
    Then I see header "Custom-Forwarded-User" set to "john"
    Then I see header "Custom-Forwarded-Groups" set to "dev,admin"

  Scenario: Custom-Forwarded-User and Custom-Forwarded-Groups are correctly forwarded to protected backend when basic auth is used
    When I request "https://single_factor.example.com:8080/headers" with username "john" and password "password" using basic authentication
    Then I received header "Custom-Forwarded-User" set to "john"
    And I received header "Custom-Forwarded-Groups" set to "dev,admin"
Add tests on headers forwarded to backend Ensure Remote-User and Remote-Groups can be forwarded to the backend app. 2017-10-14 20:04:43 +07:00			`Feature: User and groups headers are correctly forwarded to backend`
			`@need-authenticated-user-john`
			`Scenario: Custom-Forwarded-User and Custom-Forwarded-Groups are correctly forwarded to protected backend`
Change domain from test.local to example.com Warning: you will need to update your /etc/hosts to take this change into account for the example environment to work. 2017-11-03 03:34:07 +07:00			`When I visit "https://public.example.com:8080/headers"`
Add tests on headers forwarded to backend Ensure Remote-User and Remote-Groups can be forwarded to the backend app. 2017-10-14 20:04:43 +07:00			`Then I see header "Custom-Forwarded-User" set to "john"`
			`Then I see header "Custom-Forwarded-Groups" set to "dev,admin"`
Add basic authorization support for single-factor protected endpoints One can now access a service using the basic authorization mechanism. Note the service must not be protected by 2 factors. The Remote-User and Remote-Groups are forwarded from Authelia like any browser authentication. 2017-11-02 01:23:45 +07:00
			`Scenario: Custom-Forwarded-User and Custom-Forwarded-Groups are correctly forwarded to protected backend when basic auth is used`
Change domain from test.local to example.com Warning: you will need to update your /etc/hosts to take this change into account for the example environment to work. 2017-11-03 03:34:07 +07:00			`When I request "https://single_factor.example.com:8080/headers" with username "john" and password "password" using basic authentication`
Add basic authorization support for single-factor protected endpoints One can now access a service using the basic authorization mechanism. Note the service must not be protected by 2 factors. The Remote-User and Remote-Groups are forwarded from Authelia like any browser authentication. 2017-11-02 01:23:45 +07:00			`Then I received header "Custom-Forwarded-User" set to "john"`
			`And I received header "Custom-Forwarded-Groups" set to "dev,admin"`