Have permission to manage
Standard authorization ID The OAM recognizes a default permission group to which all users nominally be assigned. This group is represented by the pseudo authorization ID 'NOBODY' defined. 'NOBODY' can queue line control seem like a valid authorization ID used will assign permissions by using Series commands. This ID has no default permissions. Users without Permissions can this authorization queue management software to access SeriesRessourcen be granted. Resources that can be protected with the OAM With the OAM you can controlAccess to Series objects through the I.

Administration commands 

When an application program attempts access an object, the queue management software checks if the requesting User ID permission (on the basis of the authorization ID) for this Operation features. This primarily means that queues, and the messages in queues queue line control can be protected against unauthorized access. Object Authority Manager (OAM)Series for Compaq OpenVMS Alpha, Version Release System Administrationpermission to run SC commands. Only principals with the Authorization ID M can for queue managers, for Creating a queue run. Permission to execute control queue line control commands.

 Only principals with the Authorization ID M can execute control commands, ex. As creating a queue manager, starting a command server, or using the command runs. Permission to run PCF commands Different users can have different types of access permissions be issued for the same object. For example, it queue management software can users with an ID are allowed, both PUT and GET operations on a perform specific clicking here queue while users with a different ID only is allowed, the queue to browse (GET with option 'Browse'). Accordingly, users have IDs with maybe about GET and However, for a queue, they are not entitled to the queue To change or delete. Use authorization IDs for Authorization Management By using IDs rather than individual principals for authorization management can the cost of authorization management can be reduced. Typically, a single type of access requested by several principals.

Commands for queue management software 

You can, for example, define an ID for end users, a want queue management software to run certain applications. New users can then easily Be granted access by the relevant ID of the OpenVMS user ID this user is assigned. Try to keep the number of IDs as low as possible. Begin for example, so that the principals in a group for application users and another group of administrators divide. Object Authority Manager inactivate The OAM is enabled by default. You can disable it by following these define the logical name SNOAUT before the Queue manager is created In this case, however, it is usually no longer possible, the OAM to a later date to restart.



The better solution is to OAM does not inactivate, but instead to ensure that all users Have access through an appropriate user ID. You can also disable the OAM for testing purposes queue management software by the stanza for the authorization service from the configuration file Remove queue manager Object Authority Manager (OAM) Chapter. Series objects protectUse OAM Commands The OAM provides a command interface to grant and revoke privileges available. To use these commands, you need appropriate authorization, ie, your user ID must OpenVMSBerechtigungs ID M include.




Today, there have been 1 visitors (1 hits) on this page!
This website was created for free with Own-Free-Website.com. Would you also like to have your own website?
Sign up for free