Bug 1409642

Summary:	passsync install guide describes to use secure port but the non-secure one is shown in the graphic
Product:	Red Hat Directory Server	Reporter:	German Parente <gparente>
Component:	Doc-installation-guide	Assignee:	Marc Muehlfeld <mmuehlfe>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Viktor Ashirov <vashirov>
Severity:	low	Docs Contact:
Priority:	unspecified
Version:	10.0	CC:	gparente, rhel-docs
Target Milestone:	---	Keywords:	EasyFix
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-01-17 08:26:03 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description German Parente 2017-01-02 17:20:07 UTC

Description of problem:

in this url:

https://access.redhat.com/documentation/en-US/Red_Hat_Directory_Server/10/html/Installation_Guide/Install_the_Password_Sync_Service.html

we can see that it's described in 7:


7. Fill in the Directory Server hostname (or IPv4 or IPv6 address), secure port number ...

But the graphic is showing 389 in port number which could be confusing.

I would prefer to have 636 in the graphic because 389 is normally used as non-secure port.

Thanks !

Comment 1 Marc Muehlfeld 2017-01-03 10:39:13 UTC

I replaced the screen capture in the DS9, 10.0, 10.1, and master branch of the guide.

Additionally I fixed:
- Step 3 showed "Red Hat Enterprise Linux" instead "Red Hat Directory Server"
- Step 4 (DS 10.x only): I removed the information about selecting the architecture. There is only 64-bit for RHEL7.
- Step 4 (DS 9): The package download for DS 9 is named "WinSync" and not "PassSync". I replaced the package name in step 4, while keeping "PassSync" in all other steps, because this is the name of the tool, which is also shown in the window title.

Comment 7 Marc Muehlfeld 2017-01-17 08:26:03 UTC

The update is now available on the Customer Portal.