Learn more about these different git repos.
Other Git URLs
Folks in the process of debugging an issue I had with a helper I am writing I noticed the following issue (Ignore the cookie, that was my bug that I was debugging): 2017-09-21 21:27:06 [18581] Request3('20170922032649') provided CA cookie "300 550228 " 2017-09-21 21:27:06 [18581] Request3('20170922032649') moved to state 'CA_WORKING' 2017-09-21 21:27:06 [18581] Will revisit Request3('20170922032649') in 604800 seconds.
604800 seconds, is if I am doing this right, 7 days. This appears to be the default time that is used and that is a bit unreasonably long to check (again) for a cert to be issued by a CA.
Can this be adjusted to something more reasonable (I know exit 5 exists and I am using that because of this issue but it seems like it should be fixed in certmonger itself)?
Thanks, -Erinn
Many CA's need to manually issue a certificate after doing a security review of the requester. The default is a guess on how long this might take.
Using CM_SUBMIT_STATUS_WAIT_WITH_DELAY is the correct way to customize this value (freeIPA uses this as well).
Yeah that is fair enough, 7 days just seemed a bit extreme for another poll request. But I understand where you are coming from. Perhaps adding a note in the helpers.txt file stating the default is 7 days would be helpful, I was expecting repolling on the order of minutes to hours. I'll make a quick PR for that.
Metadata Update from @erinn: - Issue close_status updated to: invalid - Issue status updated to: Closed (was: Open)
Login to comment on this ticket.