Is your feature request related to a problem? Please describe.
The current cookie/batman flow is nonstandard and the sync routines are not entirely reliable.
Describe the solution you'd like
ElasticSearch and Kibana actually do support external OpenID Connect provider:
This will require
- extra docker-compose and/or yaml config for ElasticSearch and Kibana,
- reconfiguring ElasticSearch client in Seacat Auth, possibly a separate one for Kibana,
- syncing of roles, role mappings and Kibana spaces. This however should not be as problematic as the syncing of users.
This approach needs to be explored, there may be obstacles.
Is your feature request related to a problem? Please describe.
The current cookie/batman flow is nonstandard and the sync routines are not entirely reliable.
Describe the solution you'd like
ElasticSearch and Kibana actually do support external OpenID Connect provider:
This will require
This approach needs to be explored, there may be obstacles.