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

Certificates: hierarchical view #29

Open
jbostoen opened this issue Apr 21, 2020 · 5 comments
Open

Certificates: hierarchical view #29

jbostoen opened this issue Apr 21, 2020 · 5 comments

Comments

@jbostoen
Copy link
Owner

Type: request

Version info:

  • iTop: 2.7
  • PHP: 7.2
  • MySQL: 5.7
  • Extension (if applicable): certificates

Description:
Hierarchical view for certificates

@Hipska
Copy link

Hipska commented Apr 21, 2020

I have something for certs laying around. Intrested?

@jbostoen
Copy link
Owner Author

Just datamodel or also something more?
Already got a bit of a class myself :)

@Hipska
Copy link

Hipska commented Apr 27, 2020

Datamodel only indeed.
Has hierarchical keys + impact relations:
image
WebApplication has a direct link, SoftwareInstance is with a link class because multiple certs can be linked.

I had a look at your implementation, but I don't agree with linking certs to Server or VM.

@jbostoen
Copy link
Owner Author

Datamodel only indeed.
Has hierarchical keys + impact relations:
image
WebApplication has a direct link, SoftwareInstance is with a link class because multiple certs can be linked.

I had a look at your implementation, but I don't agree with linking certs to Server or VM.

That's also a nice idea. Well it's still a bit of a concept. We're going to step away from the way iTop defines the software and license classes, because licenses really aren't flexible enough for us to keep track of everything and we were also struggling with software versions.

I linked it to a Server/VirtualMachine for cases where it's used for services. You could argue that's a WebApplication or SoftwareInstance and that they each might have a dedicated certificate for their purpose, but I didn't think those classes (or our interpretation of them) covered it all. For instance, what about LDAPS connections where the certificate is really tied to your server? Or we also have an instance where one of our servers has a certificate used for identification to another secure FTP server.

Using relations is a nice idea!

@Hipska
Copy link

Hipska commented Apr 27, 2020

For instance, what about LDAPS connections where the certificate is really tied to your server?

The cert is still not tied to the server, but to the LDAP service instance. (As the same server can also have other certs for other software running on the same server.)

Or we also have an instance where one of our servers has a certificate used for identification to another secure FTP server.

Are we also talking about the same kind of certificates here? Or more like public and private keys for authentication like usual on SSH connections?

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

No branches or pull requests

2 participants