They also somehow provided us with a URL to the dashboard with an auth token in it which would be valid forever and thus should not be shared.

+1

This is all I have left from the Atlassian partner that config'd this for us long ago - OBSS was the partner
-------------------------------------------------
I have developed a different and more elegant solution to allow unauthorized access to a certain Jira endpoints from a specified list of IPs. In my new solution, we do not need to write any extra PHP scripts, install and configure PHP etc. Basically we are going to check IP address and user agent of the client that make request and add authentication header if all the conditions are met. Here are the conditions that must be met:

1. The reqeust must be made to Jira wallboard endpoint (ie. /jira/plugins/servlet/Wallboard)
2. The request must be made from an allowed IP address (We can define multiple)
3. The client that made request must have allowed user-agent (ie. Zoom Rooms Digital Signage) signature. This is an extra precaution to prevent possible HTTP session conflicts with the real users who share same public IP address with Zoom Rooms Digital Signage.

All of the above conditions must met in order to pass client to Jira as an authenticated-user. This solution needs only Apache configuration modification on Atlas server, we need to access and modify Apache configuration file(s) accordingly.

Also looking for this from customer requests

Yes please

+1 I'm in too! Need this feature despite the issue beeing closed already

yeah its shame they dont have this. We would love this capability as well 

Please can reconsider allowing  wallboards/ kanban boards to be publicly viewable?  We want to display our kanban boards for various project  on interoffice tv's w/o having to login as a user or setup an additional account. 

+1 Banging my head up against the same thing

@paul Same same! +1