> For the complete documentation index, see [llms.txt](https://docs.xibosignage.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.xibosignage.com/kb/player-app/automate-cms-credentials-for-samsung-tizen-soc.md).

# Automate CMS credentials for Samsung Tizen SoC

Once configured, connect a USB to your Samsung Soc for an easier way to provide CMS credentials. Follow the steps to automate credentials on Player start up.

### Create JSON file

You will need to create a JSON file, named `cms_settings.json` that will contain the credentials you want to pass to the monitor.

Below is the correct format for that JSON file:

```
{
"CMSUrl":"http://yourCMSUrl",
"CMSPassword":"yourCMSPassword",
"CMSEmail":"your@email.com"
}
```

If you do not have a License Pool when installing your player, leave it as `""`

### USB setup

The `cms_settings.json` file must be saved to the root directory of your USB.

{% hint style="info" %}
When following the steps for a USB installation, this JSON file must be saved to the root directory on the USB device and not in the SSSP folder for the player WGT.
{% endhint %}

### Automate credentials

On installation or restart, the Player will start automatically.

You will see the credentials for your CMS pre-populated on the **Connect to CMS** page.

{% hint style="info" %}
The Player will automatically check for these credentials as long as the CMS address and CMS Key fields are empty.
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.xibosignage.com/kb/player-app/automate-cms-credentials-for-samsung-tizen-soc.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.