Child pages
  • Admin API Complex Type sshKey

This documentation is for a previous version of Flexiant Cloud Orchestrator. The most recent version is v5.0. For the most recent documentation please see here

Skip to end of metadata
Go to start of metadata

Description
The SSHKey class describes an ssh key.
Derived By
Extending virtualResource
Content Model
Contains elements as defined in the following table.

Component

Type

Occurs

Description

billingEntityUUID

string

0..1

The UUID of the Billing Entity to which the resource belongs

resourceCreateDate

dateTime

0..1

The creation date of the resource

resourceKey

resourceKey

0..*

The keys attached to the resource

resourceMetadata

resourceMetadata

0..1

The metadata attached to the resource

resourceName

string

0..1

The name of the resource

resourceState

resourceState

0..1

The state of the resource

resourceType

resourceType

0..1

The type of the resource

resourceUUID

string

0..1

The UUID of the resource (read-only)

clusterName

string

0..1

The name of the cluster in which the resource is located

clusterUUID

string

0..1

The UUID of the cluster in which the resource is located

customerName

string

0..1

The name of the customer that owns the resource

customerUUID

string

0..1

The UUID of the customer that owns the resource

productOfferName

string

0..1

The name of the product offer associated with the resource

productOfferUUID

string

0..1

The UUID of the product offer associated with the resource

vdcName

string

0..1

The name of the VDC in which the resource is contained

vdcUUID

string

0..1

The UUID of the VDC in which the resource is contained

globalKey

boolean

1..1

 

publicKey

string

0..1

The public key in the same format as a line from authorized_keys

userName

string

0..1

The username to which the ssh key applies (or none to make it apply to the default initial user)

Remarks
SSHKeys are provided to servers via metadata. The normal use case is that they can initialise the SSH keys for the initial user on boot, thus permitted secure login without the danger inherent in an initial password.

  • No labels