Security: Difference between revisions
From MXMS Wiki
Jump to navigationJump to search
| Line 2: | Line 2: | ||
== Roles == | == 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. | 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. | ||
<pre> | |||
public class ExampleAccessProfile : CodedAccessProfile | |||
{ | |||
protected override void Configure() | |||
{ | |||
Set<Class1>() | |||
.AllowAllCreate() | |||
.AllowAllUpdate(); | |||
Set<Class2>() | |||
.AllowAllCreate() | |||
.AllowAllUpdate() | |||
.AllowDelete(); | |||
Set<Class2>() | |||
.AllowAllCreate() | |||
.AllowAllUpdate() | |||
.AllowDelete(); | |||
} | |||
} | |||
</pre> | |||
== Claims == | == Claims == | ||
== Attributes == | == Attributes == | ||
Revision as of 05:38, 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();
}
}