Clarification on URL based discovery

[shikhasingh]

Hi All,

We are trying to explore URL discovery .

When looking into the documents it mentions two table that looks similar.

•  Certificate Discovery Source URLS
• HTTP(s) Endpoint [cmdb_ci_endpoint_http]

I am clear about certificate discovery Source URL table that my discovery will scan the URL's that have been included in my schedule from this table.

I do not understand what is the use of HTTP Endpoint ? How it will make difference in discovery if I check and or uncheck this in discovery schedule.

In document below line is mentioned what does that mean?

When your Discovery schedule runs, it automatically scans for any certificates on the specified URLs and fetches all URLs from the cmdb_ci_endpoint_http table.

TIA

[Appli]

Hi, the use case here - Service Mapping creates a CI record in HTTPs endpoints CI Class (cmdb_ci_endpoint_http) and a relationship between this HTTPs endpoint and associated application.

URL certificate discovery creates an additional relationship between the certificate and application, to "find" application it uses relations (HTTPs endpoint -> Application) set by Service Mapping before.

[shikhasingh]

@Appli 

Thanks for quick  response.

So it means it will only create relationship between the certificate and application, if we check this checkbox in discovery schedule and there is already existing relations between HTTPS endpoint and application?

What if we enable this checkbox but not relations exists between HTTPS endpoint and application?