#2536 Deprecating generic pki user/group commands
Closed: fixed Opened by edewata.

Currently user/group management can be done using the following generic commands:

  • pki user-*
  • pki group-*

By default these commands will be directed to CA subsystem. To manage users/groups in other subsystem, the subsystem name can be specified in the server URL, for example:

$ pki -U https://server.example.com:8443/kra ... user-find

To simplify CLI usage, ideally the server URL should be identical for all CLI commands directed to the same server, so the subsystem name should not be included in the server URL. Instead, the subsystem name should be specified as part of the command name:

  • pki ca-user/group-*
  • pki kra-user/group-*
  • pki ocsp-user/group-*
  • pki tks-user/group-*
  • pki tps-user/group-*

The above commands have already existed for some time. Most of these commands are identical except that the tps-user command might have specific input parameters/output for TPS user profiles.

In the future there might be more subsystem-specific input parameters/output, so it would make sense to deprecate the generic user/group commands now, and potentially remove them in the future.


Per PKI Bug Council of 11/10/2016: 10.4 - minor

Linked to Bugzilla bug: https://bugzilla.redhat.com/show_bug.cgi?id=1394069

Metadata Update from @edewata:
- Issue set to the milestone: UNTRIAGED

Metadata Update from @mharmsen:
- Custom field feature 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)

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

Metadata Update from @mharmsen:
- Issue set to the milestone: FUTURE (was: 10.4)

Metadata Update from @mharmsen:
- Issue set to the milestone: 10.5 (was: FUTURE)

Metadata Update from @mharmsen:
- Custom field lowhangingfruit adjusted to vakwetu: X

[20171025] - Offline Triage ==> 10.6

Metadata Update from @mharmsen:
- Issue set to the milestone: 10.6 (was: 10.5)

Fixed in master:

  • https://github.com/dogtagpki/pki/commit/156f1883fc44cf40c34fcf79987ec3a64cfd9ce8
  • https://github.com/dogtagpki/pki/commit/96df98aaa73dd51f8c19a0fad0b0c4bf3239f9a4
  • https://github.com/dogtagpki/pki/commit/5b73386fd0c2f37a6ef231701a5d6d279a2fab46

Metadata Update from @edewata:
- Issue close_status updated to: fixed
- Issue set to the milestone: 10.6.0 (was: 10.6)
- Issue status updated to: Closed (was: Open)

Per 10.5.x/10.6 Triage: 10.5.x

Metadata Update from @mharmsen:
- Issue set to the milestone: 10.5 (was: 10.6.0)

Metadata Update from @mharmsen:
- Issue set to the milestone: 10.6.0 (was: 10.5)

Dogtag PKI is moving from Pagure issues to GitHub issues. This means that existing or new
issues will be reported and tracked through Dogtag PKI's GitHub Issue tracker.

This issue has been cloned to GitHub and is available here:
https://github.com/dogtagpki/pki/issues/2656

If you want to receive further updates on the issue, please navigate to the
GitHub issue and click on Subscribe button.

Thank you for understanding, and we apologize for any inconvenience.

Metadata