Staging Security Options
Commerce Server Staging (CSS) supports three methods for establishing authentication credentials for the transmission and reception of content and data. The three methods are as follows:
Destination-level authentication. A project is configured to have the CSS authentication account credentials for those CSS servers to which they will transmit content and data.
Project-level authentication. A single CSS authentication account is defined in the project for the source staging server. This account is used to stage the project across the servers in the staging project.
Default authentication. Each CSS server is assigned default authentication credentials. These credentials are used to authenticate transmission of content and data across the servers in the staging project.
Regardless of the method that is used, the CSS authentication account that is used to authenticate the receipt of data must be defined on the resident CSS server which receives the data. Also, each CSS authentication account specified for each of these levels of authentication must be members of the CSS Administrators or CSS Operators groups on the destination CSS servers. For more information about CSS authentication accounts, see How Are CSS Authentication Accounts Defined and Managed?
For staging of business data projects, database access permissions must be granted to the CSS authentication accounts that are used to export and import data. For information about these requirements, see What Database Access Permissions Must You Grant to CSS Authentication Accounts?
See Also
Other Resources
How Are CSS Authentication Accounts Defined and Managed?
What Database Access Permissions Must You Grant to CSS Authentication Accounts?
How to Configure Destination-Level Authentication
How to Configure Project-Level Authentication
How to Change the Default (Global) Authentication Account
What are the Staging Security Configuration Requirements?