Note - the GitHub issue linked above is closed with the following, but I would disagree with it as it means your tile server serving your custom maps would need to be exposed!
For general purpose web-apps like Kibana, it's reasonable to expect that the tile-servers are not behind an authentication layer.
You are correct, there is no functionality for authentication with an external map server. Solution are there, like proxies or firewall configs and so on.
If you just want to test one without authentication, you can check the mundialis WMS.
I don't have an instance to try this on currently, but do you know if it would work with Basic Authentication if the URL was entered as such?
To be clear, what if the map.tilemap.url setting was set with a value such as https://user:pass@tileserverbox.com? Would Kibana reject this URL, or would it feed this to the browser, and the browser would then create the connection?
My use case is that I do not care if my users are able to directly navigate to my tile server (as their browser would make the map connection) but I still want to protect it against random Internet users from discovering and (ab)using the service.
Well - it's not wrong, it does indeed contain embedded credentials! I wonder if it'd just work if it didn't reject it (i.e. perhaps the browser would read it as intended).
Edit: Actually, I think the error message is from the browser (Firefox). I guess it just rejects it when it's from a different source?
Apache, Apache Lucene, Apache Hadoop, Hadoop, HDFS and the yellow elephant
logo are trademarks of the
Apache Software Foundation
in the United States and/or other countries.