Yandex Cloud
Search
Contact UsGet started
  • Pricing
  • Customer Stories
  • Documentation
  • Blog
  • All Services
  • System Status
    • Featured
    • Infrastructure & Network
    • Data Platform
    • Containers
    • Developer tools
    • Serverless
    • Security
    • Monitoring & Resources
    • AI for business
    • Business tools
  • All Solutions
    • By industry
    • By use case
    • Economics and Pricing
    • Security
    • Technical Support
    • Start testing with double trial credits
    • Cloud credits to scale your IT product
    • Gateway to Russia
    • Cloud for Startups
    • Center for Technologies and Society
    • Yandex Cloud Partner program
  • Pricing
  • Customer Stories
  • Documentation
  • Blog
© 2025 Direct Cursus Technology L.L.C.
Yandex Identity Hub
  • Access management
  • Pricing policy
  • Terraform reference
    • Authentication
      • Overview
        • Overview
          • Overview
            • Overview
            • Get
            • List
            • Create
            • Update
            • Delete
  • Audit Trails events
  • Release notes

In this article:

  • HTTP request
  • Path parameters
  • Response
  1. API reference
  2. REST
  3. Identity Provider API
  4. SAML Application API
  5. SignatureCertificate
  6. Get

SAML Application API, REST: SignatureCertificate.Get

Written by
Yandex Cloud
Updated at October 30, 2025
  • HTTP request
  • Path parameters
  • Response

Returns the specified signature certificate.

To get the list of available certificates, make a List request.

HTTP requestHTTP request

GET https://organization-manager.api.cloud.yandex.net/organization-manager/v1/idp/application/saml/signature-certificates/{signatureCertificateId}

Path parametersPath parameters

Request to get a signature certificate by ID.

Field

Description

signatureCertificateId

string

Required field. ID of the signature certificate to return.

ResponseResponse

HTTP Code: 200 - OK

{
  "id": "string",
  "applicationId": "string",
  "status": "string",
  "name": "string",
  "description": "string",
  "createdAt": "string",
  "data": "string",
  "fingerprint": "string",
  "notAfter": "string",
  "notBefore": "string"
}

A signature certificate for SAML applications.

Field

Description

id

string

Unique identifier of the signature certificate.

applicationId

string

ID of the SAML application that the signature certificate belongs to.

status

enum (Status)

Current status of the signature certificate.

  • STATUS_UNSPECIFIED: The status is not specified.
  • ACTIVE: The certificate is active and can be used for signing.
  • INACTIVE: The certificate is inactive and cannot be used for signing.

name

string

Name of the signature certificate.

description

string

Description of the signature certificate.

createdAt

string (date-time)

Creation timestamp.

String in RFC3339 text format. The range of possible values is from
0001-01-01T00:00:00Z to 9999-12-31T23:59:59.999999999Z, i.e. from 0 to 9 digits for fractions of a second.

To work with values in this field, use the APIs described in the
Protocol Buffers reference.
In some languages, built-in datetime utilities do not support nanosecond precision (9 digits).

data

string

Certificate data in PEM format.

fingerprint

string

SHA256-fingerprint of the signature certificate.

notAfter

string (date-time)

Time after which the signature certificate is not valid.

String in RFC3339 text format. The range of possible values is from
0001-01-01T00:00:00Z to 9999-12-31T23:59:59.999999999Z, i.e. from 0 to 9 digits for fractions of a second.

To work with values in this field, use the APIs described in the
Protocol Buffers reference.
In some languages, built-in datetime utilities do not support nanosecond precision (9 digits).

notBefore

string (date-time)

Time before which the signature certificate is not valid.

String in RFC3339 text format. The range of possible values is from
0001-01-01T00:00:00Z to 9999-12-31T23:59:59.999999999Z, i.e. from 0 to 9 digits for fractions of a second.

To work with values in this field, use the APIs described in the
Protocol Buffers reference.
In some languages, built-in datetime utilities do not support nanosecond precision (9 digits).

Was the article helpful?

Previous
Overview
Next
List
© 2025 Direct Cursus Technology L.L.C.