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
due to some bad historical decisions i have now 2 clusters, one without authorization and second protected by passwords.
first one never issues auth challenge with original client and now i have an situation when proxy actually expecting opcodes from target but got always "authenticate" instead of "ready" and so on.
that's kind of expected behavior (if you deeply in source code) but i would like to ask you to estimate possibilities to (say) mock auth challenge or something like to redirect auth response from second cluster or something like that
and i perfectly understand that best solution would be enabling auth on both clusters (as it should be in production environment) but ability will be helpful to deal with problems like mine seamlessly
enormously helpful tool, guys.
due to some bad historical decisions i have now 2 clusters, one without authorization and second protected by passwords.
first one never issues auth challenge with original client and now i have an situation when proxy actually expecting opcodes from target but got always "authenticate" instead of "ready" and so on.
that's kind of expected behavior (if you deeply in source code) but i would like to ask you to estimate possibilities to (say) mock auth challenge or something like to redirect auth response from second cluster or something like that
and i perfectly understand that best solution would be enabling auth on both clusters (as it should be in production environment) but ability will be helpful to deal with problems like mine seamlessly