This project serves as a Software Development Kit for developers of Indykite applications. The Python SDK enables you to easily integrate the IndyKite platform gRPC APIs into your Python application. https://console2.indykite.id/ https://www.indykite.com/
- Python >=3.11
add to pipfile [packages]:
indykite-sdk-python = {ref = "v1.49.0", git = "https://github.com/indykite/indykite-sdk-python"}
To do anything at all in the IndyKite platform, you must first create an Organization (Customer) in the Hub (https://console2.indykite.id/) — the Web interface used to interact with and do tasks in the IndyKite platform and get your credentials (https://docs.indykite.com/docs/get-started).
Once you have created a Customer, a service account, and you have your service account credentials, you can set up the SDK.
Definition | Description |
---|---|
Identity Knowledge Graph | The Identity Knowledge Graph is a contextualized data model that constructed entities and their relationships (data entities) using a graph database. |
Nodes | Data points stored as nodes (identity nodes and resources) and edges (relationships) |
Identity node | An identity node (node with is_identity=True) is the digital identity of a physical entity on/in a software/identity system |
Application Space ID | ID of the application space the nodes belong to |
Application Agent ID | ID of the agent which makes the application available for the different calls |
Private Key and Settings | The secret which required to reach the system. |
JWT | JSON Web Tokens |
Introspect | A process used to validate the token and to retrieve properties assigned to the token |
1️⃣ Service account credentials
You need to have a Service Account credentials json file to be able to use the IndyKite Python SDK. You can get it from the IndyKite hub: https://console2.indykite.id/.
To manage its spaces, among other things, the owner of the relevant customer creates a service account.
A service account is a non-person entity which belongs to the owner who created it. It is a node with its own credential which acts only through its owner.
A service account is always created under a customer.
The purpose of a service account is for a non-person entity to manage the platform configuration: creating Projects (AppSpaces), Applications, Agent credentials, other service accounts, configuration nodes or any action through the Graph DB.
The service account is also needed if you want to use Terraform for your configuration.
You have two choices to set up the necessary credentials. You either pass the json to the INDYKITE_SERVICE_ACCOUNT_CREDENTIALS
environment variable or set the INDYKITE_SERVICE_ACCOUNT_CREDENTIALS_FILE
environment variable to the configuration file's path.
You should use an absolute path for the file.
-
on Linux and OSX
export INDYKITE_SERVICE_ACCOUNT_CREDENTIALS='{ "serviceAccountId":"", "endpoint":"", "privateKeyJWK":{ "alg":"ES256", "crv":"P-256", "d":"", "kid":"", "kty":"EC", "use":"sig", "x":"", "y":"" }, "privateKeyPKCS8Base64":"", "privateKeyPKCS8":"-----BEGIN PRIVATE KEY----------END PRIVATE KEY-----\n" }'
or
export INDYKITE_SERVICE_ACCOUNT_CREDENTIALS_FILE=/Users/xx/configuration.json
-
on Windows command line
setex INDYKITE_SERVICE_ACCOUNT_CREDENTIALS='{ "serviceAccountId":"", "endpoint":"", "privateKeyJWK":{ "alg":"ES256", "crv":"P-256", "d":"", "kid":"", "kty":"EC", "use":"sig", "x":"", "y":"" }, "privateKeyPKCS8Base64":"", "privateKeyPKCS8":"-----BEGIN PRIVATE KEY----------END PRIVATE KEY-----\n" }'
or
setex INDYKITE_SERVICE_ACCOUNT_CREDENTIALS_FILE "C:\Users\xx\Documents\configuration.json"
2️⃣ AppAgent Credentials
You will also need to have an Application Agent credentials json file to be able to use the other services like IKG (ingestion) and KBAC (authorization). You can get it from the IndyKite hub (https://console2.indykite.id/) or using the SDK.
Example configuration file:
{
"baseUrl": "",
"applicationId": "",
"appSpaceId": "",
"appAgentId": "",
"endpoint": "",
"privateKeyJWK":
{
"alg": "ES256",
"crv": "P-256",
"d": "",
"kid": "",
"kty": "EC",
"use": "sig",
"x": "",
"y": ""
},
"privateKeyPKCS8Base64": "",
"privateKeyPKCS8": ""
}
A token lifetime is 1h by default. You can change this time (from 2 minutes to 24h) by adding a tokenLifetime parameter.
It will have to be human-readable and Golang-like see -> https://pkg.go.dev/time#ParseDuration
Examples: 30m, 1.5h, 2h45m
Example at the end of the json file:
{
...
"privateKeyPKCS8": "-----BEGIN PRIVATE KEY-----\nM\n-----END PRIVATE KEY-----",
"tokenLifetime": "30m"
}
Identity
You have two choices to set up the necessary credentials. You either pass the json to the `INDYKITE_APPLICATION_CREDENTIALS`
environment variable or set the `INDYKITE_APPLICATION_CREDENTIALS_FILE` environment variable to the configuration file's path.
-
on Linux and OSX
export INDYKITE_APPLICATION_CREDENTIALS='{ "baseUrl": "", "applicationId": "", "appSpaceId": "", "appAgentId": "", "endpoint": "", "privateKeyJWK": { "alg": "ES256", "crv": "P-256", "d": "", "kid": "", "kty": "EC", "use": "sig", "x": "", "y": "" }, "privateKeyPKCS8Base64":"", "privateKeyPKCS8": "" }'
or
export INDYKITE_APPLICATION_CREDENTIALS_FILE=/Users/xx/configuration.json
-
on Windows command line
setex INDYKITE_APPLICATION_CREDENTIALS='{ "baseUrl": "" "applicationId": "", "appSpaceId": "", "appAgentId": "", "endpoint": "", "privateKeyJWK": { "alg": "ES256", "crv": "P-256", "d": "", "kid": "", "kty": "EC", "use": "sig", "x": "", "y": "" }, "privateKeyPKCS8Base64":"", "privateKeyPKCS8": "" }'
or
setex INDYKITE_APPLICATION_CREDENTIALS_FILE "C:\Users\xx\Documents\configuration.json"
3️⃣ Initialize a client to establish the connection.
This client instance's self.stub
will be used by the other functions.
Note: The client is opening a GRPC channel and the client must close the channel, too! If the client doesn't close the channel
after use, it can cause surprises like _InactiveRpcErrors
.
from indykite_sdk.identity import IdentityClient
import argparse
# Create parent parser
parser = argparse.ArgumentParser(description="Identity client API.")
parser.add_argument("-l", "--local", action="store_true", help="make the request to localhost")
subparsers = parser.add_subparsers(dest="command", help="sub-command help")
# Create
args = parser.parse_args()
local = args.local
client = IdentityClient(local)
4️⃣ Close a GRPC channel
You simply call the close()
function on the channel (The IdentityClient()
function below represents the def in the previous step)
from indykite_sdk.identity import IdentityClient
def open_and_close_channel():
client = IdentityClient()
client.channel.close()
To run unit tests, simply execute
pytest
To display code coverage, enter
pytest --cov .
https://indykite.github.io/indykite-sdk-python/
https://github.com/indykite/indykite-sdk-python/tree/master/indykite_sdk
Commit message follows commit guidelines
Checkout our roadmap on our issues page
Contribution guidelines for this project
Feel free to file a bug, submit an issue or give us feedback on our issues page
Coming Soon!
IndyKite is a cloud identity platform built to secure and manage human & non-person (IoT) identities and their data. Based on open source standards, the cloud platform gives developers the ability to secure data and embed identity controls into their Web 3.0 applications. Empowering the world’s 23 million developers without the need to involve security and identity specialists.
This project is licensed under the terms of the Apache 2.0 license.