Create
Create mints a decoy credential and returns the one-time vending material exactly once. The Decoy id is server-set; the credential’s secret cannot be retrieved again after this response.
Authorizations
Bearer authentication header of the form Bearer <token>, where <token> is your auth token.
This API uses OAuth2 with the Client Credential flow. Client Credentials must be sent in the BODY, not the headers. For an example of how to implement this, refer to the c1TokenSource.Token() function.
Body
The DecoyServiceCreateRequest message.
This message contains a oneof named create_input. Only a single field of the following list may be set at a time:
- userClientCredential
- connectorClient
- workloadFed
- accessToken
DecoyAccessTokenInput mints a session access-token decoy under an existing User.
The annotations field.
DecoyConnectorClientInput plants a connector-shaped credential decoy. The server allocates placement under the tenant's ConductorOne app; the customer makes no app/connector choice.
The description field.
The displayName field.
DecoyUserClientCredentialInput plants a client-credential decoy under an existing User. The User must be typ=HUMAN or typ=SERVICE.
DecoyWorkloadFederationInput plants a workload-federation-trust decoy under an existing Provider. The Provider must already be registered so its JWKS is reachable for signature verification.
Response
Successful response
The DecoyServiceCreateResponse message.
Decoy is the read projection of a planted honey-credential. All fields except annotations are server-managed.
DecoyVendingMaterial carries the freshly-vended secret material returned exactly once at Create or Rotate.
This message contains a oneof named material. Only a single field of the following list may be set at a time:
- clientCredential
- accessToken
- workloadFederation