-
Notifications
You must be signed in to change notification settings - Fork 443
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
oauth/kratos/self-service/login/browser response 400 #1120
Comments
I had the same problem. Navigate to dev.withpixie.dev requests https://work.dev.withpixie.dev/api/authorized and return "failed to fetch token - unauthenticated". Meanwhile,click login ,then response 401, cannot jump to the login page |
…anager (#1188) Summary: Add `access-tls-socket-fd-via-syscall` feature flag to cloud config manager This feature flag will be used to opt internal clusters into the new tls tracing implementation developed in #1120. We may want a more sophisticated toggle for gradually opting in more clusters, but this will suffice for the initial set of testing (validating some hand picked clusters). Relevant Issues: #692 Type of change: /kind feature Test Plan: Verified the following: - [x] Deploying a new pixie install without launch darkly credentials results in the default, `false`, value ([P354](https://phab.corp.pixielabs.ai/P354)) - [x] Deploying a new pixie install with a cloud with launch darkly credentials results in a `true` value ([P355](https://phab.corp.pixielabs.ai/P355)) Signed-off-by: Dom Del Nano <[email protected]>
…anager (pixie-io#1188) Summary: Add `access-tls-socket-fd-via-syscall` feature flag to cloud config manager This feature flag will be used to opt internal clusters into the new tls tracing implementation developed in pixie-io#1120. We may want a more sophisticated toggle for gradually opting in more clusters, but this will suffice for the initial set of testing (validating some hand picked clusters). Relevant Issues: pixie-io#692 Type of change: /kind feature Test Plan: Verified the following: - [x] Deploying a new pixie install without launch darkly credentials results in the default, `false`, value ([P354](https://phab.corp.pixielabs.ai/P354)) - [x] Deploying a new pixie install with a cloud with launch darkly credentials results in a `true` value ([P355](https://phab.corp.pixielabs.ai/P355)) Signed-off-by: Dom Del Nano <[email protected]>
I also encountered the same problem, about the response 400 error, did you find the reason for this part? |
@dragonTour @yantingqiu I have the same question, do you have fixed it? |
I have the same problem. Did you manage to solve it? |
Hello! Did you manage to solve the problem? |
Hey! I also encountered the same problem. |
hi, I used this release and everything worked: release/cloud/prod/1683050579
пн, 30 окт. 2023 г., 14:02 yuval0499 ***@***.***>:
… Hey! I also encountered the same problem.
Any progress to solve this behavior ?
—
Reply to this email directly, view it on GitHub
<#1120 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ARWE3RIXXHJOQM7JGQPBAK3YB6CMJAVCNFSM6AAAAAAWLYTYIGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTOOBUHE2TCOBSHE>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
@aakosarev @yuval0499 @tanjunchen edit kratos deployment: oryd/kratos:v0.10.1 to oryd/kratos:latest |
**Describe **
all pods are ready
click login ,then response 400, cannot jump to the login page
cloud version: latest
The text was updated successfully, but these errors were encountered: