Cheap mobile adult chat - Updating file authorization lists

Using the Change Object Owner (CHGOBJOWN) command, you can transfer ownership to another user’s profile or to a group profile.

Forexample, when I develop an application for my company’s enterprise resource planning (ERP) system, I change its ownership to the group profile associated with the system’s users. (Security officers, of course, have *ALL authority over all objects.)Using the Work with Objects (WRKOBJ) command, or the specific object authority commands, you can grant (with the Grant Object Authority [GRTOBJAUT] command), revoke (with the Revoke Object Authority [RVKOBJAUT] command), or modify (with the Edit Object Authority [EDTOBJAUT] command) an object’s specific authorities.

It seems redundant to point out that you should be careful when granting *ALL authority.

You’ll understand why when your transaction history file mysteriously disappears.*CHANGE lets the user or group profile change the object, but this authority means slightly different things for different types of objects.

For example, the user can clear, read, or change the records in a database file.

There are so many features and options that it seems impossible to determine how applications will interact with objects. How will their security attributes affect their access to other objects? *ALL means you can access anything; *CHANGE lets you change objects; *USE lets you use the object; and finally, *EXCLUDE means you can’t access anything. I’m sure I don’t know, but I have a guess. Every object in the system has its own list of authority attributes.

The AS/400 allows four basic types of access to objects. Department of Defense is (and almost always has been) the single largest purchaser of computer equipment in the world. If you think about it, discretionary resource control and isolation basically mandate object-level security.

Simply put, object-level security allows you to control not only access to objects but also the type of access users have. In order to obtain a C2 rating, a system has to meet strict criteria in the areas of access control, user accountability, security auditing, and resource isolation.

This article will help you establish a working understanding of object-level security and what paths applications will take when accessing objects. It may interest you to know that the AS/400 is the first system with an integrated database to meet the department’s criteria for its C2 level of security.

The good news is this: While there is a lot to know about the AS/400’s security features, you can understand how to configure those features.

These can all be applied at the user, group, or authorization-list level. This list is, in essence, a description of who can do what with the object.

Tags: , ,