Graylog2 / Graylog2/graylog2-server

Support Bearer Tokens for authenticating instead of using a token in basic auth

Open
#5,167 2 comments 2 reactions 0 assignees View on GitHub
feature good first issue triaged
Dominant language
Java
Stars
8.1k
Forks
1.1k
Avg merge
1d 20h
Merged PRs (30d)
217

Description

## Expected Behavior

When a user creates a token which can be used for authentication, it should be accepted by the server when passed as part of a `Authentication: Bearer ` header.

## Current Behavior

For token authentication, the server expects basic auth with the username set to the token and password to `token`. This is rather proprietary. Additionally, some systems which are otherwise capable of speaking to Graylog (e.g. the [telegraf prometheus plugin](https://github.com/influxdata/telegraf/tree/master/plugins/inputs/prometheus) speaking to the [Graylog prometheus metrics reporter](https://github.com/graylog-labs/graylog-plugin-metrics-reporter/tree/master/metrics-reporter-prometheus) do not work due to the nonacceptance of Bearer Tokens.

## Possible Solution

## Steps to Reproduce (for bugs)

1.
2.
3.
4.

## Context

## Your Environment

* Graylog Version:
* Elasticsearch Version:
* MongoDB Version:
* Operating System:
* Browser version:

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.