# Ansible Jewel: Connecting Ansible services

**URL:** <https://forum.ansible.com/t/ansible-jewel-connecting-ansible-services/45774>\
**Category:** Project Discussions\
**Tags:** ansible-ui, jewel, awx-modernization, awx\
**Created:** [May 6, 2026, 5:25pm UTC](https://forum.ansible.com/t/ansible-jewel-connecting-ansible-services/45774 "2026-05-06T17:25:57Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![john.westcott.iv](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/john.westcott.iv/32/95_2.png) [@john.westcott.iv](https://forum.ansible.com/u/john.westcott.iv)\
**Post date:** [May 6, 2026, 5:25pm UTC](https://forum.ansible.com/t/ansible-jewel-connecting-ansible-services/45774/1 "2026-05-06T17:25:57Z")

</div>

Hi everyone, I’m John. Today I’d like to introduce the [`ansible/jewel`](https://github.com/ansible/jewel) project.

## What is Ansible Jewel?

Ansible Jewel is a centralized authentication, authorization, and proxy layer for Ansible services. Ansible Jewel intercepts user requests, authenticates them, and routes traffic to the appropriate Ansible service.

## A brief introduction

Ansible Jewel performs web authentication via a pluggable Django framework (currently provided by the [`ansible/django-ansible-base`](https://github.com/ansible/django-ansible-base) project) with a Role-Based Access Control (RBAC) system to grant permissions for web requests.

Ansible Jewel then forwards user requests to Ansible services with signed JSON web tokens (JWT). This allows Ansible services to validate requests and control access based on user permissions that Jewel provides.

## Ways to contribute

We’re excited to announce the [`ansible/jewel`](https://github.com/ansible/jewel) project. We welcome contributions of all kinds and have some suggestions for anyone looking to get involved:

- **New authentication backends** — SAML, OIDC, LDAP, and TACACS+ are some of the supported authentication methods that already exist; we’d love to see more
- **Performance optimizations** — proxy throughput, JWT validation, cache efficiency
- **Documentation and examples** — tutorials and deployment guides
- **Bug reports and fixes** — especially around edge cases in authentication flows

## How to contribute

Check out our [CONTRIBUTING.md](https://github.com/ansible/jewel/blob/devel/CONTRIBUTING.md) to dive in and join us.

## Useful links

- Forum: [Jewel topics](https://forum.ansible.com/tag/jewel/)
- Source: [Jewel repository](https://github.com/ansible/jewel)

---

<div class="post-metadata">

**Author:** ![MalfuncEddie](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/malfunceddie/32/428_2.png) [@MalfuncEddie](https://forum.ansible.com/u/MalfuncEddie)\
**Post date:** [May 21, 2026, 2:00pm UTC](https://forum.ansible.com/t/ansible-jewel-connecting-ansible-services/45774/2 "2026-05-21T14:00:23Z")

</div>

I see in the makefile refferences to [quay.io/ansible/platform-ui:latest](http://quay.io/ansible/platform-ui:latest) bit that does not exist?

---

<div class="post-metadata">

**Author:** ![jon-nfc](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/jon-nfc/32/10748_2.png) [@jon-nfc](https://forum.ansible.com/u/jon-nfc)\
**Post date:** [May 22, 2026, 8:13am UTC](https://forum.ansible.com/t/ansible-jewel-connecting-ansible-services/45774/3 "2026-05-22T08:13:01Z")

</div>

I asked about the same in another post → [AWX modernization: Ansible Jewel - #2 by jon-nfc](https://forum.ansible.com/t/awx-modernization-ansible-jewel/45775/2). Along with being able to have official builds as well as currently there are none.