Introduction

The CoreOne Suite offers different ways to create and manage resources. Approaching the CoreOne Suite’s access management features, it is important to understand which features will be the best match for the use case.

Due to different terminologies used in the target systems supported by the CoreOne Suite, we’ve settled on the terminology “resources”. A resource is a permission that is assignable to an identity within a target system. In the target system Active Directory for example, groups are the equivalent of resources.

This article should aid in deciding between the use of Linked Resources versus Managed Resources.

Step 1 - Understand the differences between resource types

The following documentation is recommended for a better understanding of what resource types are and what the Cleanup Tasks can do:

Step 2 - Understand the limitations when creating new resources

Step 3 - Identify the use case

Where is the resource lifecycle going to be managed?

Using both Management Modes at the same time is also possible. It might be necessary to mange already existing resources as Linked Resources and new ones as Managed Resources, for example.

Frequently Asked Questions

Yes.

No. Objects that are not present in the CoreOne Suite Meta Directory remain untouched during the Cleanup Tasks. See Reconciliation / Cleanup for more details.

The change is not visible to the CoreOne Suite Meta Directory. This will lead to errors in the application. See: System monitoring / Health Check for more details.

Remove any memberships, delete the resource withing the CoreOne Suite Meta Directory, and finally delete the resource in the target system.

The change is not visible to the CoreOne Suite Meta Directory. This will lead to errors in the application.