Share via

Troubleshooting Security and Permissions Issues

  • Article

This content is no longer actively maintained. It is provided as is, for anyone who may still be using these technologies, with no warranties or claims of accuracy with regard to the most recent product version or service release.

This section addresses issues relating to general security in the workflow application. This might include Microsoft® Windows® 2000, Microsoft® SQL Server™, and Workflow Designer for SQL Server row-level permissions.

Security Requirements and Limitations

To secure your workflow applications, it is important to consider the following issues:

  • All the users of a server that contains workflow applications should log on using Windows 2000 authentication. Local SQL Server logins are not supported.
  • Because Windows 2000 caches user credentials and SQL Server is using Windows 2000 authentication, any changes made to a user's Windows 2000 or SQL Server login accounts will not take affect until the user logs off and then logs back on. Therefore, if credentials are changed during an active connection, SQL Server only recognizes the new credentials after the user logs out and logs back on.

Insert and Column Permissions Limitations

By default, any data changes on a data access page bound to an SQL view (for example, IssuesView in the Issue Tracking sample application) send updates to the underlying table (for example, Issues).

When a table is added to the table hierarchy, the permissions provided depend on whether the table has a primary key defined. For example, if the table has a primary key and row-level permissions are enabled, then update, insert, and delete permissions are provided by default on the base table. In addition, select permissions are provided on the primary key columns of the base table, which makes updating possible. If the primary key does not exist, no changes are made to the table permissions.

Permissions in the Issue Tracking Sample

If you make any changes to row-level permissions in the Issue Tracking sample, you must update the IssuesBaseView manually with those changes. The IssuesBaseView is not updated automatically with changes you make to the Issues or IssuesView tables.

See Also

Troubleshooting Workflow Applications for SQL Server | Troubleshooting Setup and Server Issues | Troubleshooting Database Issues | Troubleshooting Workflow Process and Scripting Issues | Error Messages