Security: Difference between revisions
From MXMS Wiki
Jump to navigationJump to search
| Line 27: | Line 27: | ||
== Claims == | == Claims == | ||
== Attributes == | == Attributes == | ||
Another way to limit access is by using the Availability attribute. This attribute defines the maximum available permissions for a property. The options are None, Writeonly and Readonly. | |||
<pre> | <pre> | ||
[Availability(Availability.ReadOnly)] | [Availability(Availability.ReadOnly)] | ||
Revision as of 05:43, 3 April 2026
Roles
A role defines which classes, properties and methods the user has access to. A user can be added in multiple roles and the cummultative permission set of classes, properties and methods will be the users final access profile.
public class ExampleAccessProfile : CodedAccessProfile
{
protected override void Configure()
{
Set<Class1>()
.AllowAllCreate()
.AllowAllUpdate();
Set<Class2>()
.AllowAllCreate()
.AllowAllUpdate()
.AllowDelete();
Set<Class2>()
.AllowAllCreate()
.AllowAllUpdate()
.AllowDelete();
}
}
Claims
Attributes
Another way to limit access is by using the Availability attribute. This attribute defines the maximum available permissions for a property. The options are None, Writeonly and Readonly.
[Availability(Availability.ReadOnly)]
public virtual string Name
{
get; set;
}