Added keycloak integration test

[ricklambrechts]

I currently have a running keycloak service.

Part of #340

Next things todo:

• Create or import a basic realm
• Create a test script that uses this package and connects to the realm
• Serve the test script
• Create cypress test to check if authentication flow is working

[ricklambrechts]

@azmeuk @DeepDiver1975

First integration test 🎉
Let me know what you think.

Things to improve:

• Import realms/users/clients to Keycloak instead of making them one by one
• Create small application (with something like https://www.slimframework.com/) with multiple endpoints for the different clients
• Add additional test cases

[azmeuk]

Thank you so much for this! ❤️

I am wondering: is cypress needed here?
Wouldn't PHP testcases with requests against keycloak in PHPUnit be enough? I don't really know cypress, so I fear this would make an additional difficulty for contributors.
What do you think?

[azmeuk]

Why redirecting the outputs to /dev/null? When everything is fine you surely don't need it, but this might be useful to debug when things are broken.

[ricklambrechts]

We could indeed save the output as a kind of debug log., thanks.

[ricklambrechts]

Thanks!

I think that multiple integration tests are really usefull to check if the package can load the openid-configuration correctly at first, than a user really can login at the identity provider and after that check if the application can load the user info endpoint.

The package redirects the user to the login screen of the identity provider, after successful login the user is redirected to the sample code where the user name is shown. With Cypress, selenium or another tools we can fully test this flow.

[DeepDiver1975]

I have to agree with @azmeuk - adding cypress here is a bit of an overkill.

From my understanding we don't need to test full flows but only parts of it - meaning dedicated calls to keycloak and assert the response.