feat(jans-lock-master): process telemetry data from Cedraling and post it to config api

[yurem]

Calendaring has communication channel with Lock master only. In this case it should post periodically telemetry data to /audit endpoint.

Data should be send in CBOR format and have at least next properties:

/audit/telemetry:
last_policy_load_time
last_policy_load_size
last_policy_load_status

policy_success_load_counter
policy_failed_load_counter

last_policy_evaluation_time_ns
avg_policy_evaluation_time_ns
mem_usage_mb
count_evaluation_requests

After getting this data Lock master should forward it to config-api

[pujavs]

Looking into it

[pujavs]

Impacted modules changes in

• lock-master
• config-api
• setup

Changes:

• lock-master /jans-lock/v1/audit/telemetry endpoint internally calls config-api jans-config-api/lock/audit/telemetry with required oauth scope to persist the data.
• config-api: persists the telemetry data in DB
• setup: New config properties for lock client and endpoint details Note Lock should have its pre-registered client, during setup a client with with required scope should be created and its details should be updated in lock DB config.

Only snippet of newly added config properties are as follows; { ........... "issuerUrl": "https://pujavs-probable-alpaca.gluu.info", "clientId": "1800.222ebcc3-6f3f-4a27-bf99-6d1fc57f8295", "clientPassword": "e4HafedZpRWR6ZbB6h6V8Q==", "tokenUrl": "https://pujavs-probable-alpaca.gluu.info/jans-auth/restv1/token", "endpointDetails": { "jans-config-api/lock/audit/telemetry": [ "https://jans.io/oauth/lock/telemetry.readonly", "https://jans.io/oauth/lock/telemetry.write" ], "jans-config-api/lock/audit": [ "https://jans.io/oauth/lock/audit.readonly", "https://jans.io/oauth/lock/audit.write" ], "jans-config-api/lock/audit/health": [ "https://jans.io/oauth/lock/health.readonly", "https://jans.io/oauth/lock/health.write" ] }, ................................. }

Screenshot

[pujavs]