Need Authentication and Authorization Mechanisms for Exposed HTTP Endpoint

Is your feature request related to a problem?
Yes. In our current implementation of Prometheus Exporter, we take a string parameter to configure the HTTP we want to expose in the constructor. Then the Prometheus server will scrape the metrics data from that HTTP endpoint. However, besides the Prometheus server, anyone else can also send HTTP GET request to that endpoint and scrape data, which will cause two problems:

1. The metrics data we exported is not secure, because anyone can get the data without permission as simply as visiting the exposed endpoint in the browser.
2. The data we served is one-time, which means that they can only be scraped once. If someone else takes the data away before a Prometheus pull request comes, Prometheus will not receive that batch of data and results in a data loss.

Describe the solution you'd like
Adding some authentication and authorization mechanism to the HTTP endpoint we exposed, so that only authorized target Prometheus instance can read and fetch the data we exported from the HTTP endpoint.

Start by locating the Prometheus Exporter constructor that accepts the HTTP endpoint configuration and the code serving that endpoint. Define an authentication and authorization approach that permits only the target Prometheus instance to fetch the exported data, then verify that unauthorized requests are rejected without disrupting authorized scrapes.