Self managed Connection timeout #461
-
@dimastbk ` import grpc from pyzeebe.channel.channel_options import get_channel_options def create_self_managed_channel(
def _create_camunda_self_managed_credentials( def _get_access_token(url: str, client_id: str, client_secret: str, audience: str) -> str: def _create_oauth_credentials(access_token: str) -> grpc.ChannelCredentials: ` |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 1 reply
-
Hi! For self-managed Camunda Cluster you can use CamundaIdentityCredentials (see example in https://github.com/camunda-community-hub/pyzeebe/blob/master/docs/channels.rst under "Example with oauth2 (like Camunda Identity):") . This GRPC plugin can automatically update the token every five minutes (default in Camunda Self-Managed). (Available only in 4.*, that under development.) |
Beta Was this translation helpful? Give feedback.
-
Thanks for your reply! However I get this error after it tries to connect multiple times: File "c:\Users\rickb\Desktop\pyzeebe4.0\pyzeebes4.0\pyzeebe\pyzeebe\grpc_internals\zeebe_job_adapter.py", line 41, in activate_jobs any idea why? |
Beta Was this translation helpful? Give feedback.
Hi! For self-managed Camunda Cluster you can use CamundaIdentityCredentials (see example in https://github.com/camunda-community-hub/pyzeebe/blob/master/docs/channels.rst under "Example with oauth2 (like Camunda Identity):") . This GRPC plugin can automatically update the token every five minutes (default in Camunda Self-Managed). (Available only in 4.*, that under development.)