This repository has been archived by the owner on Dec 18, 2018. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 446
Enhancements to negotiate response url #1947
Labels
Milestone
Comments
Triage: We'll need to discuss this. |
davidfowl
added
status: Needs Design
cost: S
Will take up to 2 days to complete
cost: M
Will take 3 - 5 days to complete
and removed
cost: S
Will take up to 2 days to complete
labels
Apr 12, 2018
Today if websockets is chosen, we skip negotiate, we need to make this an explicit flag instead of using the transport type. |
If this flag (SkipNegotiate) is set, we should throw if the Transports flags enum (on the client) is anything other than exactly WebSockets. |
The response will look like: {
"url": "https://myothersignalrapp.foo.net/chat",
"accessToken": "accessToken"
} |
@davidfowl how about |
Not required, we're going to be just using the access token specified here as is. If it expires, the connection will die and we'll get a new one from the same negotiate endpoint. |
davidfowl
added
SHP: Approved
3 - Done
and removed
shiproom-approved
2 - Working
labels
Apr 18, 2018
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
We want to add 2 things to the negotiate response:
A url that the client connects to for the actual SignalR end point. This is to support scenarios where the main application wants to direct the real time traffic to another server but doesn't want to hard code urls in the client. Negotiate would gain the ability to specify a URL that the client should connect to.
An access token or access token end point. This would automagically get plugged into the client's access token provider when making a request to the above url.
The text was updated successfully, but these errors were encountered: