...
| Table of Contents | ||||
|---|---|---|---|---|
|
Theory
Resources in the CoreOne Suite are nothing else than a Group in an Active Directory. Due to different Terminations in all our supported target systems, we decided to use the termination “Resources”. Simple said: A Resource is a right you can assing to an Identity in a Target System. In an Active Directory it is a Group (Resource) where you add a user (Identity) as member. This results in a right.
Linked Resources
Linked Resources are the most used type of resources. With linked Resources
Pro’s & Con’s
Managed Resources
Pro’s & Con’s
What they don’t do
They won’t be added automatically as Resource in the CoreOne Suite, if you create them directly in the target system.
Linked Resources: You have to link the newly created Active Directory Group in the CoreOne Suite Admin UI to be able, to assign it to a Core-Identity. See: /wiki/spaces/IKB/pages/1796997245
Managed Resources: You’ve chosen the wrong way. It is not possible to use this Group. You have to delete it in the target system and recreate it in the CoreOne Suite Admin UI and the CoreOne Suite creates the Group in the target system automatically. See: /wiki/spaces/IKB/pages/1796997245
Frequently Asked Questions
| Expand | ||
|---|---|---|
| ||
Technically: Yes you can. Logically: It’s not that simple. For Example: The IAM Manager’s goal is to create a new Active Directory Group. In some OU-Path’s where you work with Linked Resources he have to do that directly in the target system Active Directory. For an another OU-Path where you work with Managed Resources he have to get the job done through the Admin UI of the CoreOne Suite. |
We recommend, to focus on one type. We observed, that new IAM Manager’s are often confused, if there are different ways, of how they have to handle rights. ...