open-vault/website/source/docs/auth/alicloud.html.md
Jeff Escalante a3dfde5cec New Docs Website (#5535)
* conversion stage 1

* correct image paths

* add sidebar title to frontmatter

* docs/concepts and docs/internals

* configuration docs and multi-level nav corrections

* commands docs, index file corrections, small item nav correction

* secrets converted

* auth

* add enterprise and agent docs

* add extra dividers

* secret section, wip

* correct sidebar nav title in front matter for apu section, start working on api items

* auth and backend, a couple directory structure fixes

* remove old docs

* intro side nav converted

* reset sidebar styles, add hashi-global-styles

* basic styling for nav sidebar

* folder collapse functionality

* patch up border length on last list item

* wip restructure for content component

* taking middleman hacking to the extreme, but its working

* small css fix

* add new mega nav

* fix a small mistake from the rebase

* fix a content resolution issue with middleman

* title a couple missing docs pages

* update deps, remove temporary markup

* community page

* footer to layout, community page css adjustments

* wip downloads page

* deps updated, downloads page ready

* fix community page

* homepage progress

* add components, adjust spacing

* docs and api landing pages

* a bunch of fixes, add docs and api landing pages

* update deps, add deploy scripts

* add readme note

* update deploy command

* overview page, index title

* Update doc fields

Note this still requires the link fields to be populated -- this is solely related to copy on the description fields

* Update api_basic_categories.yml

Updated API category descriptions. Like the document descriptions you'll still need to update the link headers to the proper target pages.

* Add bottom hero, adjust CSS, responsive friendly

* Add mega nav title

* homepage adjustments, asset boosts

* small fixes

* docs page styling fixes

* meganav title

* some category link corrections

* Update API categories page

updated to reflect the second level headings for api categories

* Update docs_detailed_categories.yml

Updated to represent the existing docs structure

* Update docs_detailed_categories.yml

* docs page data fix, extra operator page remove

* api data fix

* fix makefile

* update deps, add product subnav to docs and api landing pages

* Rearrange non-hands-on guides to _docs_

Since there is no place for these on learn.hashicorp, we'll put them
under _docs_.

* WIP Redirects for guides to docs

* content and component updates

* font weight hotfix, redirects

* fix guides and intro sidenavs

* fix some redirects

* small style tweaks

* Redirects to learn and internally to docs

* Remove redirect to `/vault`

* Remove `.html` from destination on redirects

* fix incorrect index redirect

* final touchups

* address feedback from michell for makefile and product downloads
2018-10-19 08:40:11 -07:00

4.4 KiB

layout page_title sidebar_title sidebar_current description
docs AliCloud - Auth Methods AliCloud docs-auth-alicloud The AliCloud auth method allows automated authentication of AliCloud entities.

AliCloud Auth Method

The alicloud auth method provides an automated mechanism to retrieve a Vault token for AliCloud entities. Unlike most Vault auth methods, this method does not require manual first-deploying, or provisioning security-sensitive credentials (tokens, username/password, client certificates, etc), by operators. It treats AliCloud as a Trusted Third Party and uses a special AliCloud request signed with private credentials. A variety of credentials can be used to construct the request, but AliCloud offers instance metadata that's ideally suited for the purpose. By launching an instance with a role, the role's STS credentials under instance metadata can be used to securely build the request.

Authentication Workflow

The AliCloud STS API includes a method, sts:GetCallerIdentity, which allows you to validate the identity of a client. The client signs a GetCallerIdentity query using the AliCloud signature algorithm. It then submits 2 pieces of information to the Vault server to recreate a valid signed request: the request URL, and the request headers. The Vault server then reconstructs the query and forwards it on to the AliCloud STS service and validates the result back.

Importantly, the credentials used to sign the GetCallerIdentity request can come from the ECS instance metadata service for an ECS instance, which obviates the need for an operator to manually provision some sort of identity material first. However, the credentials can, in principle, come from anywhere, not just from the locations AliCloud has provided for you.

Each signed AliCloud request includes the current timestamp and a nonce to mitigate the risk of replay attacks.

It's also important to note that AliCloud does NOT include any sort of authorization around calls to GetCallerIdentity. For example, if you have a RAM policy on your credential that requires all access to be MFA authenticated, non-MFA authenticated credentials will still be able to authenticate to Vault using this method. It does not appear possible to enforce a RAM principal to be MFA authenticated while authenticating to Vault.

Authorization Workflow

The basic mechanism of operation is per-role.

Roles are associated with a role ARN that has been pre-created in AliCloud. AliCloud's console displays each role's ARN. A role in Vault has a 1:1 relationship with a role in AliCloud, and must bear the same name.

When a client assumes that role and sends its GetCallerIdentity request to Vault, Vault matches the arn of its assumed role with that of a pre-created role in Vault. It then checks what policies have been associated with the role, and grants a token accordingly.

Authentication

Via the CLI

Enable AliCloud authentication in Vault.

$ vault auth enable alicloud

Configure the policies on the role.

$ vault write auth/alicloud/role/dev-role arn='acs:ram::5138828231865461:role/dev-role'

Perform the login operation

$ vault write auth/alicloud/login \
        role=dev-role \
        identity_request_url=$IDENTITY_REQUEST_URL_BASE_64 \
        identity_request_headers=$IDENTITY_REQUEST_HEADERS_BASE_64

For the RAM auth method, generating the signed request is a non-standard operation. The Vault CLI supports generating this for you:

$ vault login -method=alicloud access_key=... secret_key=... security_token=... region=...

This assumes you have the AliCloud credentials you would find on an ECS instance using the following call:

curl 'http://100.100.100.200/latest/meta-data/ram/security-credentials/$ROLE_NAME'

Please note the $ROLE_NAME above is case-sensitive and must be consistent with how it's reflected on the instance.

An example of how to generate the required request values for the login method can be found found in the Vault CLI source code.

API

The AliCloud auth method has a full HTTP API. Please see the AliCloud Auth API for more details.