Process credentials and impersonation

You apply credentials and impersonation to control who can deploy applications or microservices and where the applications or microservices are deployed.

  • You can attach one or more credentials to component, application, or microservice process steps.

  • You can use only one impersonation credential when running an application or microservice process, component process, or a process step.

  • When you attach an impersonation credential in CloudBees Flow, it specifies the user who can deploy the application or microservice and the environment in which the application or microservice is deployed.

  • When you attach an impersonation credential to a platform-level object (such as a procedure), it specifies the account (user) that can run the job or job step. If you want to specify another condition, you have to attach another credential to the object.

When you impersonate using a credential, make sure that the impersonated user has the absolute path to the bin directories in the $PATH environment. If you define a process step with a command, you must enter the absolute path in the Post Processor and Shell fields in the Define Step dialog box.

Click in the Add Credentials field. The Component Process Step / Add dialog box opens.

  • To impersonate one credential:

    1. Select Impersonate in the Type field.

    2. Click the Select Project field to select a project. You can select a credential from a project that is different than the one containing the application.

    3. Select the Select Credential field to open a drop-down list of credentials for the process step.

    4. Select a credential.

    5. Click OK .

      The Credentials dialog box now shows the one credential for impersonation.

  • To attach one or more credential parameters to the process step:

    1. Select Attach Parameter in the Type field.

    2. Click the Select Credential Parameter field to open a drop-down list of credentials for the process step.

    3. Select a credential.

    4. Click OK .

      The Credentials dialog box now shows the attached credentials

  • To attach one or more credentials to the process step:

    1. Select Attach in the Type field.

    2. Click the Select Project field to select a project. You can select a credential from a project that is different than the one containing the application.

    3. Click the Select Credential field to open a drop-down list of credentials for the process step.

    4. Select a credential.

    5. Click OK .

      The Credentials dialog box now shows the attached credentials.

Copyright © 2010-2020 CloudBees, Inc.Online version published by CloudBees, Inc. under the Creative Commons Attribution-ShareAlike 4.0 license.CloudBees and CloudBees DevOptics are registered trademarks and CloudBees Core, CloudBees Flow, CloudBees Flow Deploy, CloudBees Flow DevOps Insight, CloudBees Flow DevOps Foresight, CloudBees Flow Release, CloudBees Accelerator, CloudBees Accelerator ElectricInsight, CloudBees Accelerator Electric Make, CloudBees CodeShip, CloudBees Jenkins Enterprise, CloudBees Jenkins Platform, CloudBees Jenkins Operations Center, and DEV@cloud are trademarks of CloudBees, Inc. Most CloudBees products are commonly referred to by their short names — Accelerator, Automation Platform, Flow, Deploy, Foresight, Release, Insight, and eMake — throughout various types of CloudBees product-specific documentation. Oracle and Java are registered trademarks of Oracle and/or its affiliates. Jenkins is a registered trademark of the non-profit Software in the Public Interest organization. Used with permission. See here for more info about the Jenkins project. The registered trademark Jenkins® is used pursuant to a sublicense from the Jenkins project and Software in the Public Interest, Inc. Read more at www.cloudbees.com/jenkins/about. Apache, Apache Ant, Apache Maven, Ant and Maven are trademarks of The Apache Software Foundation. Used with permission. No endorsement by The Apache Software Foundation is implied by the use of these marks.Other names may be trademarks of their respective owners. Many of the designations used by manufacturers and sellers to distinguish their products are claimed as trademarks. Where those designations appear in this content, and CloudBees was aware of a trademark claim, the designations have been printed in caps or initial caps. While every precaution has been taken in the preparation of this content, the publisher and authors assume no responsibility for errors or omissions, or for damages resulting from the use of the information contained herein.