Versions Compared

Version Old Version 3 New Version Current
Changes made by

Frode Nilsen (Unlicensed)

Kristoffer Kristoffer (Unlicensed)

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Published by Scroll Versions from space PDOIDC and version master
URLhttps://<fraud-data-baseurl>/securityData/<tid>
Request

GET with URL path parameter tid for the authentication session is question (Transaction ID from the ID Token)

AuthenticationAccess Token as Bearer Token in Authorization Header
Response
202AcceptedA new process for retrieval of fraud data for tid  is accepted
204No ContentA process for retrieval of fraud data for tid  is still ongoing (not yet completed)
200OKA process for retrieval of fraud data for tid has completed. The body contains a JSON with fraud data response elements.
400Bad requestThe tid value does not correspond to a session associated with the requesting OIDC client
401Unauthorized Bearer token is missing or not accepted for any reason
403ForbiddenBearer token has insufficient scope
404Not foundThe tid  is an unknown value for the OIDC Provider.
410GoneFraud data for tid is no longer available
429Too many requests The fraud data service is currently too busy to serve the request
500Internal server error Any other error condition

Error responses contains further information on the reason according to standard.

ExampleSee below

This method provides data (security data / fraud data) that can be used for risk scoring on a recent authentication session via the OIDC Provider. The  tid claim from the ID Token works as the reference to the session in question. At first invocation of this method for a given tid, the Fraud Data service starts a process to retrieve all relevant data for the transaction in question. When all available fraud data for the given transaction has been retrieved, the set of available data may be returned to the requesting OIDC Client upon request. The typical usage pattern for an OIDC Client is to receive a 202 in response to the initial request, followed by one or more 204 responses on subsequent polling requests, before the service eventually responds with a 200 along with the actual fraud data in the body. 

...

The following is a truncated JSON example from the response from the Fraud Data service for an authentication session with BankID netcentric. A complete JSON example is not included in this documentation for security reasons. A complete example can be provided upon request.

...