Who should use HTTP Header Authentication for Jira?

HTTP Header Authentication for Jira is a B2B product built for Jira Server and Data Center administrators.

Is HTTP Header Authentication for Jira free?

No — HTTP Header Authentication for Jira is paid.

What platforms does HTTP Header Authentication for Jira run on?

HTTP Header Authentication for Jira runs on the web. It can also be self-hosted.

Is HTTP Header Authentication for Jira still active?

Unverified. HTTP Header Authentication for Jira has not been re-checked since it entered the index, so there is no finding either way — and only a positive finding would say otherwise.

What are alternatives to HTTP Header Authentication for Jira?

Similar projects tracked by PulseGate include HTTP Header Authentication for Confluence, Enhanced API Authentication, and API Token Authentication.

Who makes HTTP Header Authentication for Jira?

HTTP Header Authentication for Jira is developed by resolution Reichert Network Solutions GmbH, based in Germany.

Does HTTP Header Authentication for Jira have an API or integrations?

Yes — HTTP Header Authentication for Jira exposes a public API.

Back to the index

HTTP Header Authentication for Jira

Name: HTTP Header Authentication for Jira
Author: resolution Reichert Network Solutions GmbH

atlassian.comAuth & identity🇩🇪

HTTP Header Authentication for Jira passes an authenticated user ID from a reverse proxy to Jira through an HTTP header. It is distributed as a JAR file for Jira Server and Data Center deployments and supports automatic user login.

PaidWebSelf-hosted

HTTP Header Authentication for Jira preview

Visit atlassian.com

Overview

7 features

HTTP Header Authentication for Jira is an Auth & identity project. It focuses on passing reverse-proxy authentication into Jira so users can access Jira without a separate login. HTTP Header Authentication for Jira is a B2B product aimed at Jira Server and Data Center administrators. HTTP Header Authentication for Jira is paid. HTTP Header Authentication for Jira is available on the web, and it can be self-hosted.

Behind HTTP Header Authentication for Jira is resolution Reichert Network Solutions GmbH, based in Germany. Among its 7 catalogued features are header authentication, automatic login, and reverse proxy support. It exposes integrations via a public API.

Summary written by a language model from the project’s public pages.

Header authentication
Automatic login
Reverse proxy support
Jira Server support
Jira Data Center support
JAR download
Admin documentation

Built with & integrations

Hosting

AWS

Connectors

API

Runs on

BrowserSelf-hosted

Detected from

AWS: x-amz-cf-id header · x-amz-cf-pop header · via header

Trust & compliance

Verified signals

HTTPSPrivacy Policy Terms of Service

Legal

Indexing history

What PulseGate has recorded for this listing

Indexed6 Sept · 19:10 UTC
HTTP Header Authentication for Jira verified via Atlassian Marketplace
Source: Atlassian Marketplace · Open

Frequently asked questions about HTTP Header Authentication for Jira

What does HTTP Header Authentication for Jira do?: HTTP Header Authentication for Jira focuses on passing reverse-proxy authentication into Jira so users can access Jira without a separate login. It is catalogued under Auth & identity on PulseGate.
Who should use HTTP Header Authentication for Jira?: HTTP Header Authentication for Jira is a B2B product built for Jira Server and Data Center administrators.
Is HTTP Header Authentication for Jira free?: No — HTTP Header Authentication for Jira is paid.
What platforms does HTTP Header Authentication for Jira run on?: HTTP Header Authentication for Jira runs on the web. It can also be self-hosted.
Is HTTP Header Authentication for Jira still active?: Unverified. HTTP Header Authentication for Jira has not been re-checked since it entered the index, so there is no finding either way — and only a positive finding would say otherwise.
What are alternatives to HTTP Header Authentication for Jira?: Similar projects tracked by PulseGate include HTTP Header Authentication for Confluence, Enhanced API Authentication, and API Token Authentication.HTTP Header Authentication for Confluence Enhanced API Authentication API Token Authentication
Who makes HTTP Header Authentication for Jira?: HTTP Header Authentication for Jira is developed by resolution Reichert Network Solutions GmbH, based in Germany.
Does HTTP Header Authentication for Jira have an API or integrations?: Yes — HTTP Header Authentication for Jira exposes a public API.

At a glance

Pricing: Paid · pricing page detected
Platforms: Web · API
Languages: English
First seen: 6 Sept 2026
Built for: Jira Server and Data Center administrators
Model: B2B
Solves: Passing reverse-proxy authentication into Jira so users can access Jira without a separate login.

Registered as

Atlassian Marketplace: de.resolution.httpheaderauth.jira

Developer

🇩🇪resolution Reichert Network Solutions GmbH

Index record

Indexed: 6 Sept 2026
Lifecycle: Alive
First seen: Sept 2026
Last seen: 6 Sept 2026

Identity audit (13)

Slug: http-header-authentication-for-jira-atlassian-com
Lifecycle state recorded: 6 Sept 2026
Verification state: Indexed for public listing
Listing state: Listed: yes
Index status: Included in index
Latest evidence snapshot: 6 Sept 2026
Timeline basis: Indexed-at chronology (no inferred launch/funding milestones).
Name from: Derived from the project's own page and URL.
Category from: Assigned by a language model.
Summary from: Written by a language model from public pages.
Languages from: Detected by a language model, checked against the page's own declaration.
Last updated: 6 Sept 2026
Canonical URL: https://marketplace.atlassian.com/apps/1221625/http-header-authentication-for-jira

Ship this? Send a correction — no account, and you get a link to follow it.

Similar projects

Closest matches by what these projects do