How to configure a THRON Custom Application Manager

Business Case:

KPI to be measured

Bookmark this resource Follow

Ask a question

Was this article helpful? 0 out of 0 found this helpful

The following approach is recommended for integration projects involving the upload of content to THRON from an external source.
The first step is to identify the public folder in which the content will be published. On this folder it is important to ensure that all the stakeholders, whether users or groups, have access to the content with their own set of access rights.
Once the folder has been identified, it is necessary to install a THRON Custom Application Manager on it, whose credentials will be used to authenticate to THRON and obtain the token with which to upload the content.

To install a THRON Custom Application Manager, select the folder and then click on the "+" button in the Cockpit menu; then click on "THRON Custom Application Manager". You will be shown a modal where you will have to put a name and a prettyID for the application. Make sure the correct folder is selected in the dropdown:




Once the application has been activated you will be redirected to its configuration panel.

In this screen, make sure you undertake the following steps:





  1. Take note of the appId, as it will be used to perform authentication and invoke web services
  2. Under "Content Management", make sure you select "Can create new content", and the choose the user that will be impersonated by the app to perform content upload. Basically, it will be the owner of the uploaded content. You can either choose the application's owner (default), or a different user. Choose this second if you want to avoid notifications on such content. In either case, take note of the username, since it will be used to perform authentication.
  3. Scroll down and take note of the appKey, as it will be used to perform a secure authentication and invoke web services.

Now the set up is complete, you can use the application to invoke web services and perform integrations.

The first thing to do is to obtain a valid token via application, the procedure is illustrated in this article. To do that, you will have to invoke a su web service, which is a POST request that will return you a token that must be used in all the subsequent requests. The url of the request is structured as follows:



Required parameters are: your clientId, which is the domain name used to access THRON, the appId and appKey you previously took note of and the username of the user selected during app’s configuration.


  "clientId": "",
  "appId": "",
  "username": "",
  "appKey": ""


In the response you will obtain a token that must be used in all the subsequent requests.


Create a pkey to share content


Through the Management of this application you can create a pkey which can be used to publish all and only the contents in the folder and its subfolders. To do so, refer to the "Create new sharing" section, and click on the "Add sharing" button.



This procedure will trigger the creation of an embed script which can be copied and paste into any project, you can make two choices:

  1. Create a Public Sharing: A pkey will be generated that will allow access to all the content within the folder without restriction, the embed made with this pkey will be public and the content will be indexed by search engines.
  2. Create a Secure Sharing: The content will be delivered only if a valid user token is provided. It ensures the privacy of the content which will not be indexed by search engines.





Select the Template to be used by the specific embed and click on "Confirm".

In the following example we have created a Public Sharing, subject to a pkey which is visible both in the upper part of the modal and within the script under the "sessId" parameter. The only dynamic part of the provided script is the "xcontentId" which can be filled with the id of the specific content to be embedded (must be a content of the folder).





The validity of the pkey can be controlled with just one click by using the checkbox in the Management of the application, if turned off, all the embeds will no longer be available on your channels.



The pkey can also be used as a parameter for all the /public web services in order to include content into pages.

Was this article helpful?
0 out of 0 found this helpful

Have any question?

Open a ticket