Quick question; if I want to use a token to authenticate my Data Virtualization, rather than a FME Flow user, I need to build it myself, correct? (and then do that for all endpoints of course)
Question
Data Virtualisation - authentication via token / api key
+9- Safer
Hi
Data Virtualization permissions work a little differently than regular FME Flow permissions. Rather than relying on the standard role/permission model, each Data Virtualization endpoint must be assigned to a specific user, and requests to that endpoint run under that user's identity. So yes, you need to build the token yourself.
A common approach is to create a dedicated user with no other permissions, assign it to the endpoint, and then use that user's token to authenticate requests. This keeps access scoped tightly to just the Data Virtualization endpoint and nothing else in FME Flow.
You can find the full details here: https://support.safe.com/hc/en-us/articles/36098228739469-Secure-Data-Virtualization-Endpoints-with-Authentication#:~:text=In%20short%2C,it%E2%80%99s%20meant%20for.