> For the complete documentation index, see [llms.txt](https://docs.vitaracharts.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.vitaracharts.com/faq/secure-vitara-license-file.md).

# Secure Vitara license file

#### How to protect VitaraCharts license on the network and allow access to specific users <a href="#how-to-protect-vitaracharts-license-on-the-network-and-allow-access-to-specific-users" id="how-to-protect-vitaracharts-license-on-the-network-and-allow-access-to-specific-users"></a>

By default access to the vitara license from client browsers is left open using a URL of the format below.

<http://host\\_name:port/MicroStrategy/plugins/VitaraCharts/license.txt>

However, access to the vitara license can be blocked by implementing the security constraints in the web.xml file. The web.xml file will be available in the following directory.

/\<Webserver>/webapps/MicroStrategy/WEB-INF/

Edit the **web.xml** file and copy and paste the below given security constraint just before the closing \</web-app> tag.

```
  <security-constraint>
          <display-name>Security constraint for Vitara license</display-name>
          <web-resource-collection>
              \** <web-resource-name>Protected Area</web-resource-name> \** 
              <url-pattern>/plugins/VitaraCharts/license.txt</url-pattern>
          </web-resource-collection>
          <auth-constraint>
              <!--uncomment role-name to allow access for specific roles-->
              <!-- <role-name>admin</role-name> -->
          </auth-constraint>
          <user-data-constraint>
              <transport-guarantee>NONE</transport-guarantee>
          </user-data-constraint>
  </security-constraint>
```

At this point, the file is not accessible to any user. Now you need to make sure the right role still has access to this file

* Uncomment the role-name tag in the auth-constraint section
* Replace “admin” with the right tomcat role corresponding to your MicroStrategy Web application deployment.

Save and close the **web.xml** file and restart the webserver.

For your reference, below is the screenshot of the **web.xml** file after adding the above security constraint code.

<figure><img src="https://230207405-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FOuiTPVEbVQnzR38vviPf%2Fuploads%2F9IwOSk1Mio5Zhk4OCPan%2Fimage.png?alt=media&amp;token=fc490871-408e-4130-8566-3a9c49f46762" alt=""><figcaption></figcaption></figure>


---

# 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.vitaracharts.com/faq/secure-vitara-license-file.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.