Process Orchestrator: Cannot Connect UCS Manager with Domain Credentials

Available Languages

Updated:January 24, 2012

Document ID:113400

Bias-Free Language

The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.

Introduction

Prerequisites

Components Used

Problem

Solution

Related Information

Introduction

This document describes how to set up a Unified Computing System (UCS) Manager run-time user when the UCS Manager is in a domain.

Prerequisites

Components Used

The information in this document is based on the Cisco Process Orchestrator 2.2 and later.

The information in this document was created from the devices in a specific lab environment. All of the devices used in this document started with a cleared (default) configuration. If your network is live, make sure that you understand the potential impact of any command.

Problem

When attempting to use local or domain users when the UCS Manager is in a domain, the run-time user (if not properly configured) will receive an authentication error.

Solution

On the username of the run-time user, the domain or local must be listed in the configuration preceded by "ucs-". For example, if the username was "bob", the local run-time user would be "ucs-local\bob". For a domain user, it would be "ucs-domainname\bob". Once these run-time users are set up properly, a connection should occur.