Description of problem:

Customer has added two LDAP Sources.  One AD and LDAP.
Then the users from AD can log in and they have an external group taken from LDAP which assigns the roles.

Now they have updated to 6.2.2 but still have an issues with the LDAP groups connection.

Here is more information and a test case

1. Create a new LDAP Authentication
    Server Type: Active Directory
    Enable -> Automatically create accounts in Satellite : True

2. Create a new LDAP Authentication
    Server Type: POSIX
    Enable -> Usergroup sync

3. Create a new User group
    Connect it to a group in the LDAP directory (Created in #2)
    Enable role -> Admin

4. Log in as an AD user
    This works and the user is created but the user have not got the role Admin

Now do either one of these actions
5.a Login as an administrator
    Go to "User Groups"
    Click the name of your external group
    See that the new user is in the group (On the left side)
    Do nothing, just click "submit"

Or
5.b Run cron job found in /etc/cron.d/foreman
    # Refreshes ldap usergroups. Can be disabled if you're not using LDAP authentication.
    */30 * * * *    foreman    /usr/sbin/foreman-rake ldap:refresh_usergroups >>/var/log/foreman/cron.log 2>&1


6. Now the user group is updated and the user is admin (user needs to log out/in again)

Version-Release number of selected component (if applicable):

Satellite 6.2.2

How reproducible:

Described above.

Actual results:

User role from LDAP is not assigned unless user logs out/in to the webui.

Expected results:

User role assigned automatically without login out and login.