`bm idp ldap accesskey info`

Description

The bm idp ldap accesskey info outputs information about the specified access key(s).

This command works against access keys created by an AD/LDAP user after authenticating to Buckit.

Create AD/LDAP service accounts with the bm idp ldap accesskey create command.

Buckit supports using AssumeRoleWithLDAPIdentity to generate temporary access keys using the Security Token Service.

EXAMPLE

The following example outputs details for the access key mykey from the buckit deployment:

bm idp ldap accesskey info buckit/ mykey

SYNTAX

The command has the following syntax:

bm [GLOBALFLAGS] idp ldap accesskey info      \
                                    ALIAS     \
                                    KEY       \
                                    [KEY2] ...

Replace ALIAS with the alias of a Buckit deployment configured for AD/LDAP integration.
Replace KEY with the access key to delete. You can list more than one access key by separating each key with a space.

Brackets [] indicate optional parameters.
Parameters sharing a line are mutually dependent.
Parameters separated using the pipe | operator are mutually exclusive.

Copy the example to a text editor and modify as-needed before running the command in the terminal/shell.

Parameters

ALIAS

Required

The alias of the Buckit deployment configured for AD/LDAP.

For example:

bm idp ldap accesskey ls buckit

KEY

Required

The configured access key to output information about.

You can list more than one access key by separating each key with a space.

Example

Output information about the access keys mykey and mykey2 from the buckit deployment.

bm idp ldap accesskey info buckit/ mykey mykey2

Global Flags

This command supports any of the global flags.

Behavior

S3 Compatibility

The bm commandline tool is built for compatibility with the AWS S3 API and is tested with Buckit and AWS S3 for expected functionality and behavior.

Buckit provides no guarantees for other S3-compatible services, as their S3 API implementation is unknown and therefore unsupported. While bm commands may work as documented, any such usage is at your own risk.