What Are Security Components?
Fliplet provides components that can be used to secure your apps against unauthorized access. These security components are:
You must also set up App security under App Settings. Otherwise, the components will not be effective in securing your apps.
This article is intended for users who want to become more familiar with the above-listed components, and to suggest when to use each type. The decision as to which component to use ultimately depends on your unique requirements. For more information on each individual component, see the related articles section below.
Pros and Cons of Each Security Component Type
The email and SMS verification components are similar, except that one has users verify their identities using email and the other uses SMS. With these components, users who register for an account with your app can verify their identities using codes sent to either their email addresses or cell phone numbers, which means they don’t have to remember any password. Since these components leave the verification process to your users, this means less work for your app administrators.
On the other hand, emails and text messages can end up in spam folders or be delayed. So, app admins might still need to troubleshoot access problems.
For more information on using the email and SMS verification components, see Email/SMS verification.
Fliplet has three (3) login components you can choose from: Fliplet Login, Login, and SAML2 Login.
With the Fliplet Login component, your users need to have Fliplet accounts to be able to access your apps. Fliplet takes care of verifying user credentials. If two-factor authentication is set up on the account, the user will need to use this step to verify as well. See this article for more on adding users to Fliplet.
With the Login component, user credentials are saved to your own data source. Users access your apps after entering their credentials and verifying them against the data source.
Finally, the SAML2 component enables web-based, cross-domain, single sign-on (SSO) authentication for your app. This is ideal for organizations with their own identity servers. With SAML2, a trusted connection is established between Fliplet and your servers.
While app administrators have closer control over user access using these Login components, it also requires more work from them, as they must add each user beforehand.
For more information on using Fliplet’s three Login components, see Login.
You can use the Lock component to give your users the ability to lock your apps, adding another layer of security to them. If users forget their passcodes for unlocking an app, you may either let them reset it or redownload the app. You can also let users with Touch ID-capable mobile phones to lock and unlock apps.
For more information on using the Lock component, see Lock.
Why Use Security Components?
Fliplet recommends adding security components for apps that require account creation prior to user access. Examples include apps with chat, bookmarking, and commenting features. Certain apps with personal data are also strongly advised to include security, given the implications of this information being accessed by the wrong users.
However, you must set up App security for these components to be effective. App security will be covered in another article.
In other cases, security may not be a requirement, for example, internal use-only apps or apps that are open to the broader public but don’t contain sensitive data.