Bug 1403844 - ipa Client failes to join when ca.cert is missing
Summary: ipa Client failes to join when ca.cert is missing
Keywords:
Status: CLOSED DUPLICATE of bug 1387779
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: ipa
Version: 7.3
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: rc
: ---
Assignee: IPA Maintainers
QA Contact: Kaleem
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-12-12 13:41 UTC by Kim Borup
Modified: 2020-01-17 16:19 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-12-12 14:40:03 UTC
Target Upstream Version:


Attachments (Terms of Use)

Description Kim Borup 2016-12-12 13:41:08 UTC
Description of problem:
When you have a replica Setup, the replica is not making a copy of the ca to /usr/share/ipa/html/ca.crt, making ipa-client-install --Password= fail if a replica is hit, due to the Ca.crt missing. 

ls -l /usr/share/ipa/html/ca.crt will come out empty
Where on Server 1 it will be there. 

Check missing in replica install for ca.crt

And Client Needs to say if it can not download a ca.crt instead of giving wrong Password. 


Version-Release number of selected component (if applicable):
ipa-client-common-4.4.0-12.el7.noarch
ipa-client-4.4.0-12.el7.x86_64

ipa-server-4.4.0-12.el7.x86_64
ipa-server-dns-4.4.0-12.el7.noarch
ipa-server-common-4.4.0-12.el7.noarch
ipa-server-trust-ad-4.4.0-12.el7.x86_64

How reproducible:
Always

Steps to Reproduce:
1. Install IPA-server
2. Create Ad-Trust
3. setup-replica of IPA Server
4. Create Client ipa host-add hostname.example.com --Password=flaf
5. on Client ipa-client-install --Password=flaf
6. If IDM Server 1 is hit it will work, if replica is hit 

Actual results:
Server Fails with Password wrong. 

Expected results:
Server joined the AD.

Additional info:

Comment 2 Kim Borup 2016-12-12 14:40:03 UTC

*** This bug has been marked as a duplicate of bug 1387779 ***


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