KEYCLOAK-13319 Use newest WebDriver/Selenium for the WebAuthn testing#8534
KEYCLOAK-13319 Use newest WebDriver/Selenium for the WebAuthn testing#8534mposolda merged 4 commits intokeycloak:mainfrom
Conversation
1151967 to
dc56d09
Compare
|
I need to fix some additional tests. |
dc56d09 to
0df34a4
Compare
|
I edited test cases and this PR is ready to review. |
mposolda
left a comment
There was a problem hiding this comment.
@mabartos This is great work! Thanks for it! I have few more concerns and added some additional comments:
-
Does this PR work in the pipeline already?
-
Any update for HOW-TO-RUN.md ? Or is it expected that this does not work yet in the community? HOW-TO-RUN.md has some notes related to WebAuthn, which are surely not valid anymore with these changes, so some update to this document will be nice in this PR.
-
It seems WebAuthnRegisterAndLoginTest tests only single configuration of WebAuthn authenticator? Is it a plan to extend this to run with multiple various WebAuthn configurations (EG. BLE, NFC and others...). Or is it a plan to do it as a follow-up?
|
@mposolda Thank you very much for your comments!
|
No, I did not yet tried it. I guess that if it runs in pipeline, it can be considered that it works? One thing, which I am not sure, is using these credentials to download your privately build packages. I don't have much experience with this approach and not 100% sure whether it is good practice. However if @miquelsi or @pdrozd are fine with this approach and approves this PR, I am fine as well :-)
That will be nice, Thanks!
Will it be useful for you to have this PR merged to be able to continue with the follow-up work? From my point of view, this PR is ready to go once:
I consider that other things (HOW-TO-RUN update, commented SigningInTest, follow-up test tasks etc) can be done as a follow-up as long as there are JIRA for them in the "WebAuthn testing epic" . |
|
@mposolda Thanks! I'm trying to properly execute those tests in pipeline, which ensures us that everything works correctly. I'm still investigate it and then I'll notify you about it. |
|
Selenium 4 is now officially available. Apparently this version is required if we want to test WebAuthn LoginLess authentication scenarios (resident key and user verification set to 'required'). I'll add the tests for #7860 as soon as this is merged |
|
@vanrar68 I'm working on a WebAuthn testsuite, but it seems, there won't be any other major changes in this PR, so you can follow up on this PR. Moreover, probably we'll be able to properly execute those tests in a pipeline soon, therefore this PR will be merged soon. |
0df34a4 to
a3f8e7d
Compare
|
@mposolda Pipeline tests passed: https://keycloak-jenkins.com/job/universal-test-pipeline-server/1033/console |
|
The GH actions failures are not related to this PR. |
|
Hi! it seems webauthn tests are failing on Windows platform because chrome 64bits webdriver are not available on remote storage (no matter which version of chrome is installed on the machine performing the tests). Google seems to publish 32bits driver exclusively for Windows platform. It used to work nicely with old webauthn test framework though:
|
I managed to make the webauthn tests work on Windows platform by adding the -Dwebdriver.chrome.driver=C:/path/to/chromedriver.exe option to the maven command line. Could be interesting to add to the HOW-TO-RUN.md |
|
@vanrar68 Thanks for your information. I'll create a new issue for Arquillian Drone and note the workaround to the HOW-TO-RUN.md |
|
@vanrar68 The issue for that was created. See arquillian/arquillian-extension-drone#300 |
JIRA: KEYCLOAK-13319
This is a prototype for the WebAuthn testing, which use features from Selenium 4. Virtual Authenticators work as expected in the WebAuthn tests.
@pskopek @Pepo48 Could you please take a look at it?