Assignment Context
- Silvan Grüter
- Witold Wabik
Introduction
Starting from version 6, the CoreOne Suite supports the assignment of roles and resources in the context of a context type. For example take the CoreOne Suite Legal Entity Delete resource. This resource gives the user the right to delete a legal entity / company and needs a context. Without the context, the system does not know for which legal entity / company the user possesses the right. Therefore you can assign this resource to a Core Identity in the context of a organizational unit, which technically represents the legal entity / company.
Another example would be a tax application where one user can do the taxes for another user. In this case you would probably have a submit taxes resource that you can assign to others in the context of a user. So user A gives user B the right to do his taxes. In this case user B would get the submit taxes resource in the context of user A.
Context Type
Currently the following context types are supported.
Id | Context Type | Description |
|---|---|---|
1 |
| The assignment is made in the the context of an Organizational unit. |
2 |
| The assignment is made in the context of another user. A specific user or identity is uniquly identifiable in the CoreOne Suite Meta Directory as the combination of the Core Identity and the Identity type. |
3 |
| The assignment is valid in all context. |
Supported Target Systems
Even tough you can select the assignment context for all resources and roles, not all target system will be able to actually store that information. Thus far, only the following systems will be able to handle it:
CoreOne Authentication Service
MS SQL Database
Oracle Database
SCIM
© ITSENSE AG. Alle Rechte vorbehalten. ITSENSE und CoreOne sind eingetragene Marken der ITSENSE AG.