Yellow JackIntegration guides
Step-by-step guides for connecting Yellow Jack to services you already run.
A guide is marked tested only when an e2e leg runs it against the real service. A guide that has not been run that way is listed as not yet tested and has no steps here, because steps nobody has run are guesses.
Package registries
How to put Yellow Jack behind a registry you run (as the upstream of its proxy repositories) or in front of it (as the address your clients use). The two positions stop different things; each guide says what the gate sees in each one.
| Registry | Status | Guide |
|---|---|---|
| Nexus Repository Community Edition 3.96.4 | Tested by e2e/registry_nexus.sh (2026-10-05): npm, PyPI and Docker behind Nexus; npm and Docker in front. PyPI in front is not supported |
registry-nexus.md |
| Harbor v2.15.2 | Tested by e2e/registry_harbor.sh (2026-10-05, run locally, not in CI): images behind Harbor and in front. |
registry-harbor.md |
| JFrog Artifactory | Not yet tested. JFrog Container Registry 7.161.26, the free edition that was run, reports only the docker and properties add-ons, so it has no npm or PyPI repositories, and it refuses repository creation through the REST API (“available only in Artifactory Pro”). Artifactory OSS was not run |
— |
Console sign-in (OIDC)
The console’s OIDC settings are described in CONFIGURATION.md. The console works with any OpenID Connect provider that supports the authorization code flow for a confidential client.
| Provider | Status | Guide |
|---|---|---|
| Keycloak 26.8.0 | Tested by e2e/keycloak_oidc.sh (2026-10-05) |
oidc-keycloak.md |
| Microsoft Entra ID | Not yet tested | — |
| Not yet tested | — | |
| Okta | Not yet tested | — |