#1003 TPS authenticator lifecycle management
Closed: migrated 3 years ago by dmoluguw. Opened 9 years ago by edewata.

Currently TPS authenticators will only be initialized/started during initial server startup. The current REST interface for authenticators only manages the configuration. If an authenticator is added, edit, or removed, the change wouldn't become effective until the next server restart.

There should be a mechanism (via REST interface) to manage TPS authenticator lifecycle while the server keeps running. Here are the possible states of an authenticator:

  • disabled
  • enabled, stopped
  • enabled, initializing (resources being started, not fully ready yet)
  • enabled, running
  • enabled, shutting down (resources being stopped)

Note that the configuration can still be edited any time, but the changes will become effective only after restarting the authenticator (not the whole server). Or it's also possible to allow editing only when the authenticator is stopped.

Enabled authenticator will start automatically during server startup. To remove an authenticator the authenticator must be stopped first.

If editing approval process is required, the states can be expanded as follows:

  • configuration
  • pending approval
  • approved, disabled
  • approved, enabled, stopped
  • approved, enabled, initializing
  • approved, enabled, running
  • approved, enabled, shutting down

In this case editing can only be done while in configuration state.


Proposed milestone: 10.3

Per PKI/389 Meeting of 05/19/2014, moving to Milestone 10.3.

This requires:

  • writing the REST service and client
  • adding UI to display/manage TPS authenticators

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

7 years ago

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/1569

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 Update from @dmoluguw:
- Issue close_status updated to: migrated
- Issue status updated to: Closed (was: Open)

3 years ago

Login to comment on this ticket.

Metadata