Yandex Cloud
Search
Contact UsGet started
  • Blog
  • Pricing
  • Documentation
  • All Services
  • System Status
    • Featured
    • Infrastructure & Network
    • Data Platform
    • Containers
    • Developer tools
    • Serverless
    • Security
    • Monitoring & Resources
    • ML & AI
    • Business tools
  • All Solutions
    • By industry
    • By use case
    • Economics and Pricing
    • Security
    • Technical Support
    • Customer Stories
    • Start testing with double trial credits
    • Cloud credits to scale your IT product
    • Gateway to Russia
    • Cloud for Startups
    • Education and Science
    • Yandex Cloud Partner program
  • Blog
  • Pricing
  • Documentation
© 2025 Direct Cursus Technology L.L.C.
Yandex IoT Core
    • Authentication
    • Resource relationships
    • MQTT server connection parameters
    • Sending messages to an MQTT server via gRPC
    • Backups
    • Quotas and limits
  • Access management
  • Pricing policy
  • Terraform reference
  • Monitoring metrics
  • Audit Trails events
  • Release notes
  • FAQ

In this article:

  • Authentication using certificates
  • Authenticating by username and password
  1. Concepts
  2. Authentication

Authentication

Written by
Yandex Cloud
Updated at May 12, 2025
  • Authentication using certificates
  • Authenticating by username and password

There are two authentication methods:

  • Using X.509 certificates.
  • Using a username and password.

You can use both X.509 certificates and passwords at the same time. Note that passwords have a higher priority than certificates. The table below describes different ways to use a certificate and password simultaneously during authentication.

Certificate Password Authentication
Invalid Invalid Authentication fails.
Invalid Correct Authentication is successful.
Correct Invalid Authentication fails.
Correct Correct Authentication using a username and password is successful.
Correct,
but for a different device
Correct Authentication is performed on behalf of the device, the ID of which is specified in the username.

Authentication using certificates

When authenticating with X.509 certificates, private keys and certificates stored as .pem files are used. They are stored on a device or in a registry.

  • For a private key, you specify the path to the .pem file when sending messages or subscribing to receive messages.
  • You add the certificate to the device or registry and specify the path to the .pem file with the certificate when sending messages or subscribing to receive messages.

Each certificate must be unique. You can't add the same certificate to two different devices or a device and a registry. To send and receive messages in a topic, you need to use two different certificates.

Warning

No additional settings are required for working with the MQTT broker integrated into the CLI (yc iot mqtt --help). If you use third-party libraries or applications (such as Mosquitto) as an MQTT broker, use the MQTT broker connection parameters.

Authenticating by username and password

When authenticating with your username and password:

  • The username is the ID of the device or registry.
  • The password is a combination of characters that you specify. You can also generate your password in the CLI.
    • Minimum password length is 14 characters.
    • The password must contain three groups of characters out of these four: lowercase Latin letters, uppercase Latin letters, numbers, and special characters.

See also

  • Resource relationships in Yandex IoT Core
  • Creating a certificate
  • Managing device certificates
  • Managing registry certificates
  • Managing device passwords
  • Managing registry passwords

Was the article helpful?

Previous
Viewing operations with the service's resources
Next
Resource relationships
© 2025 Direct Cursus Technology L.L.C.