-
Notifications
You must be signed in to change notification settings - Fork 6
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
OpenUnison Server error when forward-auth0 requests access token #97
Comments
is there a stack trace after this? It would start with "Sendnig JSON Error"? Also, what verion of the helm charts are you on? |
hello, we're using orchestra-login-portal-argocd via the ArgoCD Application Object - version: 2.3.38 there's no stack trace, but here's fuller log context before and after:
here's the OU config:
|
nothing stands out. it's odd that there's no error in the logs. i've never used auth0 forward, so i'll try to get it up and running and see if i can reproduce |
If you can email me directly, we can easily spin up a full temporary environment with everything in place and provide you access.
From: Marc Boorshtein ***@***.***>
Sent: Tuesday, January 9, 2024 3:40 PM
To: OpenUnison/openunison-k8s ***@***.***>
Cc: plcarterco ***@***.***>; Author ***@***.***>
Subject: Re: [OpenUnison/openunison-k8s] OpenUnison Server error when forward-auth0 requests access token (Issue #97)
nothing stands out. it's odd that there's no error in the logs. i've never used auth0 forward, so i'll try to get it up and running and see if i can reproduce
—
Reply to this email directly, view it on GitHub<#97 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AEWCXAUJ3YURTSL5WKSUKALYNXBMJAVCNFSM6AAAAABBTSXDKCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQOBTHEYTENZQGE>.
You are receiving this because you authored the thread.Message ID: ***@***.******@***.***>>
|
Thank you for the offer, but we reserve direct interaction for customers with support contracts, as we don't produce any closed source or "enterprise" editions that require licensing. If you're interested in a support contract, please reach out at https://www.tremolosecurity.com/contact/contact-us. That said, I put together a debug build of 1.0.38 for you (the same version as is running per your helm chart) - docker.io/tremolosecurity/openunison-k8s-debug:1.0.38 This should have the build number |
Completely understand, and thank you for the debug build. We'll try it out and let you know. |
Hello,
Background
we've been using Openunison successfully in regards to k8s dashbard, grafana, argocd, etc.
we also successfully used forward-auth0 (not to be confused with traefik-forward-auth) for authentication against Auth0 as idp
we're now trying to have forward-auth0 utilize Openunison (via Application CR) as idp within the cluster.
Issue
Authentication is successful. But the forward-auth0 access token request to openunison fails with OpenUnison server error.
We were wondering if you all had encountered similar before or had any thoughts or advice. (We couldn't determine the mechanism to increase Opeunison logging level.)
OpenUnison log entries:
[2024-01-09 18:07:48,570][XNIO-1 task-5] INFO AccessLog - [AzSuccess] - forward-auth - https://k8sou.athens-aks.patb68.REDACTED.ai/auth/idp/forward-auth/completefed - uid=patrickx-64-xneosavant.ai,ou=shadow,o=Tremolo - NONE [10.244.0.26] - [f80611c3db9a5fff7039260ae062fa712855a0cde]
[2024-01-09 18:07:48,627][XNIO-1 task-5] INFO AccessLog - [Error] - forward-auth - https://k8sou.athens-aks.patb68.REDACTED.ai/auth/idp/forward-auth/token - cn=none - NONE [10.244.0.26] - [f8f6134e320a1bdfd6713491ccf6a63827721dbb3]
forward-auth0 log entires:
2024-01-09 18:07:47.304 INFO 1 --- [nio-8080-exec-7] d.f.infrastructure.auth0.Auth0Service : AuthorizationCodeExchange: code=LZK5rqNIAAD/xSkrmfvYzGAabMDcV2sSHrQBQ/MacxgYzb/vk3aSykqqoH6f2vX07wl86dZCDSsn+/d+NFNQpS2sfy00zVX/8/TPCQ3leyczqgI0LmiafzylYEZmO7/2B2wOpurQ4h6bVZKOitrwM+L0zaTiFmjFrkXtZTXyZEbGIbPXeASGYoOq5Acc5nCXzhLC7pgVlmYfsouKCdTD+hSvpmnGaiArvNAIo+K/uKR2S/pNT3rIFArE9KMBwvlR1CDPD4XGUyeNZmTsji8ukmLIF+AuWc/0QtOO3M1hpas9PAfMKuUX2ns+E4eyKkbQ6rUT9SVV8BwfOE7V3olA5d8ARp4BKd15HakkghTR2cPuEfRL88K+ENGyxnzHTTgxsUWPtOH4dSvPkCjbJwQiVzYa2T4RJ1At00kKIxIQqXjoWuMnG2kUlO9pm5AkjiN2Ct1Df6T+5YKHFTvJ7fvNMm1c2rKgJ1/nOfjUccUegrXGixK7qrEHhLexjIbOPs6UOkTB1Ze0HiZHOUYmM7l1juWGyl09zoEkX1RnUW6kaGM1k/2XI+ryM9Nels26395bNKgzCSHa7RE4xBQW3MmQ2d3zcgCGzCX08pwQy05Wnka1pZp0AFsvEqJGTGfhuuamx2HOy5+QEYxsZIXrPTs+8nfS0ccN9TjkA3qIVog299FdQu1ZBptPd7P1+oAu44uz8ZiaHt5yYk/TnCXva7VvXu7MvNW9klnHqdPNnuc91GhOluSWtAhfidnAkOpVydI0KgjC99NBONnNDwpVfxV3f1vvbK2r7KzhvzOf/vwH
2024-01-09 18:07:48.030 ERROR 1 --- [nio-8080-exec-7] d.f.i.e.ServerFaultExceptionMapper : ServerFaultExceptionMapper.toResponse: error=JSONObject["error_description"] not found.
Openunison Application CR configuration
The text was updated successfully, but these errors were encountered: