Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[ifw-api] PS daemon: pick up new certificate once changed by Icinga #632

Closed
Al2Klimov opened this issue Jun 5, 2023 · 2 comments · Fixed by #690
Closed

[ifw-api] PS daemon: pick up new certificate once changed by Icinga #632

Al2Klimov opened this issue Jun 5, 2023 · 2 comments · Fixed by #690
Milestone

Comments

@Al2Klimov
Copy link
Member

Current Behavior

(At least if you're not using tickets to sign Icinga cluster nodes,) Icinga will run with a self signed certificate until I do icinga2 ca sign .... Your PS daemon (having no choice) picks up the initial self signed certificate and runs with that until restarted. But its API clients such as

Will require an actually Icinga CA signed certificate and complain/fail.

Expected Behavior

The PS daemon stat(2)s the certificate file either periodically or on hint from ReadDirectoryChangesW(). Changed? Reload!

Possible Solution

At least consider a KB entry in the upcoming version.

Steps to Reproduce (for bugs)

  1. Install IfW as usual
  2. Use no ticket
  3. Never restart the PS daemon
  4. Query IfW API

Context

@LordHepipud
Copy link
Collaborator

Thank you for the issue. If you do not sign the certificate, the Icinga for Windows installer should print a warning during the activation of the REST-Api, that the certificate has not been signed yet.

Can you confirm this?

@Al2Klimov
Copy link
Member Author

Not sure how this matters here. I know that I've signed the certificate not right now, but (say) one minute later. Icinga auto-picks up that signed cert, but AKAIK PSd doesn’t.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants