Token

Issues a JSON web token that can be used for authentication with Quippe. The identity for the token comes from the current, authenticated request context: either HTTP basic auth, an ASP.NET session cookie, or a previously-issued JWT presented as a bearer token in the Authorization HTTP header. When this endpoint is called, the token property in the response can then by presented in the Authorization HTTP header of future requests: Bearer [token]. Configuration attributes for things like the signing key, token lifetime, etc. can be adjusted through the DataServices.xml for the Quippe.Security.ITokenJwksService data service.