If you ask me what my most trusted alarm system is, I'd answer that my loyal guard dog, Clifton, does a great job at barking at anything he hears and sees before it gets within a thousand feet of our home or office. But unfortunately, he doesn't have much bite when it comes to protecting apps.
That's one of the many reasons we designed the security framework that's woven into Alpha Five Version 11.
The security framework provides a comprehensive set of services that can be used by Alpha Five developers to protect their apps. It originally debuted in Alpha Five Version 8, and has been continuously updated to stay abreast with current and emerging security threats.
Rather than delve into its many capabilities, I'd like to talk today about how it works with the dialogue component.
Here's the first in a series of security framework demo videos. This video shows how you secure an app with a username and password. This is something very few apps can do without. Watch how it's done here.
Once you've captured a username and password, you need to store them as well as a broader user profile. This is all held in a database table, and is created at the same time the new user account itself is generated. The account credentials are stored in the web security framework's tables. Any additional information you choose to collect is stored in a related table of your design. Here's a video that shows how this is done.
After you've created the user's account, it's easy to modify. You can retrieve the account information, and then allow the user to edit that data. Take a look at the video to see some of these usage scenarios.
There's more to come on this, but these are the first steps to securing an app that you've built in Version 11. Don't tell Clifton, but I'd trust this just as much as I'd trust any menacing bark or growl.