extensions-api Idea: Enable specific extensions wildcard on Tableau Server

I'm sorry for all the issues, I guess I feel inspired by the TC.

It would be cool to use wildcards (*) to enable extensions on Tableau Server. We have pretty long generated Extension URLs and when customers use multiple extensions from our platform they need to enable them all separately.

Instead of adding all the urls, something like this could work:

Oct 31 '18 14:10 merlijnbuit

Thanks for the ideas. We appreciate them! Multiple requests have come for handling wildcards in the whitelist. Thanks for adding your vote. We will get it added to our backlog. John

Oct 31 '18 16:10 johnDance

@merlijnbuit: What is the list of you think would be useful to do with wildcards?

extensions.appsfortableau.com/* is the obvious one...
What about *.appsfortableau.com ?
What about extensions.appsfortableau.com/extension* ? Any others? Would you want full regex?

Nov 05 '18 18:11 Kovner

The first and second one would be useful. I guess you can host extensions as a subdomain or a subfolder which will both work

Nov 06 '18 15:11 merlijnbuit

Wildcards will be supported in 2023.1. It is a full regex. https://extensions.appsfortableau.com/.* would be the proper form for your example. Site administrators need to be careful to not be too broad in their specifications. They should always include a host in the specification.

John

Jan 12 '23 23:01 johnDance

I'm sorry we were late to mark this issue as fixed. The change was in fact included in Server 2023.1 (and future versions). I will also get the help docs updated to make it clear.

FYI @merlijnbuit

Mar 15 '24 16:03 bcantoni