You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Cadarling has SSE communication channel with Lock master. This endpoints is protected with access token. At startup Cedarling should open connection to this endpoint for communion and re-open it on connection lost.
The main goal of this endpoint is to supply: token status list data, and 3-rd party data.
Lock master periodically fetch token status list from Jans Auth.
After that it send 2 types of events:
Full token status list
Only changed parts of token status list.
Policy re-load event
3-rd party data
It's up to Cedarling to process or not these 3 events types.
First event is with full JWT which is needed for new Cedarlings instances or for periodic full resync (Cedarling can do this on low number of policy requests).
Second event type should contains only changed parts of binary token status list.
Third event type Lock should send when it detected policy changes.
Four event is reserved for 3-rd party data.
Required event types:
STATUS_LIST: {full status_list response}
STATUS_LIST_UPDATE: {changed parts in last STATUS_LIST}
CONFIG_UPDATE: {config}
FORCE_REPORT: {force send audit messages imminently}
We need to add details about event types to project wiki.
The text was updated successfully, but these errors were encountered:
Cadarling has SSE communication channel with Lock master. This endpoints is protected with access token. At startup Cedarling should open connection to this endpoint for communion and re-open it on connection lost.
The main goal of this endpoint is to supply: token status list data, and 3-rd party data.
Lock master periodically fetch token status list from Jans Auth.
After that it send 2 types of events:
It's up to Cedarling to process or not these 3 events types.
First event is with full JWT which is needed for new Cedarlings instances or for periodic full resync (Cedarling can do this on low number of policy requests).
Second event type should contains only changed parts of binary token status list.
Third event type Lock should send when it detected policy changes.
Four event is reserved for 3-rd party data.
Required event types:
STATUS_LIST: {full status_list response}
STATUS_LIST_UPDATE: {changed parts in last STATUS_LIST}
CONFIG_UPDATE: {config}
FORCE_REPORT: {force send audit messages imminently}
We need to add details about event types to project wiki.
The text was updated successfully, but these errors were encountered: