Preview Tool

Cisco Bug: CSCus31042 - Runtime user validaton fr jobs owned by workgroups is not working prprly

Last Modified

Aug 27, 2018

Products (13)

  • Cisco Workload Automation
  • Cisco Tidal Enterprise Adapter for Oracle Database
  • Cisco Tidal Enterprise Scheduler 6.2
  • Cisco Tidal Enterprise Adapter for VMware
  • Cisco Tidal Enterprise Adapter for Oracle E-Business Suite
  • Cisco Tidal Enterprise Adapter for SAP
  • Cisco Tidal Enterprise Adapter for Informatica
  • Cisco Tidal Agent for Windows
  • Cisco Tidal Enterprise Adapter for Microsoft SQL Server DB
  • Cisco Tidal Enterprise Adapter for FTP/SFTP/FTPS
View all products in Bug Search Tool Login Required

Known Affected Releases


Description (partial)

The way it works now (beginning of 6.2.1) is that the owner field of the job is the one that determines what is a valid entry in the dropdowns for the agent and runtime fields. So if the job is owned by a workgroup and that workgroup has not been given permissions to use a runtime user, that user will not be in the dropdown. After, the users listed in the dropdown became the only valid runtime users. So if the owner field was a workgroup, and that RTU was not added to the workgroup, the job definition becomes uneditable.

Since 6.1's valid runtime users were tied to the currently logged in user, and it was IMPOSSIBLE to tie runtime users to workgroups or ldap groups, EVERYONE going from pre-6.2.1 to 6.2.1 will not have the valid configuration in place, since it was previously impossible. Valid configuration being, workgroups  given the runtime users they need.

Proposed solution:

When a job definition is opened and the runtime field in the database as an invalid runtime user, ask "The runtime user selected is not available to the owner. Would you like to add it now?"(workgroup, most likely). Yes/No. If the user selects "yes" then attempt to give the workgroup access to this runtime user. If that user does not have permissions to do this, then popup a message that says "Your logged in user does not have sufficient privileges to edit the permissions. Please contact your system administrator to make these changes." If "yes" is selected and the user does have permissions to make the change, make the change. If "no" is selected, do nothing and open the job as read-only.

Conditions:, web client


1.) In 6.1, Create a workgroup, and runtime user
2.) Add the runtime user to the currently logged in user (impossible to add it to the workgroup in 6.1)
3.) Create a job definition owned by that workgroup that the user is in with the runtime user that the user has been granted permission to use
4.) Upgrade to
5.) Try to edit the job definition (even as su)
Bug details contain sensitive information and therefore require a account to be viewed.

Bug Details Include

  • Full Description (including symptoms, conditions and workarounds)
  • Status
  • Severity
  • Known Fixed Releases
  • Related Community Discussions
  • Number of Related Support Cases
Bug information is viewable for customers and partners who have a service contract. Registered users can view up to 200 bugs per month without a service contract.