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.
Authentication
AuthorizationBasic
Login and password used to access quippe.medicomp.com. On-premise Quippe deployments can be configured to use whatever authentication and authorization your application is configured for, so basic authentication is used here to access the Quippe sandbox and is not a product requirement.
OR
AuthorizationBearer
JSON web token generated by a request to the /Quippe/Security/Token web service endpoint in Quippe.
Query parameters
DataFormat
Specifies how objects are encoded in the output
Allowed values:
RequestId
Optional value that can be used by clients to track multiple requests.
Culture
Culture to use when handling the request. If not specified the default value configured on the server will be used.
Response
Successful response
response
Errors
401
Unauthorized Error
500
Internal Server Error