Security Configuration Object

The security configuration object contains the key or token that your client requires to access Composer.

Logi Analytics recommends using Trusted Access for all embed-related workflows.

• When you generate a security key for a data source, users of the data source are automatically granted Read permission for all existing visuals using the data source, but not for any new visuals created after the security key was generated. Instead, a new security key must be generated for new visuals.

• When you generate a security key for a dashboard, users of the dashboard are automatically granted Read permission for all existing visuals on the dashboard for which they have Read permissions. However, if a new visual is created on the dashboard after the security key is generated, dashboard users will not automatically be granted Read permission for the new visual. Instead, a new security key must be generated for newer visuals on the dashboard. )

Example

   var credentialsConfig = {   
   key: '1234567890abcdef'   
   };  

The security configuration object should have only one of the following options.

• key : valid Composer security key; for steps to generate a security key, see Generate a Security Key . The client created will have credentials matching those used to create the security key.
• access_token: OAuth token for accessing the Composer server; for steps to generate an OAuth token, see Request an Access Token. The client created will have credentials matching those used to create the OAuth token.