Known issues in External Content Library
The following list describes issues known to exist in the External Content Library (ECL) feature.
- Bearer Token authentication does not work correctly on the ECL Service's Basic HTTP endpoint
-
The ECL Service on basic HTTP endpoint does not yet completely support authentication through Access Management. When using Bearer Token authentication, only a user's internal group memberships, defined in Content Manager, are taken into account. External mapped claims from Access Management are not currently available with this form of authentication.
To use the ECL Service HTTP endpoint, you can use Windows and Basic authentication instead of Access Management.
- ECL does not fully respect BluePrinting when determining whether a Category is External
-
In order to determine whether a Category is External or not, ECL compares the Category ID against the configured Stub Category IDs (for all Mount Points). To support BluePrinting, the comparison is done on the Item Reference ID only, that is, the middle part of the TCM UR. This ensures that a Category is also recognized as External Category in child Publications of where the mount point is configured.
The current approach, however, also matches on parent Publications of the Publication where the mount point is configured. Under most circumstances, this is not a problem, but in some instances, it can lead to misleading or confusing errors. The desired behavior, which is also consistent with how ECL generally resolves BluePrint items, is to not resolve the Mount Point higher in the BluePrint than where it is configured.
- Bundle Workflow not working for ECL items when Schema is localized
- If you localize an ECL Schema and apply the workflow option that Any changes made to this Component should be approved by Bundle Workflow process, and you subsequently edit and save a Distribution based on the Schema, you are not prompted to add the Distribution to a Bundle. The Distribution remains checked out and you will not be able to open it.