#2243 [RFE]: Add functionality to perform post enroll/format operations to update reporting service.
Closed: migrated 3 years ago by dmoluguw. Opened 8 years ago by dsirrine.

What problem/issue/behavior are you having trouble with? What do you expect to
see?

Currently token format and token enrollment are done outside of TMS. In order
to perform post update for TMS after these operations, such as updating token
status and site code in the CMT database, we propose to add a function to the
Red Hat TPS code. This function will call a http service with the operation
and the token id to perform the updates that are needed for TMS. This function
will be called at the end of a successful
format or enrollment process. This function will be configurable in the CS.cfg
for whether there is post service to call.

1. TPS CS.cfg
   The following configurations will be added:
       tps.post.service.enable=true/false
       conn.post.service.hostport=<host and port number of the post service>
       conn.post.service.servlet=<path of the post service>

2. RA_Processor.cpp
        New function TPSPostService will be added to do the following:
        - This function takes 2 parameters: op, tokenId
                    op - operation that was done to the token (formatted or
enrolled in this case)
                    tokenId - the token id
        - If tps.post.service.enable is defined in CS.cfg and set to true
                      - get the post service host, port and path configuration
from CS.cfg
                      - send a http request (including the op and tokenId
parameters) to the post service
        - If tps.post.service.enable is not defined in CS.cfg or set to false
              - function returns

3.      RA_Processor.cpp:
    - Modify RA_Processor::Format() to call TPSPostService("formatted", cuid)
at the end of the function upon successful completion of the format process.

4. RA_Enroll_Processor.cpp:
    - Modify RA_Enroll_Processor::Process() to call TPSPostService("enrolled",
cuid) at the end of the function upon successful completion of the enrollment
process.

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

7 years ago

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)

7 years ago

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)

6 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/2363

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