www.dwaynewright.com
info@dwaynewright.com
TWITTER: dwaynewright
For the most part, a developer or administrator will want to make security changes to a FileMaker solution manually. However, you can script some of the most basic security settings for ease of use or automation. There are limits to what you can do in regards to ScriptMaker and security settings and that is probably designed that way. If too much security actions could be scripted, that may be considered a security hole. One of the big challenges in FileMaker security scripting tasks is that you cannot script anything to do with the privilege set. So if you want to convert an account from one privilege set to another via a script, you have to delete the original account, create a new account and hard code in the privilege set you want to use.
Here is a list of the current script steps in the Account scripting family ...
Add Account
Delete Account
Reset Account Password
Change Password
Enable Account
Re-Login
=
More info about the author and FileMaker in general, contact me at info@dwaynewright.com.
© 2008 - Dwayne Wright - dwaynewright.com
The material on this document is offered AS IS. There is NO REPRESENTATION OR WARRANTY, expressed or implied, nor does any other contributor to this document. WARRANTIES OF MERCHANT ABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE EXPRESSLY DISCLAIMED. Consequential and incidental damages are expressly excluded. FileMaker Pro is the registered trademark of FileMaker Inc.
====================== ADVERTISEMENT ==============================
For more information on the InBizness SOHO and other quality FileMaker framework solutions, please visit http://www.dwaynewright.com/solutions.html
Posts
