Hi Manu, is there a reason you're not using the Guest user capability?
Hey Manu -
Since you have a core license, you're OK on the "staying legal" side of things. However, there is still some risk that you will need to consider. I used to work alot with OEM customers who embed Tableau into their apps as it sounds like you're doing. They often wanted to simplify their lives by sending all traffic through a single "proxy user".
You've already mentioned (and discounted) how this will effectively break personalization/customization for you. Cool. There's also auditing / security: If you ever have an evil user and you need to track down "bad stuff" that they've done after the fact, you're going to be in "needle in a haystack land" since the only thing you'll have to uniquify the sessions in Tableau will be the client's IP address.
Finally, there's the fact that Tableau doesn't test "many" users logged in at the same time. It works, but the behavior hasn't been tested at scale. It might function perfectly for you, or at some point in the future it could fall down when you get to <some number of users> + 1. A great big question mark that would personally make me feel very uncomfortable.
So, there you go. Most of the OEMs I used to talk to would err on the side of "more complexity" (more users) so they could sleep well at night
Sounds like Manu needs a basic level of authentication vs. leaving the server wide open to anyone who knows where the vizzes are.
Thanks Russell, This is very helpful.
You are spot-on WRT why I am using a single 'proxy user'.
Regarding the risks you highlighted :
2. hitting the untested limit of concurrent session: Any idea on what would be the normal 'tested' limit ?