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

Service Import source is missing chain id #237

Open
slalomsk8er opened this issue Apr 15, 2024 · 0 comments
Open

Service Import source is missing chain id #237

slalomsk8er opened this issue Apr 15, 2024 · 0 comments

Comments

@slalomsk8er
Copy link
Contributor

slalomsk8er commented Apr 15, 2024

Is your feature request related to a problem? Please describe.

If a service x509 - HOST/IP:PORT is imported into the director there isn't a direct way to navigate back from the service in the monitoring module to the details of the checked chain in the x509 module.

Describe the solution you'd like

If the chain id would be exposed by the import source a deep link into the x509 module could be created via Navigation service-action.

Describe alternatives you've considered

My current workaround:

USER: *
GROUP: *
URL: x509/usage?certificate.chain.target.hostname=$_service_icingacli_x509_host$&certificate.chain.target.ip=$_service_icingacli_x509_ip$&certificate.chain.target.port=$_service_icingacli_x509_port$
FILTER: _service_icingacli_x509_host!=

But I found discrepancies between the check output and the x509 usage in the remaining validity and I'm not sure if the same chain is used! #232

x509 widget

A x509 widget hooking into the monitoring module when check icingacli x509 is used would also be possible integration back into to x509 module.

Additional context

image

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

No branches or pull requests

1 participant