https://datahubproject.io logo
Join Slack
Powered by
Hi everyone!! Currently, I am testing OIDC integra...
# troubleshoot
n
Hi everyone!! Currently, I am testing OIDC integration locally. I used Google Authentication and it was possible to log in. However, when logging out, error occurs and the user is redirected to the original page (http://localhost:9002) without logging out. Post error messages and settings. Please help me. I am using datahub:v0.8.41 Error Message:
Copy code
datahub-frontend-react    | 08:23:23 [application-akka.actor.default-dispatcher-35] ERROR auth.sso.oidc.OidcCallbackLogic - Unable to renew the session. The session store may not support this feature
datahub/docker/datahub-frontend/env/docker.env:
Copy code
AUTH_OIDC_ENABLED=true
AUTH_OIDC_CLIENT_ID=my-client-id
AUTH_OIDC_CLIENT_SECRET=my-client-secret
AUTH_OIDC_DISCOVERY_URI=<https://accounts.google.com/.well-known/openid-configuration>
AUTH_OIDC_BASE_URL=<http://localhost:9002>

AUTH_OIDC_SCOPE=openid profile email
AUTH_OIDC_USER_NAME_CLAIM=email
AUTH_OIDC_USER_NAME_CLAIM_REGEX=([^@]+)
docker-compose:
Copy code
docker-compose -p datahub -f docker-compose-without-neo4j.yml -f docker-compose-without-neo4j.override.yml up
plus1 2
i
Hello Seong, Is the error that you are seeing similar to the one reported here: https://github.com/datahub-project/datahub/issues/4854 ? If yes, a fix has been merged and will be released in the coming days. Alternatively you can use a specific commit version of datahub rather than the oficial release version (think of it like a nightly release) and test the solution.
n
@incalculable-ocean-74010 Thank you for answer me. I tried the committed version [f6736bf] but it still gives the same error. Currently, the only way to log out is to delete the cookie.
i
Please try latest image
If you continue having issues, please share the gms and frontend container logs
n
@incalculable-ocean-74010 I've checked with the head version and it works great. thank you
Hi, @incalculable-ocean-74010 obviously the logout went well, but when I deleted the cookie and tried again, the same issue occurred again. • datahub-frontend-react
Copy code
datahub-frontend-react    | 06:29:59 [application-akka.actor.default-dispatcher-47] ERROR auth.sso.oidc.OidcCallbackLogic - Unable to renew the session. The session store may not support this feature
• datahub-gms
Copy code
datahub-gms               | 06:29:59.877 [qtp1830908236-31] INFO  c.l.m.r.entity.EntityResource:139 - GET urn:li:corpuser:mungiyo
datahub-gms               | 06:29:59.880 [pool-11-thread-1] INFO  c.l.m.filter.RestliLoggingFilter:55 - GET /entities/urn%3Ali%3Acorpuser%3Amungiyo - get - 200 - 4ms
datahub-gms               | 06:29:59.886 [qtp1830908236-40] INFO  c.l.m.r.entity.AspectResource:126 - INGEST PROPOSAL proposal: {aspectName=corpUserStatus, entityUrn=urn:li:corpuser:mungiyo, entityType=corpuser, changeType=UPSERT, aspect={contentType=application/json, value=ByteString(length=100,bytes=7b227374...38337d7d)}}
datahub-gms               | 06:29:59.900 [pool-11-thread-1] INFO  c.l.m.filter.RestliLoggingFilter:55 - POST /aspects?action=ingestProposal - ingestProposal - 200 - 14ms
datahub-gms               | 06:30:00.319 [pool-11-thread-1] INFO  c.l.m.filter.RestliLoggingFilter:55 - GET /entitiesV2?ids=List(urn%3Ali%3Acorpuser%3Amungiyo) - batchGet - 200 - 5ms
datahub-gms               | 06:30:00.335 [I/O dispatcher 1] INFO  c.l.m.k.e.ElasticsearchConnector:41 - Successfully feeded bulk request. Number of events: 1 Took time ms: -1
datahub-gms               | 06:30:00.801 [I/O dispatcher 1] INFO  c.l.m.s.e.update.BulkListener:28 - Successfully fed bulk request. Number of events: 2 Took time ms: -1
s
@narrow-apple-60403 did you find any solutions for this ? I'm having the same problem with the 
head
image
b
same issue here!
n
I haven't solved it yet. 🥲
i
Hello, I believe this was fixed since, can you try the latest version of datahub?
b
@incalculable-ocean-74010 Hi, Should I just upgrade the frontend(or all components)? Deployed with helm. Solved proplem. i updated application version 0.8.4 to 0.9.4, No more error log output. Thanks.
Open in Slack
PreviousNext
Powered by