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
We want to use ZooNavigator in our production environment to access zk cluster with ACLs. But also we have legacy zk cluster without ACL, and we must prevent users to specify custom connection string to prevent access to legacy cluster.
Is there any way to predefine and prevent to use custom connection string? If not, maybe it worth to implement it?
For example, add some environment variable, describing constant connection string, which will be disabling field with connection string in login form. But leave the ability to specify login and password to use ACLs, or leave it empty.
The text was updated successfully, but these errors were encountered:
I see. There is no such option yet and I do think it's worth implementing (but keeping the use-case when you want both predefined connections and custom ones). I intend to redesign login a bit and this could be part of it, but I don't see that happening very soon, unfortunately
We want to use ZooNavigator in our production environment to access zk cluster with ACLs. But also we have legacy zk cluster without ACL, and we must prevent users to specify custom connection string to prevent access to legacy cluster.
Is there any way to predefine and prevent to use custom connection string? If not, maybe it worth to implement it?
For example, add some environment variable, describing constant connection string, which will be disabling field with connection string in login form. But leave the ability to specify login and password to use ACLs, or leave it empty.
The text was updated successfully, but these errors were encountered: