TPS: tps-authenticator cli is not able to add authenticator source

[pki-bot]

This issue was migrated from Pagure Issue #2297. Originally filed by gkapoor (@geetikakay) on 2016-04-25 20:24:14:

• Assigned to nobody
• Associated bugzillas
  • https://bugzilla.redhat.com/show_bug.cgi?id=1323661

---

tps-authenticator cli is not able to add authenticator source under which we
can add properties.

example : to add properties under authenticator "ldap2",ldap2 should be created
like we did in TPS UI.

Example :

pki -d . -n "PKI Administrator for os1.phx2.redhat.com" -c redhat
tps-authenticator-add --input input
IllegalArgumentException: Arguments must not be null

Steps to Reproduce:

1. Run command:

pki -d . -n "PKI Administrator for os1.phx2.redhat.com" -c redhat
tps-authenticator-add --input input

Actual results:

IllegalArgumentException: Arguments must not be null
}}

Expected results:

Authenticator i.e LDAP here should get added.

Additional info:

input file :

auths.instance.ldap2.authCredName=uid auths.instance.ldap2.externalReg.certs.recoverAttributeName=certsToAdd auths.instance.ldap2.externalReg.cuidAttributeName=tokenCUID auths.instance.ldap2.externalReg.tokenTypeAttributeName=tokenType auths.instance.ldap2.ldap.basedn=ou=People,dc=example,dc=org auths.instance.ldap2.ldap.ldapauth.authtype=BasicAuth auths.instance.ldap2.ldap.ldapauth.clientCertNickname=subsystemCert cert-Foobar auths.instance.ldap2.ldap.ldapconn.host=geetikakay-local.os1.phx2.redhat.com auths.instance.ldap2.ldap.ldapconn.port=1389 auths.instance.ldap2.ldap.ldapconn.secureConn=False auths.instance.ldap2.ldap.ldapconn.version=3 auths.instance.ldap2.ldap.maxConns=15 auths.instance.ldap2.ldapStringAttributes=mail,cn,uid auths.instance.ldap2.ldapStringAttributes._000=################################ # auths.instance.ldap2.ldapStringAttributes._001=# For isExternalReg auths.instance.ldap2.ldapStringAttributes._002=# attributes will be available as auths.instance.ldap2.ldapStringAttributes._003=# $$ auths.instance.ldap2.ldapStringAttributes._004=# attributes example: auths.instance.ldap2.ldapStringAttributes._005=#mail,cn,uid,edipi,pcc,firstname ,lastname,exec-edipi,exec-pcc,exec-mail,certsToAdd,tokenCUID,tokenType auths.instance.ldap2.ldapStringAttributes._006=################################ # auths.instance.ldap2.pluginName=UidPwdDirAuth auths.instance.ldap2.ui.description.en=This authenticates user against the LDAP directory. auths.instance.ldap2.ui.id.PASSWORD.credMap.authCred=pwd auths.instance.ldap2.ui.id.PASSWORD.credMap.msgCred.extlogin=PASSWORD auths.instance.ldap2.ui.id.PASSWORD.credMap.msgCred.login=password auths.instance.ldap2.ui.id.PASSWORD.description.en=LDAP Password auths.instance.ldap2.ui.id.PASSWORD.name.en=LDAP Password auths.instance.ldap2.ui.id.UID.credMap.authCred=uid auths.instance.ldap2.ui.id.UID.credMap.msgCred.extlogin=UID auths.instance.ldap2.ui.id.UID.credMap.msgCred.login=screen_name auths.instance.ldap2.ui.id.UID.description.en=LDAP User ID auths.instance.ldap2.ui.id.UID.name.en=LDAP User ID auths.instance.ldap2.ui.retries=3 auths.instance.ldap2.ui.title.en=LDAP Authentication ```

[pki-bot]

Comment from mharmsen (@mharmsen) at 2016-04-25 20:28:46

Per CS/DS Meeting of 04/25/2016: 10.4

• only used in rare situations
• recent changes to CLI may have already addressed this

[pki-bot]

Comment from gkapoor (@geetikakay) at 2017-02-27 14:01:27

Metadata Update from @geetikakay:

• Issue set to the milestone: UNTRIAGED

[pki-bot]

Comment from mharmsen (@mharmsen) at 2017-03-03 20:12:26

Metadata Update from @mharmsen:

• Custom field feature adjusted to ''
• Custom field proposedmilestone adjusted to ''
• Custom field proposedpriority adjusted to ''
• Custom field reviewer adjusted to ''
• Custom field version adjusted to ''
• Issue close_status updated to: None
• Issue set to the milestone: 10.4 (was: UNTRIAGED)

[pki-bot]

Comment from mharmsen (@mharmsen) at 2017-08-09 12:45:51

Per CS/DS Meeting of August 7, 2017, it was determined to move this issue from 10.4 ==> FUTURE.

[pki-bot]

Comment from mharmsen (@mharmsen) at 2017-08-09 12:45:51

Metadata Update from @mharmsen:

• Issue set to the milestone: FUTURE (was: 10.4)