It should be enough to grant access to the specific connection. Can you run the workspace on Flow as a regular, logged-in, user?

Yes. In fact if I go into the log of the failed process, i can resubmit the job, and it works perfectly

Hey Keith,

When you say access, can I confirm that is access to the specific connection, rather than access to the broader connections. e.g.

The other one to confirm is to look at the parameter FME_SECURITY_ROLES in the log file, and just ensure that the token you are updating is the correct one.

Cheers,

Todd

Hi Todd,

The access to the connections looks exactly like your example for each of the users. I have specifically shared the database connection to the users.

As for the FME_SECURITY_ROLES, I have 

--FME_SECURITY_ROLES' ` "token:KHastings.Workspace<space>App<space>-<space>ExternalUserName"]'

I’m not exactly sure what I am expecting to see here, but the ExternalUsername bit does match the FME username that is trying to use the app.

Cheers

keith

Hey Keith,

Its that token you need to update, rather than the users. That is, the users don’t need to have access to the connection, it is the token that needs access.

So you need to to find the token starting with Workspace App  ExternalUserName

under:

<server>/fmeserver/tokens/all

Then give that token the access to the connection.

Cheers,

Todd

Thanks Todd, that seems to be it.

None of those tokens had access, so I have added that, and will cross my fingers for the next bit of data that comes in.

I presume restoring the connection access is so convoluted because of the change in connection styles, and just creating something from scratch would be much more straightforward.

Cheers

keith