-
Notifications
You must be signed in to change notification settings - Fork 116
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Add Hammer support for invalidating users JWTs #17468
Add Hammer support for invalidating users JWTs #17468
Conversation
b166c15
to
770cb4a
Compare
3de9987
to
3938ea8
Compare
09bb698
to
7c0d2de
Compare
trigger: test-robottelo |
PRT Result
|
7c0d2de
to
70008b4
Compare
trigger: test-robottelo |
PRT Result
|
8b9b6a6
to
33e4c00
Compare
trigger: test-robottelo |
PRT Result
|
33e4c00
to
8d1d61d
Compare
trigger: test-robottelo |
PRT Result
|
8d1d61d
to
704c8a8
Compare
704c8a8
to
a922725
Compare
trigger: test-robottelo |
PRT Result
|
a922725
to
6ecd4e5
Compare
trigger: test-robottelo |
PRT Result
|
non_admin_user = module_target_sat.api.User( | ||
login=gen_string('alpha'), password=password, organization=[module_org] | ||
).create() | ||
role = module_target_sat.cli_factory.make_role({'organization-id': module_org.id}) | ||
module_target_sat.cli_factory.add_role_permissions( | ||
role.id, | ||
resource_permissions={'User': {'permissions': ['edit_users']}}, | ||
) | ||
module_target_sat.cli.User.add_role({'id': non_admin_user.id, 'role-id': role.id}) | ||
module_target_sat.cli.User.add_role({'id': non_admin_user.id, 'role': 'Register hosts'}) |
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.
Since we've same setup with APIs for both CLI and API tests now, so why not move this into a setup fixture?
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.
Good point to improve it. I will make this change along with removal of no_container
marker. I don't want to block merge of the PR because of this.
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.
On the second thought, creating a fixture just for 2 tests which are in different modules and using different interfaces for the setup doesn't make sense. The fixture calls are also heavy and if we add more such tests to it then I would consider creating a fixture.
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.
I will create a fixture common for all interfaces in a separate PR.
Problem Statement
Hammer support for invalidating JWTs : SAT-30385
Solution
Added support for JWT invalidate in CLI
Related Issues