Esta página ainda não está disponível no idioma selecionado. Estamos trabalhando para adicionar mais opções de idiomas. Agradecemos sua compreensão.
- What's New
- Service Overview
- Billing
- Getting Started
- User Guide
- API Reference
- SDK Reference
-
FAQs
-
DeH FAQs
- What Is DeH?
- When a DeH Is Needed?
- Can I Use DeHs to Build Websites?
- Can I Buy DeHs by Myself?
- What Hypervisor Is Used by DeHs?
- Does Each DeH Have a Unique ID?
- What Are the Differences Between DeHs and BMSs?
- What Are the Differences Between DeH and DeC?
- What Are the Differences Between DeHs and ECSs?
- How Can I Query the Number of Available Resources on a DeH?
- Why Is It Not Possible to Successfully Create an ECS on a DeH Even When There Are More Available Resources on the DeH Than What the ECS Requires?
- Does DeH Support Capacity Expansion?
- What Is BYOL?
- How Do I Bring My Own Licenses to a DeH?
- Can I Attach an EVS Disk to a DeH?
- Is There a Limit on the Number of DeHs That I Can Purchase?
-
ECS FAQs
- What Are the Differences Between ECSs on DeHs and Those on Shared Hosts?
- What Are the Restrictions on Creating ECSs on a DeH?
- Can I Create ECSs of Different Flavors on a DeH?
- Can I Modify the Specifications of ECSs on DeHs?
- What Should I Do If I Fail to Create an ECS on a DeH?
- Can I Migrate ECSs in Resource Pools to DeHs?
- Billing FAQs
-
DeH FAQs
- Videos
- Glossary
-
More Documents
-
User Guide (Paris Region)
- Product Introduction
- Getting Started
- DeH Management
- ECS Management
- Tag Management
- Key Operations Recorded by CTS
- Managing Enterprise Projects
- Permission Management
-
FAQs
-
DeH FAQs
- What Is DeH?
- When a DeH Is Needed?
- Can I Use DeHs Build Websites?
- Can I Allocate DeHs by Myself?
- What Hypervisor Is Used by DeHs?
- Does Each DeH Have a Unique ID?
- What Are the Differences Between DeHs and BMSs?
- What Are the Differences Between DeH and DeC?
- What Are the Differences Between DeHs and ECSs?
- How Can I Query the Number of Available Resources on a DeH?
- Does DeH Support Capacity Expansion?
- What Is BYOL?
- How Do I Bring My Own Licenses to a DeH?
- Can I Attach an EVS Disk to a DeH?
- Is There a Limit on the Number of DeHs That I Can Purchase?
-
ECS FAQs
- What Are the Differences Between ECSs on DeHs and Those on Shared Hosts?
- What Are the Restrictions on Creating ECSs on a DeH?
- Can I Create ECSs of Different Flavors on a DeH?
- Can I Modify the Specifications of ECSs on DeHs?
- What Should I Do If I Fail to Create an ECS on a DeH?
- Can I Migrate ECSs in Resource Pools to DeHs?
- Billing FAQs
-
DeH FAQs
- Change History
- API Reference (Paris Region)
-
User Guide (Paris Region)
- General Reference
Copied.
Authentication
- Token authentication: Requests are authenticated using tokens.
- AK/SK authentication: Requests are encrypted using AK/SK pairs. AK/SK authentication is recommended because it is more secure than token authentication.
Token Authentication
The validity period of a token is 24 hours. When using a token for authentication, cache it to prevent frequently calling the IAM API used to obtain a user token.
A token specifies temporary permissions in a computer system. During API authentication using a token, the token is added to requests to get permissions for calling the API. You can obtain a token by calling the Obtaining User Token API.
DeH is a project-level service. When you call the API, set auth.scope in the request body to project.
{ "auth": { "identity": { "methods": [ "password" ], "password": { "user": { "name": "username", // IAM user name "password": "********", // IAM user password "domain": { "name": "domainname" // Name of the account to which the IAM user belongs } } } }, "scope": { "project": { "name": "xxxxxxxx" // Project Name } } } }
After a token is obtained, the X-Auth-Token header field must be added to requests to specify the token when calling other APIs. For example, if the token is ABCDEFJ...., X-Auth-Token: ABCDEFJ.... can be added to a request as follows:
1 2 3 |
POST https://{{endpoint}}/v3/auth/projects Content-Type: application/json X-Auth-Token: ABCDEFJ.... |
AK/SK Authentication
AK/SK authentication supports API requests with a body not larger than 12 MB. For API requests with a larger body, token authentication is recommended.
In AK/SK authentication, AK/SK is used to sign requests and the signature is then added to the requests for authentication.
- AK: access key ID, which is a unique identifier used in conjunction with a secret access key to sign requests cryptographically.
- SK: secret access key, which is used in conjunction with an AK to sign requests cryptographically. It identifies a request sender and prevents the request from being modified.
In AK/SK authentication, you can use an AK/SK to sign requests based on the signature algorithm or using the signing SDK. For details about how to sign requests and use the signing SDK, see API Request Signing Guide.
The signing SDK is only used for signing requests and is different from the SDKs provided by services.
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
For any further questions, feel free to contact us through the chatbot.
Chatbot