Security Profiles
A security profile contains permissions for a set of groups and users.
If an object is not given public read access, a user will not be able to see the object unless specifically granted access as a user or as a member of an application group in the security profile for that object.
Access to objects in Meta Data Services is based on the access type in the security profile associated with the object. If an object is not given public read access, a user will not be able to see the object unless specifically granted access as a user or as a member of an application group in the security profile for that object.
In the example in Figure 11, Mary, Fred and all users in the Acct and Payroll Application Groups have read permission to databases A and B. Fred and all the users in the Payroll Application Group can update objects corresponding to databases A and B.
Lucy and all users in the Application Group Acct have read and write access to databases C and D. No other users can view these databases.
Figure 11: Example Security Profiles
It is possible for a user to have multiple privileges defined in the profile. In the above example, user Mary has been granted explicit Read rights. If Mary is also a member of the Payroll group, she will also have Full rights. The user will be granted the highest level of rights (in this case, Full rights).
There is a special term that can be used to define rights in a security profile. The term is “Everyone.” Everyone specifies permissions for anyone connecting to the MDS repository.