Implement at least one smoke test

[j08lue]

1. Define what to test
2. Prototype in staging environment (easier to access for dev)

Acceptance criteria

• Test is running on staging environment

[lahirujayathilake]

I’d like to propose a set of automated smoke tests for our veda‑keycloak deployment. The idea is to add a lightweight, Python‑based test suite that runs as part of our GitHub workflows immediately after deployment. The main goals of these tests would be to quickly validate that our Keycloak instance is healthy and its most critical functionalities are working as expected. Specifically, the tests would cover

Health Check
Verify that the Keycloak server is up and responding by hitting the health endpoints (e.g. /health/live).

Authentication & Token Issuance
Ensure that valid test credentials yield a proper access token from the token endpoint (/realms/{realm}/protocol/openid-connect/token), and that error responses are correctly returned when using invalid credentials.

User Details Retrieval
Test the API/service logic that fetches user details (covering use case in issue #28) by simulating a call and validating that the returned user model has the expected attributes.

Realm and Client Details Retrieval
Validate that the endpoints for obtaining realm and client details work correctly, returning the right metadata and configurations.

Provider & Configuration Verification
Confirm that our custom providers and related configurations are loaded and operational

Console Accessibility
Check that the Admin and Account consoles are accessible and render correctly. Even a simple HTTP status check and a content verification (like confirming expected title text) would be enough

These tests will be simple, quick “happy-path” checks, not full regression tests. The plan is to write them in Python using libraries like requests and pytest, and trigger them through GitHub workflows so that any major failure immediately stops the pipeline. This way, we catch critical issues early and ensure only stable builds move forward for deeper testing.

Issues created

• Functional Smoke Test: User Authentication & Token Issuance #57
• Functional Smoke Test: Health Check Endpoint #58
• Functional Smoke Test: User Details Retrieval #59
• Functional Smoke Test: Realm Details Retrieval #60
• Functional Smoke Test: Client Details Retrieval #61
• Functional Smoke Test: Provider & Configuration Verification #62
• Functional Smoke Test: Admin Console Accessibility #63
• Functional Smoke Test: Account Console Accessibility #64
• Functional Smoke Test: Secure HTTPS & Certificate Validation #65
• Functional Smoke Test: Client Registration & Configuration Flow #66

[smohiudd]

This work is covered in this epic in Data Services: #87