Stale Cached Permissions on Re-Login

Discussion created by on Aug 29, 2016
Latest reply on Feb 9, 2017 by Daniel Farnan

Product and version: FileMaker Server / Pro

OS and version: Windows Server 2008 R2 (DB), Windows Server 2012 R2 (WPE/Client) / Windows 7 Professional SP1 (Client)

Browser and version: Google Chrome Version 49.0.2623.87 m

Reproducable: Consistent on WebDirect and FileMaker Pro Advanced (installed on Server or workstation).

Description: Database has an auto-login using an account with minimal permissions ("Login"). Login has script execution limitations (can only execute specified scripts). Database subsequently logs in as another account based on user input ("User"). User has execution permission for all scripts. When attempting to execute a script under User after re-login, if script was NOT permissible under Login, returns error code 9.

How to replicate:

Scripts: ScriptA, ScriptB, ScriptC

Accounts: Login (execute ScriptA, no access ScriptB/ScriptC), User (execute all scripts)

Steps: Log in as Login. Re-login as User. Attempt to execute ScriptA, executes normally. Attempt to execute ScriptB or ScriptC, returns error code 9.

Workaround: Enable executable permissions for Login account for all scripts and enforce permissions manually in non-permissible scripts.