...
Informācijas iegūšana par identitāti no elektroniskā paraksta
There is two types of signing identity, one for electronic signing and one for authentication
Request
| Code Block |
|---|
GET /trustedx-resources/esigp/v1/sign_identities/{sign_identity_id} |
Parameters
| Name | Type | Usage | Description |
|---|---|---|---|
sign_identity_id | path | Required | Identifier of the signing identity information is being requested on. |
Authorization
The request must contain a bearer access token generated by a trusted authorization server of the service from which the information on the signing identity is requested and that is associated to the domain to which the identity belongs. This token must be used as explained in RFC 6750. It must have the urn:safelayer:eidas:sign:identity:profile scope.
...
The access token can be obtained via an authorization code grant or Service provider's credentials grant OAuth 2.0 flow.
Example
| Code Block |
|---|
GET /trustedx-resources/esigp/v1/sign_identities/12345678 HTTP/1.1 Authorization: Bearer mF_9.B5f-4.1JqM |
Response
Response body representation in JSON as follows
...