Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

`failed: HTTP Authentication failed; no valid credentials available` logs on my web browser.

See original GitHub issue

Description

Sometimes my Chrome shows a lot of failed: HTTP Authentication failed; no valid credentials available message. Even though I’m using patched Che-server, I suspect it will be reproduced on the vanilla Che.

It looks the similar issue was reported on the another project and fixed there.

Referring to the code tree, it seems they don’t update their token applied.

Reproduction Steps

Should be clarified.

OS and version:

Che nightly build. Multi-user with Keycloak. Possibly all versions of OSes and browsers.

Diagnostics:

app-fd93f77024.js:114795 WebSocket connection to 'wss://che-{censored}/api/websocket?token=eyJhbGciOiJSUzI1NiIsInR5cCIgOiAiSldUIiwia2lkIiA6ICJlMjNGc3kzRlI5dnRUZms3TGlkX1lQOGU0cDNoY0psM20wQTRnckIzNnJJIn0.eyJqdGkiOiJhNWE3YTQyMi1iYjU0LTQxYmItYTk2Yy04NDJjOTdhMjc0YzMiLCJleHAiOjE1NDMwMTg4MzgsIm5iZiI6MCwiaWF0IjoxNTQzMDE4MjM4LCJpc3MiOiJodHRwczovL2tleWNsb2FrLWNhbWluby5jLnBpenphZmFjdG9yeS5qcC9hdXRoL3JlYWxtcy9jaGUiLCJhdWQiOiJjaGUtcHVibGljIiwic3ViIjoiNjNjZTg2MDQtMmViNS00NmIwLWI0MWUtMTdiNjM3NmE5YjliIiwidHlwIjoiQmVhcmVyIiwiYXpwIjoiY2hlLXB1YmxpYyIsIm5vbmNl...ybmFtZSI6ImNyeXB0Y29pbi1qdW5rZXkiLCJnaXZlbl9uYW1lIjoiQ3J5cHRvY29pbiIsImZhbWlseV9uYW1lIjoiSnVua2V5IiwiZW1haWwiOiJjcnlwdGNvaW4uanVua2V5QGdtYWlsLmNvbSJ9.TZ8nJYIaFiKIUhA5hkVCATgvK2YQcxxx-oSPeAWD0pDYD6M1sKamp3hnrvLqw4oleC69FZ2Le26AROct9d-SXZEgb-gzGShlYUlpKxEB35PZlmUbwkBYhssUbeCz-XJ-9mQSnvBhr05mpPp71oh1X5fnU2H0DOdRJzyWZjDiOzMtJW15p79es9hf0ODgjfnknPtYJjv0FsfTRFISIq9kt8Sm5uVn9iFrcxtG5M3Hdshj_TiP6qMKyGzJsvVrmBI8X2JedhWuHqJhwADfG8eourGzJNVzIXg1xEZ3PDxkdvJ8IaovxUnu3niI9SpnrO8mQ1ISjM1Q4CzDJBFSM-2F2Q&clientId=40835350' failed: HTTP Authentication failed; no valid credentials available

Issue Analytics

State:
Created 5 years ago
Comments:9 (6 by maintainers)

Top GitHub Comments

1reaction

che-botcommented, Dec 18, 2019

Issues go stale after 180 days of inactivity. lifecycle/stale issues rot after an additional 7 days of inactivity and eventually close.

Mark the issue as fresh with /remove-lifecycle stale in a new comment.

If this issue is safe to close now please do so.

Moderators: Add lifecycle/frozen label to avoid stale mode.

0reactions

i524304commented, Aug 11, 2020

Hi @monaka

I am also getting same error and cognitive services speech option is not working for me. While using cognitive servcices speech options for web chat using this sample (https://github.com/microsoft/BotFramework-Samples/blob/master/docs-samples/web-chat-speech/index.html) i am getting this web sockect connection error

Error : WebSocket connection to ‘wss://speech.platform.bing.com/speech/recognition/interactive/cognitiveservices/v1?format=simple&language=en-US&Ocp-Apim-Subscription-Key=xxxxxxxxxxxxxxxxxxxxxxxxx-ConnectionId=2607EB6D18B74798BD56FAA15AE367A0’ failed: HTTP Authentication failed; no valid credentials available

Hope you can help and hoping to hear from you soon.

Kind Regards

Top Results From Across the Web

WebSocket connection failed - HTTP Authentication failed

Hi. It looks like WebSocket works in browser ie, but not in chrome. When i start /episerver i get this error message in...

HTML5 Websocket HTTP Authentication failed; no valid ...

I have implemented this web socket using web API. This code is working fine in my local environment. But it is giving me...

websocket authentication failed; no valid credentials available

I think the issue here is that Chrome cache the old credentials and uses the same while requesting WebSocket endpoint. To confirm this...

aspnet/SignalR - Gitter

Does anyone know why, when authenticating with a token, i connect and authenticate fine running in edge, but get failed: HTTP Authentication failed;...

423609 - Support Windows authentication for WebSocket

I'm getting "HTTP Authentication failed; no valid credentials available". However, other browsers (IE11, Edge, Firefox) in my machine worked fine.