Replies: 2 comments
-
Hi @jyoussefzadeh But ... It definitely can be added. If you can share more on your use-case, and timeline you'd want to see this, we can take it into account :) Of course if you'd want to add these capabilities yourself, we'd be more than happy to help you get started. |
Beta Was this translation helpful? Give feedback.
0 replies
-
transformed to an issue: https://github.com/authorizon/opal/issues/160 |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
From the documentation & previous discussions, I understand that a JWT token can be issued to authenticate the OPAL Clients connection to OPAL Server.
Is it also possible to restrict which
OPAL_DATA_TOPICS
can be subscribed to from that client?For instance, if there is a single shared pool of OPAL Servers with hundreds of different OPAL Clients connected to it, we do not want one client to be able to subscribe to & fetch unauthorized information that belongs to another client.
On a similar vein, given some bearer token for calling OPAL Server APIs, is it possible to restrict which topics that token can publish an event to, using the
/data/config
API?Also, is it possible to restrict access to different OPAL Server endpoints entirely?
Beta Was this translation helpful? Give feedback.
All reactions