Add auth file just for login purpose

[gouyang]

Fixes #2015

Signed-off-by: Guohua Ouyang [email protected]

[openshift-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: gouyang
To complete the pull request process, please assign alecmerdler
You can assign the PR to them by writing /assign @alecmerdler in a comment when ready.

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

Details

Needs approval from an approver in each of these files:

• frontend/OWNERS

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

[spadgett]

/assign @alecmerdler @TheRealJon

[TheRealJon]

I don't know if this is what we want. We created the login scenario to more fully exercise the login workflow. This simple auth test is more or less the same as what we moved away from. @spadgett what do you think?

[gouyang]

@TheRealJon @spadgett As kubevirt tests are going to move here, the current login scenario which has lots of login test seems no necessary for it, so I'm trying to create a simple auth scenario for all tests.

[TheRealJon]

This will break our current login test. If the IDP that we create is still in flight when the login scenario runs, this condition will be false, meaning the IDP selection will be skipped, and we will attempt to login using test user credentials against the kubeadmin idp.

[TheRealJon]

@gouyang I think we'll need some input from @spadgett on this. The changes to protractor.conf.ts remove our existing login test from all of the suites, which I'm pretty sure isn't what we want.

[gouyang]

@gouyang I think we'll need some input from @spadgett on this. The changes to protractor.conf.ts remove our existing login test from all of the suites, which I'm pretty sure isn't what we want.

The login scenario has a single test suite login, so I think we don't need to worry about it.

Let's wait for @spadgett inputs.