ACI & Websocket - Didn't switch protocols?

Harish.Kamath — Wed, 11 Jan 2017 12:16:48 GMT

Hello,

I am trying to open a websocket connection to APIC Controller that results into an exception with "Didn't switch protocols". I am using Jetty implementation for Java websocket.

The websocket URL is of the form "wss://<URL>/socket<APIC-Cookie>"

This result is observed if I had received APIC-Cookie along with APIC-Challenge during login request i.e., usage of "?gui-token-request=yes". The websocket connection succeeds if APIC-Challenge was not requested but as you know subscriptions requests require APIC-Challenge to be specified.

Any experiences ?

Thanks,

-Harish Kamath.

Re: ACI & Websocket - Didn't switch protocols?

Ravu al Hemio — Sat, 10 Apr 2021 15:19:08 GMT

I have run into what appears to be the same issue: if I call api/aaaLogin.json including the gui-token-request=yes parameter, I can no longer open a WebSocket connection (I receive a 404 error instead of the 101 success response code).

Is there a way to pass the APIC-challenge when creating the WebSocket or do I have to remove the gui-token-request=yes parameter to aaaLogin?

(This is an external application, so I assume api/requestAppToken.json is not an option.)

topic ACI & Websocket - Didn't switch protocols? in Controllers

ACI & Websocket - Didn't switch protocols?

Re: ACI & Websocket - Didn't switch protocols?