airflow-cyberark-secrets-backend
This is a secrets backend for CyberArk CCP (central credential provider) for the Apache Airflow platform. It will allow one to pull connections and variables from their CyberArk safes via the CCP.
This library has been tested with Airflow 1.10.14.
Documentation for CyberArk CCP can be found here .
Documentation for Airflow secrets backends can be found here
Usage
pip install airflow-cyberark-secrets-backend
Update your airflow.cfg with the following
[secrets]
backend = airflow_cyberark_secrets_backend.CyberArkSecretsBackend
backend_kwargs = {"app_id": "/files/var.json", "ccp_url": "/files/conn.json", "safe": "", "verify": "/path/to/ssl/cert.pem" }
The backend_kwargs:
- app_id : The application ID for CCP
- ccp_url : The host URL for CCP AIM, excluding query params
- safe : The secrets safe
- verify : The SSL cert path to for CCP SSL, can be False for disable, can be env var
CYBERARK_SSL, defaultFalse
This library expects and requires your CyberArk response to have the the following properties (will be mapped mapped to Airflow keys). This map is a band-aid required from the little configuration CyberArk PAM (11.xx) allows.
- AccountDescription : svc_account
- ApplicationName : schema
- Address : host
- Comment : extra
- Content : password
- LogonDomain : login
- Port : port
AccountDescription : svc_account field is used to fetch password from rotating secret where the fetched secret is statis, i.e. if you fetch
secret1which is static, if you specify the CCP URL forsecret2which rotates it will fetch metadata forsecret1and fill in password fromsecret2in its response
Development
PRs welcomed.
The following will install in editable mode with all required development tools.
pip install -e '.[dev]'
Please format (black) and lint (pylint) before submitting PR.
Metadata
Release files for airflow-cyberark-secrets-backend 0.1.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| airflow-cyberark-secrets-backend-0.1.0.tar.gz | 3.8 kB | Without provenance | Details for airflow-cyberark-secrets-backend-0.1.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| airflow_cyberark_secrets_backend-0.1.0-py3-none-any.whl | Python 3 | none | any | Details for airflow_cyberark_secrets_backend-0.1.0-py3-none-any.whl |
Total release size: 8.9 kB
Release files / airflow-cyberark-secrets-backend-0.1.0.tar.gz
| Download URL | airflow-cyberark-secrets-backend-0.1.0.tar.gz |
|---|---|
| Size | 3.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
4629a46a36baa136654b4c307251b0c99bf3209fc74e17a3828c7b3b886d5dda
|
|
BLAKE2b-256 checksum How to use checksums |
9b4aec482df99200a8c8f5eaff5d89d94f8d857767e5cabc8eb3912c301b42c8
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.3.0 pkginfo/1.7.0 requests/2.25.1 setuptools/54.0.0 requests-toolbelt/0.9.1 tqdm/4.51.0 CPython/3.7.3
|
Release files / airflow_cyberark_secrets_backend-0.1.0-py3-none-any.whl
| Download URL | airflow_cyberark_secrets_backend-0.1.0-py3-none-any.whl |
|---|---|
| Size | 5.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
3f793eac7a7b7313426bef6aabf7d1a9632aa08b39ec446005fb788d318c977e
|
|
BLAKE2b-256 checksum How to use checksums |
be4aabeddca445338fdf0739a5a0cb8a27d40a197002bfabf3ff1db0c912ac05
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.3.0 pkginfo/1.7.0 requests/2.25.1 setuptools/54.0.0 requests-toolbelt/0.9.1 tqdm/4.51.0 CPython/3.7.3
|
Security for airflow-cyberark-secrets-backend 0.1.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.