Project

General

Profile

Actions

Bug #14868

closed

After satellite upgrade to 6.1.4 'Usergroup sync' under ldap authentication gets enabled automatically

Added by Daniel Lobato Garcia almost 8 years ago. Updated over 7 years ago.

Status:
Resolved
Priority:
Normal
Category:
Authentication
Target version:
-
Difficulty:
Triaged:
Fixed in Releases:
Found in Releases:

Description

Cloned from https://bugzilla.redhat.com/show_bug.cgi?id=1284832
Description of problem:
After upgrading satellite to version 6.1.4 the 'Usergroup Sync' under Ldap Authentication get enabled automatically.

Version-Release number of selected component (if applicable):
Red Hat Satellite 6.1.4

How reproducible:
Always

Steps to Reproduce:
1. On Satellite 6.1.3 or below version. Satellite webui --> Administer --> Ldap Authentication --> Click on name --> Account --> here uncheck the 'Usergroup Sync' is present --> Save
2. Upgrade satellite to 6.1.4 by performing steps from installation guide.
https://access.redhat.com/documentation/en-US/Red_Hat_Satellite/6.1/html-single/Installation_Guide/index.html#sect-Red_Hat_Satellite-Installation_Guide-Upgrading_Red_Hat_Satellite_Server_and_Capsule_Server-Upgrading_Red_Hat_Satellite

3. Satellite webui --> Administer --> Ldap Authentication --> Click on name --> Account --> here the 'Usergroup Sync' is checked

Actual results:
'Usergroup Sync' is enabled automatically resulting in login failure.

Expected results:
Upgrade should not automatically enable 'Usergroup Sync' and should maintain configuration.

Additional info:

Actions #1

Updated by Dominic Cleal almost 8 years ago

  • Status changed from New to Need more information

Not a very useful bug report with regards to Foreman, there's no context... which upstream versions does this upgrade correspond to? 1.10 to 1.11?

Actions #2

Updated by Bryan Kearney almost 8 years ago

  • Bugzilla link changed from 1284832 to 1315268
Actions #3

Updated by Ivan Necas over 7 years ago

  • Category set to Authentication
Actions #4

Updated by Daniel Lobato Garcia over 7 years ago

  • Status changed from Need more information to Resolved

Closing as this was about that flag being enabled when migrating to 1.11 when it was introduced and not about us changing that property from what false to true on a migration.

Actions

Also available in: Atom PDF