Bug 1285262 - Provide an outline of the new Usergroup sync check box
Summary: Provide an outline of the new Usergroup sync check box
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Documentation
Version: Unspecified
Hardware: Unspecified
OS: Unspecified
high
low
Target Milestone: Unspecified
Assignee: Peter Ondrejka
QA Contact: Russell Dickenson
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-11-25 10:13 UTC by Andrew Dahms
Modified: 2019-12-16 05:07 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-04-28 00:01:57 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Andrew Dahms 2015-11-25 10:13:46 UTC
In Red Hat Satellite 6.2, there is a new checkbox under Administer > LDAP Authentication > New authentication source > Account that configures LDAP user group membership synchronization.

A description of this check box must be added to the documentation, in addition to a brief outline of why users would want to enable to disable this check box.

Comment 1 Andrew Dahms 2015-11-30 02:14:37 UTC
Assigning to Peter for review.

Comment 2 Peter Ondrejka 2015-11-30 13:36:19 UTC
I added this option to step 4 in procedure 20.1, preview at:

http://file.brq.redhat.com/~pondrejk/user-guide/#sect-Red_Hat_Satellite-User_Guide-Using_Configuring_TLS_for_Secure-LDAP

Commit:

https://gitlab.sat.lab.tlv.redhat.com/satellite6-docs/user-guide/commit/879d20098d12c506c864530d1f29f86acc93ab09

Daniel, according to the team roster (https://docs.google.com/spreadsheets/d/1G7Wo-cTiTbl-1th0E__1Rc7oKPAoViy7zTUQqBNK62Q/edit#gid=0) you know abbout LDAP. Can you please check if the formulation added above id correct?

Cheers

Comment 3 Daniel Lobato Garcia 2015-12-10 09:25:47 UTC
Peter, that's exactly what that checkbox does. Thanks!

Comment 7 Andrew Dahms 2016-04-28 00:01:57 UTC
This content is now live on the Customer Portal.

Closing.


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