Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

data masking in provectus-kafka-ui #1352

Closed
nemerna opened this issue Jan 4, 2022 · 1 comment · Fixed by #2850
Closed

data masking in provectus-kafka-ui #1352

nemerna opened this issue Jan 4, 2022 · 1 comment · Fixed by #2850
Assignees
Labels
scope/backend status/accepted An issue which has passed triage and has been accepted type/feature A new feature
Projects
Milestone

Comments

@nemerna
Copy link

nemerna commented Jan 4, 2022

Is your proposal related to a problem?

in case users need to allow specific pepole to view the data inside topics messages for example
where they need other group of pepole to only see the title of the messages without the content
then a data msking could be very helpful

Describe the solution you'd like

add an option to enable datamasking
then when a specific user is authenticated and he is supposed to see the masked data only
when a more privileged user access to the ui he will be able to see the real content of messages

Describe alternatives you've considered

regarding the user privilege based access ive been using an authentication proxy
where i have cofigure the same kafka cluster in the ui twice
but if the data masking was available then i would mention that flag in one of the cluster
then the auth-proxy will be able to give access to specific pepole into a specific kafka cluster inside the ui

Additional context

in case data masking isnt available yet
then me & my team may be able to contribute to this project and add this feature

@nemerna nemerna added the type/enhancement En enhancement to an already existing feature label Jan 4, 2022
@github-actions github-actions bot added the status/triage Issues pending maintainers triage label Jan 4, 2022
@Haarolean
Copy link
Contributor

Hi, thanks for reaching out.
We'll implement this as a part of the feature #753.

@Haarolean Haarolean added scope/backend status/accepted An issue which has passed triage and has been accepted type/feature A new feature and removed type/enhancement En enhancement to an already existing feature status/triage Issues pending maintainers triage labels Jan 4, 2022
@Haarolean Haarolean added this to the 0.5 milestone Feb 10, 2022
@Haarolean Haarolean added this to 0.5 in Roadmap Feb 10, 2022
@Haarolean Haarolean added this to Features in Release 0.5 Apr 21, 2022
@Haarolean Haarolean removed this from 0.5 in Roadmap May 4, 2022
@Haarolean Haarolean removed this from Features in Release 0.5 Aug 9, 2022
@Haarolean Haarolean removed this from the 0.5 milestone Aug 9, 2022
@Haarolean Haarolean added this to 0.6 in Roadmap Aug 9, 2022
@Haarolean Haarolean added this to To do in Release 0.5 via automation Nov 28, 2022
@Haarolean Haarolean added this to the 0.5 milestone Nov 28, 2022
@Haarolean Haarolean moved this from To do to Done in Release 0.5 Nov 28, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
scope/backend status/accepted An issue which has passed triage and has been accepted type/feature A new feature
Projects
No open projects
Development

Successfully merging a pull request may close this issue.

3 participants