-
Notifications
You must be signed in to change notification settings - Fork 2.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
OIDC settings in docker-compose file throw error in datahub frontend #7733
Comments
with those OIDC settings
|
I'm seeing the same thing in my prod env. Reverting back to 0.10.0 for now |
Commenting out PAC4J_SESSIONSTORE_PROVIDER=PlayCacheSessionStore will fix it though |
Thank you for the workaround, works also for me |
This issue is stale because it has been open for 30 days with no activity. If you believe this is still an issue on the latest DataHub release please leave a comment with the version that you tested it with. If this is a question/discussion please head to https://slack.datahubproject.io. For feature requests please use https://feature-requests.datahubproject.io |
still persists with version 0.10.2 |
This issue is stale because it has been open for 30 days with no activity. If you believe this is still an issue on the latest DataHub release please leave a comment with the version that you tested it with. If this is a question/discussion please head to https://slack.datahubproject.io. For feature requests please use https://feature-requests.datahubproject.io |
This issue was closed because it has been inactive for 30 days since being marked as stale. |
Describe the bug
Using the compose quickstart file with OIDC customization the datahub frontend container throws an error.
To Reproduce
Steps to reproduce the behavior:
docker-compose-without-neo4j.quickstart
python3 -m datahub docker quickstart --quickstart-compose-file docker/quickstart/docker-compose-without-neo4j.quickstart.yml
Expected behavior
Datahub frontend should work as expected. Without OIDC settings the service starts normal.
Desktop (please complete the following information):
Additional context
Here the error log:
The text was updated successfully, but these errors were encountered: