2021-05-04 22:06:05 +00:00
|
|
|
package suites
|
|
|
|
|
|
|
|
|
|
import (
|
|
|
|
|
"testing"
|
|
|
|
|
|
|
|
|
|
"github.com/stretchr/testify/suite"
|
|
|
|
|
)
|
|
|
|
|
|
|
|
|
|
type OIDCTraefikSuite struct {
|
|
|
|
|
*SeleniumSuite
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
func NewOIDCTraefikSuite() *OIDCTraefikSuite {
|
|
|
|
|
return &OIDCTraefikSuite{SeleniumSuite: new(SeleniumSuite)}
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
func (s *OIDCTraefikSuite) TestOIDCScenario() {
|
|
|
|
|
suite.Run(s.T(), NewOIDCScenario())
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
func TestOIDCTraefikSuite(t *testing.T) {
|
feat(oidc): add additional config options, accurate token times, and refactoring (#1991)
* This gives admins more control over their OIDC installation exposing options that had defaults before. Things like lifespans for authorize codes, access tokens, id tokens, refresh tokens, a option to enable the debug client messages, minimum parameter entropy. It also allows admins to configure the response modes.
* Additionally this records specific values about a users session indicating when they performed a specific authz factor so this is represented in the token accurately.
* Lastly we also implemented a OIDC key manager which calculates the kid for jwk's using the SHA1 digest instead of being static, or more specifically the first 7 chars. As per https://datatracker.ietf.org/doc/html/draft-ietf-jose-json-web-key#section-8.1.1 the kid should not exceed 8 chars. While it's allowed to exceed 8 chars, it must only be done so with a compelling reason, which we do not have.
2021-07-03 23:44:30 +00:00
|
|
|
if testing.Short() {
|
|
|
|
|
t.Skip("skipping suite test in short mode")
|
|
|
|
|
}
|
|
|
|
|
|
2021-05-04 22:06:05 +00:00
|
|
|
suite.Run(t, NewOIDCTraefikSuite())
|
|
|
|
|
}
|
