CQRS.NET  4.0
A lightweight enterprise Function as a Service (FaaS) framework to write function based serverless and micro-service applications in hybrid multi-datacentre, on-premise and Azure environments.
Cqrs.Authentication.SingleSignOnTokenWithUserRsn Class Reference

This is a ISingleSignOnToken that includes an identifiable UserRsn to optimise the hits of the DataStores by including data you most likely need. As such, if not used correctly, this can expose identifiable information. It is suggested the service layer populates this before sending commands as part of authorisation/authentication. More...

+ Inheritance diagram for Cqrs.Authentication.SingleSignOnTokenWithUserRsn:

Public Member Functions

override string Serialise ()
 Returns UserRsn. More...
 

Properties

Guid UserRsn [get, set]
 The Rsn of the user doing the operation. When used by an external 3rd party this is the person being impersonated, not the 3rd party system itself. More...
 
- Properties inherited from Cqrs.Authentication.SingleSignOnToken
string Token [get, set]
 The authentication token. More...
 
DateTime TimeOfExpiry [get, set]
 The DateTime this token should expire. More...
 
DateTime DateIssued [get, set]
 The DateTime this token was issued. More...
 
- Properties inherited from Cqrs.Authentication.ISingleSignOnToken
string Token [get, set]
 The authentication token. More...
 
DateTime TimeOfExpiry [get, set]
 The DateTime this token should expire. More...
 
DateTime DateIssued [get, set]
 The DateTime this token was issued. More...
 
- Properties inherited from Cqrs.Authentication.ISingleSignOnTokenWithUserRsn
Guid UserRsn [get, set]
 The Rsn of the user doing the operation. When used by an external 3rd party this is the person being impersonated, not the 3rd party system itself. More...
 

Detailed Description

This is a ISingleSignOnToken that includes an identifiable UserRsn to optimise the hits of the DataStores by including data you most likely need. As such, if not used correctly, this can expose identifiable information. It is suggested the service layer populates this before sending commands as part of authorisation/authentication.