Guide: Entitlement & Eligibility - Revision history

As1844 at 13:39, 3 March 2026

2026-03-03T13:39:58Z

← Older revision		Revision as of 13:39, 3 March 2026
Line 63:		Line 63:
	The given quota flavor name must be within the [[Guide: Project and Quota#List of quota flavors\|list of support project quota flavors]].		The given quota flavor name must be within the [[Guide: Project and Quota#List of quota flavors\|list of support project quota flavors]].

	==== Empty eligibility ====		==== Empty-eligibility ====
	Each user owns this eligibility. This is set for each user within the bwCloud-OS environment and can't be removed from a user. An empty quota entitlement can't be given explicitly. Furthermore, this eligibility, and only this, can be used for multiple projects.		Each user owns this eligibility. This is set for each user within the bwCloud-OS environment and can't be removed from a user. An empty quota entitlement can't be given explicitly. Furthermore, this eligibility, and only this, can be used for multiple projects.

As1844 at 15:53, 27 February 2026

2026-02-27T15:53:25Z

← Older revision		Revision as of 15:53, 27 February 2026
Line 12:		Line 12:

	* Entitlements are strings assigned to a user carrying information about his/her privileges.		* Entitlements are strings assigned to a user carrying information about his/her privileges.
	* Every [[Guide: Entitlement & Eligibility#Quota Entitlements\|quota entitlements]] (which can be seen as a "package") contains an eligibility. After "unpacking", the bwCloud-OS works only with the eligibility.		* Every [[Guide: Entitlement & Eligibility#Quota Entitlements\|quota entitlements]] (which can be seen as a "package") contains an eligibility. After "unpacking", the bwCloud-OS works only with the eligibility. This is kind of a "protocol" to communicate with the [[Guide: Enterprise Resource Planning\|Enterprise Resource Planning (ERP)]].
	* Every user owns at least the [[Guide: Entitlement & Eligibility#Empty Entitlement\|empty eligibility]].		* Every user owns at least the [[Guide: Entitlement & Eligibility#Empty Entitlement\|empty eligibility]].
	* Every [[Projects and Quota\|project]] needs to be linked with an eligibility.		* Every [[Projects and Quota\|project]] needs to be linked with an eligibility.

As1844 at 15:33, 27 February 2026

2026-02-27T15:33:44Z

← Older revision		Revision as of 15:33, 27 February 2026
Line 15:		Line 15:
	* Every user owns at least the [[Guide: Entitlement & Eligibility#Empty Entitlement\|empty eligibility]].		* Every user owns at least the [[Guide: Entitlement & Eligibility#Empty Entitlement\|empty eligibility]].
	* Every [[Projects and Quota\|project]] needs to be linked with an eligibility.		* Every [[Projects and Quota\|project]] needs to be linked with an eligibility.
			* Eligibilities are used in the [[Guide: Charging\|charging process]].

	Every member of a higher education institution in Baden-Württemberg has a personal account. If the institution participates in the federated identity management system ('''bwIDM'''), its members can also apply for the external service bwCloud-OS, by providing additional information. This is handled through the assignment of <code>eduPersonEntitlement</code> to the user's account.		Every member of a higher education institution in Baden-Württemberg has a personal account. If the institution participates in the federated identity management system ('''bwIDM'''), its members can also apply for the external service bwCloud-OS, by providing additional information. This is handled through the assignment of <code>eduPersonEntitlement</code> to the user's account.

As1844 at 15:28, 27 February 2026

2026-02-27T15:28:08Z

← Older revision		Revision as of 15:28, 27 February 2026
Line 9:		Line 9:
	➡️ '''To the [[Guide: Enterprise Resource Planning\|Enterprise Resource Planning]].'''		➡️ '''To the [[Guide: Enterprise Resource Planning\|Enterprise Resource Planning]].'''

	Entitlements in bwCloud-OS define '''who can access the platform''' ([[Guide: ~~Registration~~\|~~Access Control~~]]) and '''how many resources they may use''' '''and under what conditions''' ([[Guide: Entitlement & Eligibility#Eligibility\|Eligibility]]).		Entitlements in bwCloud-OS define '''who can access the platform''' ([[Guide: Conditions of use\|Conditions of Use]]) and '''how many resources they may use''' '''and under what conditions''' ([[Guide: Entitlement & Eligibility#Eligibility\|Eligibility]]).

	* Entitlements are strings assigned to a user carrying information about his/her privileges.		* Entitlements are strings assigned to a user carrying information about his/her privileges.

As1844 at 15:26, 27 February 2026

2026-02-27T15:26:35Z

← Older revision		Revision as of 15:26, 27 February 2026
Line 9:		Line 9:
	➡️ '''To the [[Guide: Enterprise Resource Planning\|Enterprise Resource Planning]].'''		➡️ '''To the [[Guide: Enterprise Resource Planning\|Enterprise Resource Planning]].'''

	Entitlements in bwCloud-OS define '''who can access the platform''' ([[Guide: ~~Entitlement & Eligibility#Access Control~~\|Access Control]]) and '''how many resources they may use''' '''and under what conditions''' ([[Guide: Entitlement & Eligibility#Eligibility\|Eligibility]]).		Entitlements in bwCloud-OS define '''who can access the platform''' ([[Guide: Registration\|Access Control]]) and '''how many resources they may use''' '''and under what conditions''' ([[Guide: Entitlement & Eligibility#Eligibility\|Eligibility]]).

	* Entitlements are strings assigned to a user carrying information about his/her privileges.		* Entitlements are strings assigned to a user carrying information about his/her privileges.

As1844 at 15:24, 27 February 2026

2026-02-27T15:24:13Z

← Older revision		Revision as of 15:24, 27 February 2026
Line 154:		Line 154:
	owner = <nowiki>{{user.eppn}}</nowiki>		owner = <nowiki>{{user.eppn}}</nowiki>
	customer = <nowiki>{{user.home_organization}}</nowiki>		customer = <nowiki>{{user.home_organization}}</nowiki>

	~~=== Eligibility examples ===~~

	~~==== Example eligibility 1 ====~~
	~~The example in the image to the left demonstrates how costs can be accumulated based on cost centers.~~
	~~[[File:Example eligibiliy cost center.drawio.png\|thumb\|Example for eligibility cost centers\|600x600px\|left]]~~

As1844 at 15:17, 27 February 2026

2026-02-27T15:17:56Z

← Older revision		Revision as of 15:17, 27 February 2026
Line 7:		Line 7:
	➡️ '''Back to the FAQ for [[Registration#Entitlements-bwCloud-OS\|Registration & Entitlements]].'''		➡️ '''Back to the FAQ for [[Registration#Entitlements-bwCloud-OS\|Registration & Entitlements]].'''

	➡️ '''To the [[Guide: Enterprise Resource Planning\|~~Enterprise_Resource_Planning~~]] .'''		➡️ '''To the [[Guide: Enterprise Resource Planning\|Enterprise Resource Planning]].'''

	Entitlements in bwCloud-OS define '''who can access the platform''' ([[Guide: Entitlement & Eligibility#Access Control\|Access Control]]) and '''how many resources they may use''' '''and under what conditions''' ([[Guide: Entitlement & Eligibility#Eligibility\|Eligibility]]).		Entitlements in bwCloud-OS define '''who can access the platform''' ([[Guide: Entitlement & Eligibility#Access Control\|Access Control]]) and '''how many resources they may use''' '''and under what conditions''' ([[Guide: Entitlement & Eligibility#Eligibility\|Eligibility]]).

As1844 at 15:12, 27 February 2026

2026-02-27T15:12:45Z

← Older revision		Revision as of 15:12, 27 February 2026
Line 97:		Line 97:

	== Testing ==		== Testing ==
	We provide a [[Guide: ~~REST~~-API ~~for accounting and resource management~~\|~~REST~~-API]] that can be used for validating syntax and checking the interpretation of an entitlement and an eligibility.		We provide a [[Guide: ERP-API\|ERP-API]] that can be used for validating syntax and checking the interpretation of an entitlement and an eligibility.

	== Examples ==		== Examples ==

As1844 at 14:52, 27 February 2026

2026-02-27T14:52:33Z

← Older revision		Revision as of 14:52, 27 February 2026
Line 6:		Line 6:
	\|}		\|}
	➡️ '''Back to the FAQ for [[Registration#Entitlements-bwCloud-OS\|Registration & Entitlements]].'''		➡️ '''Back to the FAQ for [[Registration#Entitlements-bwCloud-OS\|Registration & Entitlements]].'''

			➡️ '''To the [[Guide: Enterprise Resource Planning\|Enterprise_Resource_Planning]] .'''

	Entitlements in bwCloud-OS define '''who can access the platform''' ([[Guide: Entitlement & Eligibility#Access Control\|Access Control]]) and '''how many resources they may use''' '''and under what conditions''' ([[Guide: Entitlement & Eligibility#Eligibility\|Eligibility]]).		Entitlements in bwCloud-OS define '''who can access the platform''' ([[Guide: Entitlement & Eligibility#Access Control\|Access Control]]) and '''how many resources they may use''' '''and under what conditions''' ([[Guide: Entitlement & Eligibility#Eligibility\|Eligibility]]).
Line 19:		Line 21:

	__TOC__		__TOC__


	== Entitlement URN structure ==		== Entitlement URN structure ==
	The institutions are sending two types of entitlements to the bwCloud-OS, quota and access entitlements. Often the term 'entitlement' refers only to the quota entitlements.		The institutions are sending two types of entitlements to the bwCloud-OS, quota and access entitlements. Often the term 'entitlement' refers only to the quota entitlements.

As1844 at 14:49, 27 February 2026

2026-02-27T14:49:49Z

← Older revision		Revision as of 14:49, 27 February 2026
Line 20:		Line 20:
	__TOC__		__TOC__

	~~== Motivation ==~~
	The bwCloud-OS negotiated only contracts with institutions (customers) but not with individual members (users). This is a crucial [[Guide: Charging\|difference compared to other known cloud providers]]. Further, there are several different types of sponsors (e.g., faculties, research projects) located at the institutes that need to be enhanced to manage the resources of sub-groups of their members (e.g., students of a faculty).

	~~=== Access Control ===~~
	For [[registration]] to the bwCloud-OS several [[Guide: Conditions of use\|Condition of use]] need to be fulfilled. By rolling out the [[Guide: Entitlement & Eligibility#Access Control\|access entitlement]] home organizations can manage by themselves who is allowed to access the bwCloud-OS.

	~~=== Automated resource provisioning ===~~
	~~[[Registration]] is streamlined through entitlements:~~
	* Entitlements are automatically evaluated during registration.
	* Users receive immediate access and resources ([[Projects and Quota\|project quota]]) once their entitlement is confirmed. No manual activation is required.

	~~=== Charging ===~~
	~~All consumptions within the bwCloud-OS, within projects, are [[Guide: Charging\|charged]]. Hence, for each project, a customer is required, which differs from the user or owner.~~

	~~Charging will be based on the projects [[Booking Units\|booking units]] (BEH) and will be addressed to the [[Projects and Quota\|project owner]]'s home organization.~~

	~~=== Delegating resposibility ===~~
	~~The institutes can define an internal process so their members can set entitlements in the home IdP.~~

	~~=== Reimbursement ===~~
	~~Entitlements also help define who is financially responsible for producing BEH.~~
	* Defining [[Guide: Entitlement & Eligibility#Cost centers\|cost centers]] to separate costs into [[Guide: Entitlement & Eligibility#Example eligibility 1\|different cost positions]], allowing institutions to reimburse the costs internally.

	* bwCloud-OS will generate aggregated usage reports and invoices per institution—no individual billing.

	~~=== Budget ===~~
	~~Sometimes resources should only be consumed up to a certain level or amount of time.~~

	* [[Guide: Entitlement & Eligibility#Constraints\|Constraints]] can be used to manage the valid period for eligibility.
	* After reaching an eligibility constraint, no more costs can be produced within the associated project.

	~~=== Central eligibility platform ===~~
	The gimmic with the eligibility enhances (later) the bwCloud-OS local support to manage quota privileges within the bwCloud-OS environment. Such a [[Guide: REST-API for accounting and resource management#Eligibility rules\|central service]] could simplify local processes within the customers.

	== Entitlement URN structure ==		== Entitlement URN structure ==

← Older revision		Revision as of 15:17, 27 February 2026
Line 7:		Line 7:
	➡️ '''Back to the FAQ for [[Registration#Entitlements-bwCloud-OS\|Registration & Entitlements]].'''		➡️ '''Back to the FAQ for [[Registration#Entitlements-bwCloud-OS\|Registration & Entitlements]].'''

	➡️ '''To the [[Guide: Enterprise Resource Planning\|~~Enterprise_Resource_Planning~~]] .'''		➡️ '''To the [[Guide: Enterprise Resource Planning\|Enterprise Resource Planning]].'''

	Entitlements in bwCloud-OS define '''who can access the platform''' ([[Guide: Entitlement & Eligibility#Access Control\|Access Control]]) and '''how many resources they may use''' '''and under what conditions''' ([[Guide: Entitlement & Eligibility#Eligibility\|Eligibility]]).		Entitlements in bwCloud-OS define '''who can access the platform''' ([[Guide: Entitlement & Eligibility#Access Control\|Access Control]]) and '''how many resources they may use''' '''and under what conditions''' ([[Guide: Entitlement & Eligibility#Eligibility\|Eligibility]]).