Versions Compared

Version Old Version 19 New Version 20
Changes made by

Magnus Frank

Troels Holm

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Digizuite authentication is done using users

All API access requires that the user is authenticated. Regardless of whether you are using basic authentication (username, password) or going through a token issuer like ADFS, you need to generate an AccessKey which is used to authorize access, based on users, groups, access rights and roles. A user logs into Digizuite and based on the user rights an access key is generated. This access key grants access to the system and it’s features.The access key The AccessKey determines what assets and metadata you can access in the DAM Center.

The AccessKey is a guid and the accesskey refers to the a specific user, a language and a product. The first two are self-explanatory, however, the latter is not. Digizuite is a backend and various products may be attached to this backend. Examples of products are Media Manager or DAM For Sitecore. Each product might be Digizuite™ Media Manager or Digizuite™ DAM For Sitecore - or any other product controlled by the DAM Center. Each product has it’s own set of configuration and in order to access that specific configuration a product specific access key is needed.  

A product is simply a definition in Digizuite. To this definition several concepts can be attached. First, a product has a ConfigManager. A ConfigManager is for changing product specific configuration such as configuration parameters and searches. Secondly, most products have a channel (layoutfolder), which is a distribution channel for assets.

Lastly, Digizuite has two types of metadata, configuration metadata and asset metadata. The first is versioned and the latter is not. This means that there is a difference between what metadata you are getting in the API and this is also decided in the accesskey.

Product configuration controlled by the AccessKey:

  • Specific product configuration that vary by product and by site distribution (e.g. splash screen options in Media Manager)
  • Configurable searches (think saved searches that are unique per product).
  • Channel folder layout (e.g. for controlling access rights per distribution).

An AccessKey is bound and cannot be used across products and / or distributions. This means that an AccessKey for Media Manager cannot be used towards DAM For Sitecore. Or an AccessKey for Media Manager site X cannot be used towards Media Manager site Y. 

All login specific operations are done using the ConnectService endpoint. There are two important methods on this endpoint: LogOn and LogOnWithAccessKeyOptions.


Table of Contents