Chapter 6: RSM User Accounts and Passwords

RSM needs to acquire and cache your credentials to be able to submit jobs to a cluster on your behalf. RSM's direct integration with ANSYS applications and built-in caching capability automates this process to a great extent.

When you submit a job to RSM from Workbench for the first time, RSM will prompt you to specify credentials for accessing the cluster associated with the chosen RSM queue. RSM will validate and cache the credentials, and there will be no need to specify credentials again unless your password changes. See Credential Caching from Workbench.

When you submit a job from EKM, your operating system account credentials are passed to RSM by default unless you have specified credential overrides in your EKM job management preferences. See Credential Caching from EKM.

RSM's auto-caching capability eliminates the need to manually define user accounts in RSM. In previous versions of RSM it was necessary to define alternate accounts if different credentials were needed to log in to a remote resource. This is no longer necessary in Release 18, because the credentials required to access a remote cluster are cached in RSM the first time you submit a job to RSM.

Each user account is associated with a specific cluster configuration defined in RSM, and therefore tied to the RSM queues defined in the configuration. In addition to auto-account creation, you can create a user account directly in RSM, and apply the account to a cluster configuration.


Important:  For improved account security, passwords are always cached on the client machine, even if jobs will be submitted to a remote cluster. Passwords are no longer centrally cached and managed as they were in previous releases.


The following topics are discussed in this section:


Release 18.2 - © ANSYS, Inc. All rights reserved.