Welcome to BlokSec, and congratulations on starting the journey towards a secure, passwordless Internet! These documents will help you get started with BlokSec and help you get the most out of our service.
BlokSec can be added to your environment in one of two ways:
- As a full-featured Identity-as-a-Service (IDaaS) provider - you can use BlokSec in this way if you don't already have a centralized place to manage your user identities already, or if you are standing up an environment to serve a net new population of users (for example, launching a consumer-focused application)
- As a bolt-on Authentication-as-a-Service (AaaS) to augment your existing identity ecosystem - this is a great fit if you already have your identities in a centralized place such as Microsoft Azure, an LDAP directory, or even in an older IDaaS provider such as Okta or Ping, but want to take advantage of BlokSec's next generation secure, immutable, decentralized authentication capabilities
Whichever model best suits your needs, you will have access to BlokSec's powerful user management, authentication, and authorization APIs. You can choose to use BlokSec with our free BlokSec yuID Authenticator App, you can integrate our authentication and/or authorization services in your own app by leveraging our SDKs for iOS and Android, or for a nominal fee we can customize an authenticator app for your organization. (For this last option, please email email@example.com for more details.)
You can navigate through our documentation using the left navigation menu to access articles relevant to your application. We suggest reviewing the Use Cases to decide if you can leverage our Secure, Passwordless Login via Standard Protocols (OIDC, SAML2), or if easing your users into the new way of logging in by leveraging BlokSec for MFA / 2FA is a better fit for your organization. You can navigate to our Integrations section to access articles for integrating with specic applications.
Please note - these documents are in their infancy and are actively being expanded. If you find something confusing or can't find what you're looking for, please email Mike Gillan at firstname.lastname@example.org - we would really appreciate your help to make these documents better!