https://github.com/cyberark/ark-sdk-python
CyberArk's Official SDK and CLI - https://cyberark.github.io/ark-sdk-python/
https://github.com/cyberark/ark-sdk-python
cli cyberark python sdk
Last synced: 5 months ago
JSON representation
CyberArk's Official SDK and CLI - https://cyberark.github.io/ark-sdk-python/
- Host: GitHub
- URL: https://github.com/cyberark/ark-sdk-python
- Owner: cyberark
- License: apache-2.0
- Created: 2023-11-13T09:24:31.000Z (almost 2 years ago)
- Default Branch: main
- Last Pushed: 2024-07-23T15:38:41.000Z (about 1 year ago)
- Last Synced: 2024-09-24T17:16:46.668Z (about 1 year ago)
- Topics: cli, cyberark, python, sdk
- Language: Python
- Homepage: https://cyberark.com
- Size: 27.2 MB
- Stars: 10
- Watchers: 7
- Forks: 4
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
- License: LICENSE.txt
- Code of conduct: CODE_OF_CONDUCT.md
- Security: SECURITY.md
Awesome Lists containing this project
README
Ark SDK Python
==============
📜[**Documentation**](https://cyberark.github.io/ark-sdk-python/)
CyberArk's Official SDK and CLI for different services operations
## Features and Services
- [x] Extensive and Interactive CLI
- [x] Different Authenticators
- [x] Identity Authentication Methods
- [x] MFA Support for Identity
- [x] Identity Security Platform
- [x] Services API
- [x] SIA VM / Databases Policies and Policies Interactive Editor Service
- [x] SIA Databases Onboarding
- [x] SIA Target Sets Onboarding
- [x] SIA Databases Secrets
- [x] SIA VM Secrets
- [x] SIA Certificates Service
- [x] SIA SSO Service
- [x] SIA K8S Service
- [x] SIA DB Service
- [x] SIA Access Service
- [x] Session Monitoring Service
- [x] Identity Users Service
- [x] Identity Roles Service
- [x] Identity Policies Service
- [x] Identity Directories Service
- [x] Identity Connectors Service
- [x] PCloud Accounts Service
- [x] PCloud Safes Service
- [x] PCloud Platforms Service
- [x] PCloud Applications Service
- [x] Connector Manager Service
- [x] All services contains CRUD and Statistics per respective service
- [x] Ready to use SDK in Python
- [x] CLI and SDK Examples
- [x] Fully Interactive CLI comprising of 3 main actions
- [x] Configure
- [x] Login
- [x] Exec
- [x] Filesystem Inputs and Outputs for the CLI
- [x] Silent and Verbose logging
- [x] Profile Management and Authentication Caching
TL;DR
=====
## Enduser
## Admin
Installation
============
One can install the SDK via the community pypi with the following command:
```shell
pip3 install ark-sdk-python
```
CLI Usage
============
Both the SDK and the CLI works with profiles
The profiles can be configured upon need and be used for the consecutive actions
The CLI has the following basic commands:
- configure - Configures profiles and their respective authentication methods
- login - Logs into the profile authentication methods
- exec - Executes different commands based on the supported services
- profiles - Manage multiple profiles on the machine
configure
---------
The configure command is used to create a profile to work on
The profile consists of infomration regarding which authentication methods to use and what are their method settings, along with other related information such as MFA
How to run:
```shell
ark configure
```
The profiles are saved to ~/.ark_profiles
No arguments are required, and interactive questions will be asked
If you wish to only supply arguments in a silent fashion, --silent can be added along with the arugments
Usage:
```shell
usage: ark configure [-h] [-r] [-s] [-ao] [-v] [-ls {default}] [-ll {DEBUG,INFO,WARN,ERROR,CRITICAL}]
[-dcv] [-tc TRUSTED_CERT] [-pn PROFILE_NAME] [-pd PROFILE_DESCRIPTION] [-wwis]
[-isam {identity,identity_service_user}] [-iu ISP_USERNAME]
[-iimm {pf,sms,email,otp}] [-iiu ISP_IDENTITY_URL]
[-iiaa ISP_IDENTITY_AUTHORIZATION_APPLICATION]
optional arguments:
-h, --help show this help message and exit
-r, --raw Whether to raw output
-s, --silent Silent execution, no interactiveness
-ao, --allow-output Allow stdout / stderr even when silent and not interactive
-v, --verbose Whether to verbose log
-ls {default}, --logger-style {default}
Which verbose logger style to use
-ll {DEBUG,INFO,WARN,ERROR,CRITICAL}, --log-level {DEBUG,INFO,WARN,ERROR,CRITICAL}
Log level to use while verbose
-dcv, --disable-cert-verification
Disables certificate verification on HTTPS calls, unsafe!
-tc TRUSTED_CERT, --trusted-cert TRUSTED_CERT
Certificate to use for HTTPS calls
-pn PROFILE_NAME, --profile-name PROFILE_NAME
Profile name for storage
-pd PROFILE_DESCRIPTION, --profile-description PROFILE_DESCRIPTION
Info about the profile
-wwis, --work-with-isp
Whether to work with Identity Security Platform services
-isam {identity,identity_service_user}, --isp-auth-method {identity,identity_service_user}
-iu ISP_USERNAME, --isp-username ISP_USERNAME
Username to authenticate with
-iimm {pf,sms,email,otp}, --isp-identity-mfa-method {pf,sms,email,otp}
MFA method if mfa is needed
-iiu ISP_IDENTITY_URL, --isp-identity-url ISP_IDENTITY_URL
Identity url to use for authentication instead of fqdn resolving
-iiaa ISP_IDENTITY_AUTHORIZATION_APPLICATION, --isp-identity-authorization-application ISP_IDENTITY_AUTHORIZATION_APPLICATION
Identity application to authorize once logged in with the service user
```
login
-----
The logn command is used to login to the authentication methods configured for the profile
You will be asked to write a password for each respective authentication method that supports password, and alongside that, any needed MFA prompt
Once the login is done, the access tokens are stored on the computer keystore for their lifetime
Once they are expired, a consecutive login will be required
How to run:
```shell
ark login
```
Usage:
```shell
usage: ark login [-h] [-r] [-s] [-ao] [-v] [-ls {default}] [-ll {DEBUG,INFO,WARN,ERROR,CRITICAL}]
[-dcv] [-tc TRUSTED_CERT] [-pn PROFILE_NAME] [-f] [-nss] [-st] [-ra]
[-isu ISP_USERNAME] [-iss ISP_SECRET]
optional arguments:
-h, --help show this help message and exit
-r, --raw Whether to raw output
-s, --silent Silent execution, no interactiveness
-ao, --allow-output Allow stdout / stderr even when silent and not interactive
-v, --verbose Whether to verbose log
-ls {default}, --logger-style {default}
Which verbose logger style to use
-ll {DEBUG,INFO,WARN,ERROR,CRITICAL}, --log-level {DEBUG,INFO,WARN,ERROR,CRITICAL}
Log level to use while verbose
-dcv, --disable-cert-verification
Disables certificate verification on HTTPS calls, unsafe!
-tc TRUSTED_CERT, --trusted-cert TRUSTED_CERT
Certificate to use for HTTPS calls
-pn PROFILE_NAME, --profile-name PROFILE_NAME
Profile name to load
-f, --force Whether to force login even thou token has not expired yet
-nss, --no-shared-secrets
Do not share secrets of identity between different authenticators with the
same username
-st, --show-tokens Print out tokens as well if not silent
-ra, --refresh-auth If a cache exists, will also try to refresh it
-isu ISP_USERNAME, --isp-username ISP_USERNAME
Username to authenticate with to Identity Security Platform
-iss ISP_SECRET, --isp-secret ISP_SECRET
Secret to authenticate with to Identity Security Platform
```
Notes:
- You may disable certificate validation for login to different authenticators using the --disable-certificate-verification or supply a certificate to be used, not recommended to disable
exec
----
The exec command is used to execute various commands based on supported services for the fitting logged in authenticators
The following services and commands are supported:
- sia - Dynamic Privilege Access Services
- policies - SIA Policies Management
- vm - SIA VM Policies Service
- editor - SIA Policies Interactive Editor
- db - SIA DB Policies Service
- editor - SIA Policies Interactive Editor
- workspaces - SIA Workspaces Management
- db - SIA DB Workspace Service
- target-sets - SIA Target Sets Workspace Service
- secrets - SIA Secrets / Strong Accounts Management
- db - SIA DB Secrets Service
- vm - SIA VM Secrets Service
- certificates - SIA Certificates Management
- db - SIA DB Enduser Operations
- sso - SIA SSO Enduser Operations
- k8s - SIA kubernetes service
- access - SIA access service
- sm - Session Monitoring Service
- identity - Identity Service
- users - Identity Users Management
- roles - Identity Roles Management
- policies - Identity Policies Management
- directories - Identity Directories Reading
- pcloud - PCloud Service
- accounts - PCloud Accounts Management
- safes - PCloud Safes Management
- platforms - PCloud Platforms Management
- applications - PCloud Applications Management
- cmgr - Connector Manager Service
Any command has its own subcommands, with respective arguments
For example configure a profile to login to that respective tenant and perform SIA actions such as:
Add SIA Database Secret
```shell
ark exec sia secrets db add-secret --secret-name mysecret --secret-type username_password --username user --password mypass
```
Delete SIA Database Secret
```shell
ark exec sia secrets db delete-secret --secret-name mysecret
```
Add SIA Database
```shell
ark exec sia workspaces db add-database --name mydb --provider-engine postgres-sh --read-write-endpoint myendpoint.domain.com
```
List SIA Databases
```shell
ark exec sia workspaces db list-databases
```
Get VM policies stats
```shell
ark exec sia policies vm policies-stats
```
Add SIA VM Target Set
```shell
ark_public exec sia workspaces target-sets add-target-set --name mydomain.com --type Domain
```
Add SIA VM Secret
```shell
ark_public exec sia secrets vm add-secret --secret-type ProvisionerUser --provisioner-username=myuser --provisioner-password=mypassword
```
Edit policies interactively
This gives the ability to locally work with a policies workspace, and edit / reset / create policies, applied to both databases and vm policies
When they are ready, once can commit all the policies changes to the remote
Initially, the policies can be loaded and reloaded using
```shell
ark exec sia policies vm editor load-policies
```
Once they are loaded locally, they can be edited using the following commands
```shell
ark exec sia policies vm editor edit-policies
ark exec sia policies vm editor view-policies
ark exec sia policies vm editor reset-policies
ark exec sia policies vm editor generate-policy
ark exec sia policies vm editor remove-policies
ark exec sia policies vm editor policies diff
```
Evantually, they can be committed using
```shell
ark exec sia policies vm editor commit-policies
```
Generate a short lived SSO password for databases connection
```shell
ark exec sia sso short-lived-password
```
Generate a short lived SSO oracle wallet for oracle database connection
```shell
ark exec sia sso short-lived-oracle-wallet --folder ~/wallet
```
Generate kubectl config file
```shell
ark exec sia k8s generate-kubeconfig
```
Generate kubectl config file and save on specific path
```shell
ark exec sia k8s generate-kubeconfig --folder=/Users/My.User/.kube
```
Create a PCloud Safe
```shell
ark exec pcloud safes add-safe --safe-name=safe
```
Create a PCloud Account
```shell
ark exec pcloud accounts add-account --name account --safe-name safe --platform-id='UnixSSH' --username root --address 1.2.3.4 --secret-type=password --secret mypass
```
List available platforms
```shell
ark exec pcloud platforms list-platforms
```
List connector pools
```shell
ark exec exec cmgr list-pools
```
Get connector installation script
```shell
ark exec sia access connector-setup-script -ct onprem -co windows -cpi 588741d5-e059-479d-b4c4-3d821a87f012
```
You can view all of the commands via the --help for each respective exec action
Notes:
- You may disable certificate validation for login to different authenticators using the --disable-certificate-verification or supply a certificate to be used, not recommended to disable
Usafe Env Vars:
- ARK_PROFILE - Sets the profile to be used across the CLI
- ARK_DISABLE_CERTIFICATE_VERIFICATION - Disables certificate verification on REST API's
profiles
-------
As one may have multiple environments to manage, this would also imply that multiple profiles are required, either for multiple users in the same environment or multiple tenants
Therefore, the profiles command manages those profiles as a convenice set of methods
Using the profiles as simply running commands under:
```shell
ark profiles
```
Usage:
```shell
usage: ark profiles [-h] [-r] [-s] [-ao] [-v] [-ls {default}] [-ll {DEBUG,INFO,WARN,ERROR,CRITICAL}] [-dcv]
[-tc TRUSTED_CERT]
{list,show,delete,clear,clone,add} ...
positional arguments:
{list,show,delete,clear,clone,add}
list List all profiles
show Show a profile
delete Delete a specific profile
clear Clear all profiles
clone Clones a profile
add Adds a profile to the profiles folder from a given path
optional arguments:
-h, --help show this help message and exit
-r, --raw Whether to raw output
-s, --silent Silent execution, no interactiveness
-ao, --allow-output Allow stdout / stderr even when silent and not interactive
-v, --verbose Whether to verbose log
-ls {default}, --logger-style {default}
Which verbose logger style to use
-ll {DEBUG,INFO,WARN,ERROR,CRITICAL}, --log-level {DEBUG,INFO,WARN,ERROR,CRITICAL}
Log level to use while verbose
-dcv, --disable-cert-verification
Disables certificate verification on HTTPS calls, unsafe!
-tc TRUSTED_CERT, --trusted-cert TRUSTED_CERT
Certificate to use for HTTPS calls
```
SDK Usage
=========
As well as using the CLI, one can also develop under the ark sdk using its API / class driven design
The same idea as the CLI applies here as well
For example, let's say we want to create a demo environment containing all needed SIA DB assets
To do so, we can use the following script:
```python
ArkSystemConfig.disable_verbose_logging()
# Authenticate to the tenant with an auth profile to configure SIA
username = 'user@cyberark.cloud.12345'
print(f'Authenticating to the created tenant with user [{username}]')
isp_auth = ArkISPAuth()
isp_auth.authenticate(
auth_profile=ArkAuthProfile(
username=username, auth_method=ArkAuthMethod.Identity, auth_method_settings=IdentityArkAuthMethodSettings()
),
secret=ArkSecret(secret='CoolPassword'),
)
# Create SIA DB Secret, Database, Connector and DB Policy
sia_service = ArkSIAAPI(isp_auth)
print('Adding SIA DB User Secret')
secret = sia_service.secrets_db.add_secret(
ArkSIADBAddSecret(secret_type=ArkSIADBSecretType.UsernamePassword, username='Administrator', password='CoolPassword')
)
print('Adding SIA Database')
sia_service.workspace_db.add_database(
ArkSIADBAddDatabase(
name='mydomain.com',
provider_engine=ArkSIADBDatabaseEngineType.PostgresSH,
secret_id=secret.secret_id,
read_write_endpoint="myendpoint.mydomain.com",
)
)
print('Installing SIA Connector')
sia_service.access.install_connector(
ArkSIAInstallConnector(
connector_os=ArkOsType.LINUX,
connector_type=ArkWorkspaceType.ONPREM,
connector_pool_id='pool_id',
target_machine='1.2.3.4',
username='root',
private_key_path='/path/to/private.pem',
)
)
print('Adding SIA DB Policy')
sia_service.policies_db.add_policy(
ArkSIADBAddPolicy(
policy_name='IT Policy',
status=ArkSIARuleStatus.Enabled,
description='IT Policy',
providers_data=ArkSIADBProvidersData(
postgres=ArkSIADBPostgres(
resources=['postgres-onboarded-asset'],
),
),
user_access_rules=[
ArkSIADBAuthorizationRule(
rule_name='IT Rule',
user_data=ArkSIAUserData(roles=['DpaAdmin'], groups=[], users=[]),
connection_information=ArkSIADBConnectionInformation(
grant_access=2,
idle_time=10,
full_days=True,
hours_from='07:00',
hours_to='17:00',
time_zone='Asia/Jerusalem',
connect_as=ArkSIADBConnectAs(
db_auth=[
ArkSIADBLocalDBAuth(
roles=['rds_superuser'],
applied_to=[
ArkSIADBAppliedTo(
name='postgres-onboarded-asset',
type=ArkSIADBResourceIdentifierType.RESOURCE,
)
],
),
],
),
),
)
],
)
)
```
More examples can be found in the examples folder
## License
This project is licensed under Apache License 2.0 - see [`LICENSE`](LICENSE.txt) for more details
Copyright (c) 2023 CyberArk Software Ltd. All rights reserved.