-
Notifications
You must be signed in to change notification settings - Fork 37
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
feat: [WD-16894] Add bulk deletion and group modification of TLS Users #1008
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Some comments below, I think this is still missing to address the requirement "Legacy TLS users should be disabled, not deleted.". But maybe that is why it is still in draft state.
e8d3c8b
to
6da6cf8
Compare
Good work so far @Kxiru for figuring out the difference between legacy and fine-grained tls identities. I think before conducting a proper review for the PR, there are a few items I'd like to see covered first:
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice update on the PR details 🔥
I've left some code related comments so far. Will QA tomorrow.
QA comments
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@Kxiru I think you didn't push the changes for the review comments. Please would you double check that. I have unresolved the comments for now.
Apologies, you are right, I hadn't pushed the changes. |
6da6cf8
to
a4fcbd3
Compare
Comments 3 and 4 have been addressed in my last commit. Comment no.2 can not be recreated on my machine and therefore I believe that I have addressed this in my last commit as well. I'll address the dynamic identity chips now :). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Almost there, some small nits
a4fcbd3
to
8ed4442
Compare
After completing group modification for mixed type identities, I am still seeing that tls identities gets de-selected. Screencast.from.09-12-2024.17.20.37.webm |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Two ideas to avoid duplication and make the code a bit cleaner.
Addiitonal feature: Enable user feedback when the user is deleitng an identity such as a spinner. |
8ed4442
to
4256bfb
Compare
@Kxiru just noticed the tests are failing, looking at the failure, it's probably due to the change where we no longer reset identities selection after modifying their groups |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the iteration on this one. It seems very good already, a handful of comments for things that I discovered that can be a bit simpler or improved slightly. Most are tiny changes.
Signed-off-by: Nkeiruka <[email protected]>
4256bfb
to
a33ba9f
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
QA and Code LGTM, good stuff :)
## Done - Created "Create Identity" Button - Create modal to create new TLS fine grained identities. - A few new functions and a new LXDTrustToken type. ## User Management Spike [✔️] A user needs to be able to create a TLS user (Creates a pending user) [✔️] A user needs to be able to destroy a TLS user ([WD-16894](#1008)) Fixes: - Inability to create TLS fine grained tokens through the UI. ## QA 1. Run the LXD-UI: - On the demo server via the link posted by @webteam-app below. This is only available for PRs created by collaborators of the repo. Ask @mas-who or @edlerd for access. - With a local copy of this branch, [build and run as described in the docs](../CONTRIBUTING.md#setting-up-for-development). 2. Perform the following QA steps: - [List the steps to QA the new feature(s) or prove that a bug has been resolved] ## Screenshots ![image](https://github.com/user-attachments/assets/9549e7f1-c217-4d45-8afa-9ef2c1845f43) ![Screenshot from 2024-12-10 22-47-10](https://github.com/user-attachments/assets/71f60924-98ac-47a1-a0c4-7498792610a4) [WD-16894]: https://warthogs.atlassian.net/browse/WD-16894?atlOrigin=eyJpIjoiNWRkNTljNzYxNjVmNDY3MDlhMDU5Y2ZhYzA5YTRkZjUiLCJwIjoiZ2l0aHViLWNvbS1KU1cifQ
Done
QA
Create "new" TLS Fine grained identities
Delete TLS Users
Add TLS users users to a group
Test TLS user permissions / Login as a TLS User
cat <KEY-FILE> <CRT-FILE> > <PEM-FILE-NAME>.pem
bind 0.0.0.0:8407 ssl verify optional crt <PEM-FILE-PATH> ca-file <CRT-FILE-PATH>
server lxd_https LXD_UI_BACKEND_IP:8443 ssl verify none crt <PEM-FILE-PATH>
Screenshots