All security for a solution is set up in FileMaker Pro Advanced without server software, making it the quicker and easier option for managing accounts.
With internal authentication (via FileMaker Pro Advanced), the account name and password are stored within the solution.
See Use functions, scripts, and script triggers to enhance security.įileMaker solutions can authenticate accounts internally, externally, or with an OAuth identity provider. Track this information by using auto-enter field settings or by using the Get(AccountName) function in calculations and scripts. This allows you to track who is creating or modifying individual records or taking other actions in your solution. See Define privilege sets.Ĭreate a unique account for each user. Each account is given access privileges based on the associated privilege set. System requirementsįileMaker solutions require users to authenticate with an account name and password combination. Security settings configured within FileMaker Server and FileMaker Cloud are deployment specific and apply to all solutions hosted by the server. Security settings defined within a solution using FileMaker Pro Advanced apply only to the information and schema (layouts, tables, fields, relationships, and scripts) stored in that solution. The FileMaker platform employs a unified security model, where the security that you establish for a solution is in effect across all clients.
Access control with privilege sets: You define permissions that determine levels of access to your solution.Users can also authenticate via Active Directory, Open Directory, or OAuth identity providers. Authentication with accounts: FileMaker encrypts credentials stored within solutions so the credentials are protected.The FileMaker platform's features help you control data access, operations, and development within a FileMaker file.
0 kommentar(er)
