Working with Web Services > Privileged operations

Privileged operations

While Authenticated operations only require a user, some operations in Web Services require a user and specific user permissions. These are called privileged operations.

As with authenticated operations, for a privileged operation you must have first logged in the user and received a session token. But unlike authenticated operations, in a privileged operation, the user must also have additional SirsiDynix Symphony user rights. These rights might be that the user has a privilege level of Staff or higher, or has command code rights to execute the request, or both.

Then as part of the request for the privileged operation, you include the session token for the user. If the session token is valid and the user has sufficient rights, the request is processed (see Working with Web Services sessions).

The lookupUserInfo operation is an example of a privileged operation that requires a session token and sufficient user rights.

See Command list for information on the rights required for each privileged operation.

The PatronSamples example shows how to make the login request and return the session token for use in privileged operations. See Interacting with patron data using Perl for a specific example.

Related topics 

 


© 2009-2012 SirsiDynix