Open pki-bot opened 4 years ago
Comment from mgrigull@redhat.com (@ciphernaut) at 2017-02-27 14:10:21
Metadata Update from @ciphernaut:
Comment from mharmsen (@mharmsen) at 2017-03-03 14:54:01
Fraser -- don't know if this is associated with other GSS API work or not.
Comment from mharmsen (@mharmsen) at 2017-03-03 14:54:05
Metadata Update from @mharmsen:
Comment from ftweedal (@frasertweedale) at 2017-03-05 19:17:11
@mharmsen it's about adding support for GSS-API authn to the cli
command line program; subsequent to the server-side implementation.
Comment from mharmsen (@mharmsen) at 2017-04-07 11:40:21
Per email correspondence with frasertweedale on 04/07/2017: 10.5
Comment from mharmsen (@mharmsen) at 2017-04-07 11:40:22
Metadata Update from @mharmsen:
Comment from vakwetu (@vakwetu) at 2017-08-31 14:25:18
client auth with personal SSL certificates has always been available for the pki CLI. Make sure you are defined as an agent and have an agent cert uploaded.
http://pki.fedoraproject.org/wiki/Handling_Certificate_Request
Propose to rename this issue to:
RFE: enable gssapi support for PKI cli
Comment from mharmsen (@mharmsen) at 2017-08-31 14:29:42
Metadata Update from @mharmsen:
Comment from mharmsen (@mharmsen) at 2018-04-10 16:51:07
Per 10.5.x/10.6 Triage: FUTURE
RHBZ: CLOSED UPSTREAM
Comment from mharmsen (@mharmsen) at 2018-04-10 16:51:09
Metadata Update from @mharmsen:
This issue was migrated from Pagure Issue #2594. Originally filed by mgrigull@redhat.com (@ciphernaut) on 2017-02-09 19:39:30:
At present we use password prompt for 'pki' tool interacting with service endpoint.
We would like to use either kerberos ticket or personal SSL certificates to authenticate with the endpoint instead of using OTP password (as per our current implementation) and also avoid needing a 'shared' account.
Use of cached credentials in either form would allow us to script certificate generation for the large number of systems we maintain.