Bug 1677669 - [RFE] Background Usergroup Sync check box option
Summary: [RFE] Background Usergroup Sync check box option
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: LDAP
Version: 6.4
Hardware: x86_64
OS: Linux
medium
low
Target Milestone: Unspecified
Assignee: Daniel Lobato Garcia
QA Contact: Sanket Jagtap
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-02-15 14:24 UTC by Anand Jambhulkar
Modified: 2023-03-24 14:38 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-04-02 12:33:16 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker SAT-16737 0 None None None 2023-03-24 14:38:51 UTC

Description Anand Jambhulkar 2019-02-15 14:24:22 UTC
Description of problem:

Red Hat Satellite doesn't pull in the whole AD global group; it only pulls in the users that have accounts.  So when a new user logs in, their account gets created. If you check the box then they have to wait for AD to go out and grab the group, and if the group is large, then the login time takes a couple of minutes.  This is too long.  The other option is to wait for the cron job that runs every 30 minutes.  So, at most someone would have to wait 30 minutes before their new account has access.    It would be great to see the run in the back ground only if a person isn't already in the group.  That way a person doesn't have to wait 30 minutes before they can use their account.  And everyone else doesn't have to wait a minute every time they try and login.


Q1 - What is the exact nature of the problem trying to be solved with this request?

A1 - When an existing user logins in it takes upwards of 1 minute that they have to what for the "Usergroup sync" to happen.
     If a new user logs in then they have to wait at most 30 minutes if the "Usergroup sync" is not checked.
     If we had a background process then a new user would have access in a few minutes instead of having to wait 30 minutes.


Q2 - List the business requirements.

A2 - I would like to be more respectful of peoples time and resources.
     I don't want existing people to have to wait or new users.
     I also don't want to pound on our AD servers every 30 minutes either.


Q3 - Do you have specific timeline dependencies?

A3 - In a reasonable time.


Q4 - Can you please explain us the what are the functional requirements? If test cases can be provided this would be even more ideal.

A4 - When a new user logs in, they would have access sooner and not have to wait the 30 min.


Q5 - Would you be able to assist in testing this functionality if implemented?

A5 - Yes.

Comment 2 Bryan Kearney 2020-03-04 14:08:21 UTC
The Satellite Team is attempting to provide an accurate backlog of bugzilla requests which we feel will be resolved in the next few releases. We do not believe this bugzilla will meet that criteria, and have plans to close it out in 1 month. This is not a reflection on the validity of the request, but a reflection of the many priorities for the product. If you have any concerns about this, feel free to contact Red Hat Technical Support or your account team. If we do not hear from you, we will close this bug out. Thank you.

Comment 3 Bryan Kearney 2020-04-02 12:33:16 UTC
Thank you for your interest in Satellite 6. We have evaluated this request, and while we recognize that it is a valid request, we do not expect this to be implemented in the product in the foreseeable future. This is due to other priorities for the product, and not a reflection on the request itself. We are therefore closing this out as WONTFIX. If you have any concerns about this, please do not reopen. Instead, feel free to contact Red Hat Technical Support. Thank you.


Note You need to log in before you can comment on or make changes to this bug.