IdS with WebSockets and Server-Sent Events

[guardrex]

Fixes #17751

Internal Review Topic (links to section)

Brennan ... I'm winging this one even more than usual from the context on the issue. I need help with it ...

• Is this the best spot?
• Are these remarks sufficient/correct?
• Is Caleb's code good to provide?

[BrennanConroy]

I don't think this belongs in Blazor docs as it's specific to using SignalR directly. I would probably put it in the signalr/authn-and-authz doc.

[guardrex]

I'll move it.

Does it warrant a cross-link from the Blazor IdS topic because Caleb said ...

It does not cover the Identity Server case where AddIdentityServerJwt() is used instead, which is the default for Blazor WebAssembly apps scaffolded with authentication.

... implying that this was for a Blazor scenario in his case.

[BrennanConroy]

implying that this was for a Blazor scenario in his case

Right, they were using SignalR in Blazor WASM, and you'll notice that they commented on the SignalR docs because it's a SignalR scenario. The only reason Blazor is mentioned is because the scaffolding for a Blazor app adds IdentityServerJwt by default. Anyone using IdentityServerJwt with SignalR outside of a Blazor app will have a similar issue.

I could see a possible cross-reference in the Blazor-Wasm with SignalR tutorial as a potential "next steps, adding auth" type of thing.

[guardrex]

Seems like it goes in the same section. (I try to avoid unpaired child sections.)

Does this compose well now?

[BrennanConroy]

Should we have subsections for this to make it more obvious that this section is for IdentityServer and the other one is for the built in Jwt auth? Otherwise, looks good

[guardrex]

See if the section naming on the last commit works.

Yes, I think two is good. I just didn't want to add one (unpaired) heading. I try to follow old skool outlining rules and pair sections (and bullets) when possible.

[BrennanConroy]

Another nit: the section about the clients should probably go above the first subsection now?
From "In the JavaScript client, the token can be provided..." to "To support this on the server, additional configuration is required:"