The sign service supports scopes and claims as shown below.

Scopes

The following scopes with corresponding API access are supported. See the section on Access Tokens sign for further information on the use of the signdoc/read_write scope.

Scope	Access
signdoc/read_write	API access to SignDoc RS
sign	Access to start a sign session using the authorize endpoint

Claims

Simplified flow

The following table show the additional claims in the id_token after a simplified flow sign session has been finished.

Claim

Example

Description

sign_result

"sign_result" : {
    "endUser" : "MIAGC...",
    "merchant" : "MIAGC...",
    "hash" : "4oK3g..."
}

Signatures of the merchant and end user, as well as the hash over the received text.

Full flow: SEID-SDO

The following table shows the supported claims in response from the sign service after a SEID-SDO sign session is completed.

Claim	Example	Result specifier	Description
documentHashes	`documentHashes": [` "w5SZXrar2s7lR+lafX4Bx9v8/dm2xs5eybCTUOE9rao=" ]	documentHash	Array of hashes over the documents to be signed in the same order as the documents in the signing order
sdos	`"sdos": ["PD94bWwgdmVyc2lvbj0iMS4wIiBlbmNvZ......"]`	sdo	The SEID-SDO represented as base64 (unpack to UTF-8), one for each document
merchantSignatures	`"merchantSignatures": ["MIAGCSqGSIb3DQEHAqCAMIACAQExDzANB...."]`	basicSignature	The merchant signature, one for each document
endUserSignatures	`"endUserSignatures": ["MIAGCSqGSIb3DQEHAqCAMIACAQExDTALBAA....."]`	basicSignature	The end user signature, one for each document
signId	"910bd95b-41c0-4b6d-ae3f-d9458110d12a"		The sign_id used
clientId	"oidc-testclient"		The OIDC client used
orderState	"SIGN_COMPLETED"		Current order state
orderName	"Overlay-example"		Name of order

Full flow: PAdES

The following table shows the supported claims in response from the sign service after a PAdES sign session is completed.

Claim	Example	Result specifier	Description
unsignedDocumentSha256	"unsignedDocumentSha256": "ZfesfmamB+ADft4A0DVMAbHQ7mEeg24v3PXBsXDKf5k="	documentHash	Hash over the original document
signedDocumentSha256	"signedDocumentSha256": "ApPACd0HXMzuSB/Zt1HU9oJLAxpWvRX2/gRpu63Vs1k="	documentHash	Hash over the signed document
padesSignedPdf	"padesSignedPdf": "JVBERi0xLjQNJeLjz9MNCjEwIDAgb2JqDTw8L0xpbmVhcml6...	padesSignedPdf	The signed pdf as a base64 encoded text string
padesAppendix	"padesAppendix": "DQoxMSAwIG9iago8PAovTWV0YWRhdGEgMiAwIFIKL09wZW5BY...	padesAppendix	The signature data added to the original PDF represented as base64
description	"description": "some_document.pdf"		Description of the document
signId	"signId": "058d8691-6f2d-40c0-b6fb-f120a868cf48"		The sign_id reference
orderState	"SIGN_COMPLETED"		The current order state
orderName	"Overlay-example"		Name of the order

LATEST CURRENT (OIDC)

Scopes and claims Sign

Analytics

Scopes

Claims

Simplified flow

Full flow: SEID-SDO

Full flow: PAdES

Related content