Describe the pull request
This pull request addresses an issue causing latency and white theme flickering due to problems with next-auth. The fix involves resolving these next-auth issues by rollback to client side session fetching and eliminate the undesirable flickering effect by rolling back the client cache on local storage.
Checklist
[x] I have made the modifications or added tests related to my PR
[x] I have run the tests and linters locally and they pass
[x] I have added/updated the documentation for my RP
Additional context
The latency seams to be when nextauth try to store new session on response cookies. Maybe is a next issue. We put some metadata to the transactions for a better monitoring on Sentry
Show Validation
```
Success! The configuration is valid.
```
Terraform Plan 📖 success
Show Plan
```
kubernetes_config_map.stud42_config: Refreshing state... [id=sandbox/stud42-config]
module.jwtks_service.kubernetes_service.app[0]: Refreshing state... [id=sandbox/jwtks-service]
module.istio.kubectl_manifest.virtual_services["dev-s42-sandbox"]: Refreshing state... [id=/apis/networking.istio.io/v1alpha3/namespaces/sandbox/virtualservices/dev-s42-sandbox]
module.jwtks_service.kubernetes_deployment.app[0]: Refreshing state... [id=sandbox/jwtks-service]
module.jwtks_service.kubernetes_horizontal_pod_autoscaler_v2.app[0]: Refreshing state... [id=sandbox/jwtks-service]
module.jwtks_service.kubernetes_manifest.certificate["grpc-internal"]: Refreshing state...
No changes. Your infrastructure matches the configuration.
Terraform has compared your real infrastructure against your configuration
and found no differences, so no changes are needed.
```
Describe the pull request This pull request addresses an issue causing latency and white theme flickering due to problems with next-auth. The fix involves resolving these next-auth issues by rollback to client side session fetching and eliminate the undesirable flickering effect by rolling back the client cache on local storage.
Checklist
Additional context The latency seams to be when nextauth try to store new session on response cookies. Maybe is a next issue. We put some metadata to the transactions for a better monitoring on Sentry