[MGNLSSO-19] Integration tests with Docker Keycloak and new UI test framework Created: 27/Feb/20  Updated: 24/Sep/20  Resolved: 21/Sep/20

Status: Closed
Project: Single Sign On
Component/s: None
Affects Version/s: None
Fix Version/s: 1.0.2

Type: Task Priority: Neutral
Reporter: Maxime Michel Assignee: Maxime Michel
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
dependency
depends upon MGNLTEST-15 Allow to write custom page objects Closed
depends upon MGNLTEST-1 Attempt to extract the integration te... Closed
depends upon MGNLTEST-28 Run selftests on extracted test frame... Closed
relation
is related to MGNLSSO-30 Refactor the SSO module Closed
Template:
Acceptance criteria:
Empty
Task DoR:
Empty

 Description   

Do a docker-compose setup with Keycloak and Magnolia + the refactored SSO module (using the webapp-wizard).

Then test:

  • make sure the module can handle Keycloak downtime
  • group mappings
  • etc.


 Comments   
Comment by Maxime Michel [ 03/Mar/20 ]

To be able to leverage the new page object based UI test framework nicely (without hacks), this ticket would depend on the two linked tickets.

Comment by Maxime Michel [ 03/Mar/20 ]

https://git.magnolia-cms.com/projects/INTERNAL/repos/sso-openid-connect/commits/a59b1240e9594d68fd8c987a8b7bc74d43000c30 shows what I've done so far:

  • prepare a Magnolia webapp with the module installed (thanks to the webapp-wizard)
  • make Magnolia and Keycloak run in Docker compose
  • configure Magnolia to run the module (jaas.config & authenticationService.yaml)
  • use Keycloak's REST API to create the client, groups, users, etc.

I could get this setup to run, which is a good start. But it would now be time to write tests, for instance:

  • login and logout work
  • Magnolia can recover from Keycloak downtime
  • group mappings are respected
  • etc.
Comment by Maxime Michel [ 31/Mar/20 ]

After REST Assured was suggested to me instead of the full-blown UI test framework (not available at this time), I realized that going through the actual Keycloak login page is actually a requirement here. Authenticating over REST to access a protected web service such as Magnolia might be possible but is not something that is clearly supported, from what I could see.

Therefore, this ticket is on hold until MGNLCE-208 is resolved.

Generated at Mon Feb 12 10:50:20 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.