<commit_before>---
title: Managing Chronograf security

aliases: /chronograf_1_4/security-best-practices/

menu:
  chronograf_1_4:
    menu: Managing security
    weight: 50
    parent: Administration
---

**On this page**

* [Chronograf security](#chronograf-security)
* [Using JWT with OAuth 2.0 protocols](#using-jwt-with-oauth-2-0-protocols)
  * [JWT Signature](#jwt-signature)
  * [GitHub](#github)
  * [Google](#google)
  * [Heroku](#heroku)
  * [Auth0](#auth0)
  * [Generic](#generic)
  * [Optional: Configuring authentication duration](#optional-configure-authentication-duration)
* [TLS](#tls)
  * [Using HTTPS and TLS with Chronograf applications](#using-https-and-tls-with-chronograf-applications)
  * [Testing with Self-Signed Certificates ](#testing-with-self-signed-certificates)

## Chronograf security

Chronograf provides two mechanisms for enhancing the secruity of your applications:

* JWT with OAuth 2.0
* HTTPS and TLS (Transport Layer Security)

OAuth 2.0 protocol is used for managing Both of these mechanisms are described below.<commit_msg>updated security content<commit_after>---
title: Managing Chronograf security

aliases: /chronograf_1_4/security-best-practices/

menu:
  chronograf_1_4:
    menu: Managing security
    weight: 50
    parent: Administration
---

**On this page**

* [Chronograf security](#chronograf-security)
* [Using JWT with OAuth 2.0 protocols](#using-jwt-with-oauth-2-0-protocols)
  * [JWT Signature](#jwt-signature)
  * [GitHub](#github)
  * [Google](#google)
  * [Heroku](#heroku)
  * [Auth0](#auth0)
  * [Generic](#generic)
  * [Optional: Configuring authentication duration](#optional-configure-authentication-duration)
* [TLS](#tls)
  * [Using HTTPS and TLS with Chronograf applications](#using-https-and-tls-with-chronograf-applications)
  * [Testing with Self-Signed Certificates ](#testing-with-self-signed-certificates)

## Chronograf security

Chronograf includes two mechanisms for enhancing the secruity of your applications:

* JWT with OAuth 2.0
* HTTPS and TLS (Transport Layer Security)

OAuth 2.0 protocol is used for managing Both of these mechanisms are described below.
{'fraction_non_alphanumeric': 0.12225851609892674, 'fraction_numerical': 0.014932337844143724, 'mean_word_length': 4.90633608815427, 'pattern_counts': {'":': 0, '<': 3, '<?xml version=': 0, '>': 3, 'https://': 0, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '6612189', 'n_tokens_mistral': 706, 'n_tokens_neox': 653, 'n_words': 177}