RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1313458 - cloning CA: Failed to obtain installation token from security domain
Summary: cloning CA: Failed to obtain installation token from security domain
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: pki-core
Version: 7.2
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Matthew Harmsen
QA Contact: Asha Akkiangady
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-03-01 16:01 UTC by German Parente
Modified: 2019-10-10 11:23 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-03-03 16:39:44 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description German Parente 2016-03-01 16:01:12 UTC
Description of problem:

When installing a replica, pkispawn is failing at SystemConfigService.
Authentication is failing in master CA.

I am sorry about logging this bug. It's probably not a bug but a configuration issue but I cannot realise from log what's the issue.

These are the extract of logs in master and in replica in the moment of failure:


in master:

=======================================
[26/Feb/2016:11:32:48][TP-Processor1]: according to ccMode, authorization for servlet: caGetCookie is LDAP based, not XML {1}, use default authz mgr: {2}.
[26/Feb/2016:11:32:48][TP-Processor1]: GetCookie init
[26/Feb/2016:11:32:48][TP-Processor1]: CMSServlet:service() uri = /ca/admin/ca/getCookie
[26/Feb/2016:11:32:48][TP-Processor1]: CMSServlet::service() param name='url' value='https://ipa7.istat.it:443/ca/admin/console/config/wizard?p=5&subsystem=CA'
[26/Feb/2016:11:32:48][TP-Processor1]: CMSServlet::service() param name='uid' value='admin'
[26/Feb/2016:11:32:48][TP-Processor1]: CMSServlet::service() param name='pwd' value='(sensitive)'
[26/Feb/2016:11:32:48][TP-Processor1]: CMSServlet: caGetCookie start to service.
[26/Feb/2016:11:32:48][TP-Processor1]: GetCookie start
[26/Feb/2016:11:32:48][TP-Processor1]: GetCookie before auth, url =https://ipa7.istat.it:443/ca/admin/console/config/wizard?p=5&subsystem=CA
[26/Feb/2016:11:32:48][TP-Processor1]: IP: 10.18.103.43
[26/Feb/2016:11:32:48][TP-Processor1]: AuthMgrName: passwdUserDBAuthMgr
[26/Feb/2016:11:32:48][TP-Processor1]: CMSServlet: no client certificate found
[26/Feb/2016:11:32:48][TP-Processor1]: Authentication: UID=admin
[26/Feb/2016:11:32:48][TP-Processor1]: In LdapBoundConnFactory::getConn()
[26/Feb/2016:11:32:48][TP-Processor1]: masterConn is connected: true
[26/Feb/2016:11:32:48][TP-Processor1]: getConn: conn is connected true
[26/Feb/2016:11:32:48][TP-Processor1]: getConn: mNumConns now 2
[26/Feb/2016:11:32:48][TP-Processor1]: LdapAnonConnFactory::getConn
[26/Feb/2016:11:32:48][TP-Processor1]: LdapAnonConnFactory.getConn(): num avail conns now 2
[26/Feb/2016:11:32:48][TP-Processor1]: returnConn: mNumConns now 3
[26/Feb/2016:11:32:48][TP-Processor1]: returnConn: mNumConns now 2
[26/Feb/2016:11:32:48][TP-Processor1]: SignedAuditEventFactory: create() message=[AuditEvent=AUTH_FAIL][SubjectID=$Unidentified$][Outcome=Failure][AuthMgr=passwdUserDBAuthMgr][AttemptedCred=$Unidentified$] authentication failure

[26/Feb/2016:11:32:48][TP-Processor1]: GetCookie authentication failed
[26/Feb/2016:11:32:48][TP-Processor1]: mErrorFormPath=/admin/ca/securitydomainlogin.template
[26/Feb/2016:11:32:48][TP-Processor1]: CMSServlet: curDate=Fri Feb 26 11:32:48 CET 2016 id=caGetCookie time=26
=================================================

in replica
=================================================
[26/Feb/2016:11:32:46][http-bio-8443-exec-3]: SystemConfigService: configure()
[26/Feb/2016:11:32:46][http-bio-8443-exec-3]: SystemConfigService: request: ConfigurationRequest [pin=XXXX, token=Internal Key Storage Token, tokenPassword=XXXX, securityDomainType=existingdomain, securityDomainUri=https://ipa1.istat.it:443, securityDomainName=null, securityDomainUser=admin, securityDomainPassword=XXXX, isClone=true, cloneUri=https://ipa1.istat.it:443, subsystemName=CA ipa7.istat.it 8443, p12File=/tmp/ca.p12, p12Password=XXXX, hierarchy=root, dsHost=ipa7.istat.it, dsPort=389, baseDN=o=ipaca, bindDN=cn=Directory Manager, bindpwd=XXXX, database=ipaca, secureConn=false, removeData=true, replicateSchema=false, masterReplicationPort=7389, cloneReplicationPort=389, replicationSecurity=TLS, systemCerts=[com.netscape.certsrv.system.SystemCertData@2681e1f], issuingCA=https://ipa1.istat.it:443, backupKeys=true, backupPassword=XXXX, backupFile=/etc/pki/pki-tomcat/alias/ca_backup_keys.p12, adminUID=null, adminPassword=XXXX, adminEmail=null, adminCertRequest=null, adminCertRequestType=null, adminSubjectDN=null, adminName=null, adminProfileID=null, adminCert=null, importAdminCert=false, generateServerCert=true, standAlone=false, stepTwo=false, authdbBaseDN=null, authdbHost=null, authdbPort=null, authdbSecureConn=null, caUri=null, kraUri=null, tksUri=null, enableServerSideKeyGen=null, importSharedSecret=null, generateSubsystemCert=null, sharedDB=false, sharedDBUserDN=null, createNewDB=true, setupReplication=True, subordinateSecurityDomainNamenull]
[26/Feb/2016:11:32:46][http-bio-8443-exec-3]: === Token Panel ===
[26/Feb/2016:11:32:46][http-bio-8443-exec-3]: === Security Domain Panel ===
[26/Feb/2016:11:32:46][http-bio-8443-exec-3]: Joining existing security domain
[26/Feb/2016:11:32:46][http-bio-8443-exec-3]: Resolving security domain URLhttps://ipa1.istat.it:443
[26/Feb/2016:11:32:46][http-bio-8443-exec-3]: Getting security domain cert chain
[26/Feb/2016:11:32:47][http-bio-8443-exec-3]: Getting install token
[26/Feb/2016:11:32:48][http-bio-8443-exec-3]: Getting install token
[26/Feb/2016:11:32:48][http-bio-8443-exec-3]: Getting old cookie
[26/Feb/2016:11:32:48][http-bio-8443-exec-3]: Token: null
[26/Feb/2016:11:32:48][http-bio-8443-exec-3]: Install token is null
[26/Feb/2016:11:32:48][http-bio-8443-exec-3]: Failed to obtain installation token from security domain
===============================================

Seems rather clear to me that authentication with uid=admin is failing. But I cannot find from the source code how the admin password is obtained. And if it's simple authentication or cert based.


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

pki-server-10.2.5-6.el7


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