Security - Revision history

Bjorn: /* Attributes */

2026-04-03T06:14:25Z

Attributes

← Older revision		Revision as of 06:14, 3 April 2026
Line 30:		Line 30:

	== Attributes ==		== Attributes ==
	To further limit access if access modifiers are not feasible is by using the [[Availability (attribute)\|~~Availability~~]] ~~attribute~~. This attribute defines the maximum available permissions for a property. The options are None, Writeonly and Readonly.		To further limit access if access modifiers are not feasible is by using the [[Availability (attribute)\|availability attribute]]. This attribute defines the maximum available permissions for a property. The options are None, Writeonly and Readonly.

	<pre>		<pre>

2026-04-03T06:13:15Z

Access modifiers

← Older revision		Revision as of 06:13, 3 April 2026
Line 26:		Line 26:
	}		}
	</pre>		</pre>

			In the example above the property maximum availability is read access.

	== Attributes ==		== Attributes ==

2026-04-03T06:12:51Z

Attributes

← Older revision		Revision as of 06:12, 3 April 2026
Line 37:		Line 37:
	}		}
	</pre>		</pre>

			In the example above the property maximum availability is read access.

	== Roles ==		== Roles ==

2026-04-03T06:12:16Z

Roles

← Older revision		Revision as of 06:12, 3 April 2026
Line 47:		Line 47:

	Set<Class1>()		Set<Class1>()
	.~~AllowAllCreate()~~		.AllowAllRead();
	~~.AllowAllUpdate~~();

	Set<Class2>()		Set<Class2>()
Line 56:		Line 55:

	Set<Class2>()		Set<Class2>()
	~~.AllowAllCreate()~~		.AllowAllUpdate();
	.AllowAllUpdate()
	~~.AllowDelete~~();
	}		}
	}		}
	</pre>		</pre>

			In the example above the role has read access to Class1, has full control access to Class2 and update access to Class3. Read access is automatically granted when providing update access.

	== Claims ==		== Claims ==

2026-04-03T06:09:43Z

Rights by definition type

← Older revision		Revision as of 06:09, 3 April 2026
Line 11:		Line 11:
	\| [[Entity\|Entities]] \|\| Create, Read, Update and Delete		\| [[Entity\|Entities]] \|\| Create, Read, Update and Delete
	\|-		\|-
	\| Properties \|\| Create, Read and Update		\| [[Property\|Properties]] \|\| Create, Read and Update
	\|-		\|-
	\| [[Method\|Methods]] \|\| Execute		\| [[Method\|Methods]] \|\| Execute

2026-04-03T06:09:06Z

Rights by definition type

← Older revision		Revision as of 06:09, 3 April 2026
Line 9:		Line 9:
	! Type !! Permissions		! Type !! Permissions
	\|-		\|-
	\| Entities \|\| Create, Read, Update and Delete		\| [[Entity\|Entities]] \|\| Create, Read, Update and Delete
	\|-		\|-
	\| Properties \|\| Create, Read and Update		\| Properties \|\| Create, Read and Update
	\|-		\|-
	\| Methods \|\| Execute		\| [[Method\|Methods]] \|\| Execute
	\|}		\|}

2026-04-03T06:08:21Z

Claims

← Older revision		Revision as of 06:08, 3 April 2026
Line 64:		Line 64:

	== Claims ==		== Claims ==
	[[Claim\|Claims]] is another form to limit access to properties or methods. By adding a claim the entity's state determines if the policy is added.		[[Claim\|Claims]] is another form to limit access to properties or methods. By adding a claim the entity's state determines if the policy is added. Claims are registered and added to the application using [[Module\|modules]].

	<pre>		<pre>

2026-04-03T06:08:04Z

Roles

← Older revision		Revision as of 06:08, 3 April 2026
Line 39:		Line 39:

	== Roles ==		== Roles ==
	A [[Role\|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\|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. Roles are registered and added to the application using [[Module\|modules]].
	<pre>		<pre>
	public class ExampleAccessProfile : CodedAccessProfile		public class ExampleAccessProfile : CodedAccessProfile

2026-04-03T06:05:39Z

← Older revision		Revision as of 06:05, 3 April 2026
Line 1:		Line 1:
	~~= lkjsflkdsf dslkfjdsl f =~~		Various concepts are in place to either grant or deny users specific access to the application.
	Various concepts are in place to either grant or deny users specific access to the application. The following permissions are available for each type.
			== Rights by definition type ==
			The following permissions are available for each type.

	{\| class="wikitable"		{\| class="wikitable"

2026-04-03T06:04:32Z

Attributes

← Older revision		Revision as of 06:04, 3 April 2026
Line 26:		Line 26:

	== Attributes ==		== Attributes ==
	To further limit access if access modifiers are not feasible is by using the Availability attribute. This attribute defines the maximum available permissions for a property. The options are None, Writeonly and Readonly.		To further limit access if access modifiers are not feasible is by using the [[Availability (attribute)\|Availability]] attribute. This attribute defines the maximum available permissions for a property. The options are None, Writeonly and Readonly.

	<pre>		<pre>