chore(e2e): add RHSSO sub claim resolvers to auth e2e tests

[JessicaJHee]

Description

Adds e2e tests for the oidcSubClaimMatchingKeycloakUserId OIDC auth resolver

• sets this resolver as the default one for RHSSO auth e2e tests

Which issue(s) does this PR fix

• Fixes RHIDP-6322

PR acceptance criteria

Please make sure that the following steps are complete:

• GitHub Actions are completed and successful
• Unit Tests are updated and passing
• E2E Tests are updated and passing
• Documentation is updated if necessary (requirement for new features)
• Add a screenshot if the change is UX/UI related

How to test changes / Special notes to the reviewer

[JessicaJHee]

@albarbaro I did notice that on the first run of RHBK - remove a user from RHDH it fails on this on the first run:

rhdh/e2e-tests/playwright/e2e/authProviders/rhsso-76-provider.spec.ts

Line 609 in 836cc5e

expect(loginSucceded).toContain("Login successful");

But passes on the retry. Any ideas on why this might be?

[JessicaJHee]

/retest

[albarbaro]

@albarbaro I did notice that on the first run of RHBK - remove a user from RHDH it fails on this on the first run:

rhdh/e2e-tests/playwright/e2e/authProviders/rhsso-76-provider.spec.ts

Line 609 in 836cc5e

expect(loginSucceded).toContain("Login successful");

But passes on the retry. Any ideas on why this might be?

I did notice the same recently but I wasn't able to figure it out yet. My guess is this is due to a sync issue after the previous test cases are run, since on retry the users are re-created and the sync happens again, but I haven't verified it yet.

[JessicaJHee]

/retest

[github-actions]

The image is available at:

• quay.io/rhdh-community/rhdh:pr-2451 or
• quay.io/rhdh-community/rhdh:pr-2451-d3e7de9c

[albarbaro]

/lgtm
/approve

[JessicaJHee]

/cherry-pick release-1.5

[openshift-cherrypick-robot]

@JessicaJHee: once the present PR merges, I will cherry-pick it on top of release-1.5 in a new PR and assign it to you.

In response to this:

/cherry-pick release-1.5

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[JessicaJHee]

/retest

[kim-tsao]

/lgtm

[albarbaro]

/lgtm

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: albarbaro, kim-tsao

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• .ibm/OWNERS [albarbaro,kim-tsao]
• e2e-tests/OWNERS [albarbaro,kim-tsao]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[openshift-ci]

New changes are detected. LGTM label has been removed.

[openshift-ci]

@JessicaJHee: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
ci/prow/e2e-tests	a32f80b	link	true	/test e2e-tests

Full PR test history. Your PR dashboard.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.