OCID do usuário na OCI: onde ficam o user OCID, o tenancy OCID, o compartment e a fingerprint, e por que a CLI responde 401
O guia da OCI deste site explica como gerar a API key e colá-la no Control Cloud. O Search Console mostra gente chegando com buscas como "user ocid" e "oci auth", ou seja, o passo anterior: onde está cada dado e por que a CLI responde 401. Esta nota junta os caminhos do console para o OCID do usuário, o da tenancy e o de um compartment, a região e a fingerprint, como fica o ~/.oci/config, como…
The article explains where to find the User OCID, Tenancy OCID, Compartment OCID, and fingerprint in the Oracle Cloud Infrastructure (OCI) console, and why the CLI may respond with a 401 error. The OCID of a user can be found by going to Profile and clicking on User settings, while the Tenancy OCID can be found by going to Profile and clicking on Tenancy.
The Compartment OCID can be found by going to Identity & Security → Identity → Compartments. The fingerprint is displayed when you send the public key to the user, and it identifies which of the user's public keys signed the request. The CLI responds with a 401 error when the required authentication information is not provided or is incorrect, meaning that one of the OCID, fingerprint, or private key is missing or incorrect.
The key file should point to the private key, not the public key, and the key format should be PEM, not ssh-rsa. The tenancy must also be subscribed to the region configured in the region field, and the user must be in a group with the necessary permissions for the operation. The clock on the machine must also be within five minutes of the server's clock.
The Control Cloud form only asks for the tenancy OCID, user OCID, fingerprint, and the private key content, but not the region or compartment.
Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.
This story
This is one outlet's version. Read the fullest account.
