CloseOnAuthenticationExpiration Does not exist in class properties
See original GitHub issuedocument:
https://docs.microsoft.com/en-us/dotnet/api/microsoft.aspnetcore.http.connections.httpconnectiondispatcheroptions.closeonauthenticationexpiration?view=aspnetcore-6.0
As this document says, there should be a boolean property as CloseOnAuthenticationExpiration
on the HttpConnectionDispatcherOptions
class which there is not according to definition. Does this property removed from the class and what is the reference?
Issue Analytics
- State:
- Created 2 years ago
- Comments:6 (5 by maintainers)
Top Results From Across the Web
ASP.NET Core SignalR configuration
CloseOnAuthenticationExpiration, false, Set this option to enable authentication expiration tracking which will close connections when a ...
Read more >Authentication and authorization in ASP.NET Core SignalR
In a hub, authentication data can be accessed from the xref:Microsoft.AspNetCore.SignalR.HubConnectionContext.User?displayProperty=nameWithType property.
Read more >Authentication and authorization in ASP.NET Core SignalR
This validation is done only when the connection is established. During the life of the connection, the server doesn't automatically revalidate ...
Read more >Getting the public properties of a class in .NET core
I notice that .NET core doesn't allow myObj.GetType().GetProperties() as no GetProperties method exists. Is there another way to obtain the ...
Read more >SignalR JavaScript client: Updating query parameters ...
All this works fine as long as the ticket does not expire. In the client code, we want to periodically renew the ticket....
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
@halter73 perhaps they’re on an earlier version. The API appears to have been introduced in 6.0
Yes. It’s maintained in this repo here.