Terminology
Last updated
Last updated
A company, or also a single developer, using the Quasr platform to implement identity and privacy into their applications or service.
The account consuming a service provided by a Quasr customer.
Somebody or something that needs to be identified. This can be a human user, a machine, an IoT device, or anything else we have not yet thought of. Other common terms representing the same would be "identity" or "user". At Quasr, we chose to primarily go with the term "account" to emphasize that those needing to identify themselves do not necessarily need to be human users.
also: end-user, end-customer, consumer The account consuming a service provided by a Quasr customer.
A machine client that is not a human, such as an IoT device, server, machine.
see
A factor is an entity defined by the Quasr customer to allow accounts to identify themselves. Different Factor Types exists within Quasr. Before an account can use a factor to authenticate (identify) itself, it needs to enroll in this factor. We call this a Factor Enrollment. An account can have multiple factor enrollments, even of the same Factor or Factor Type.
Factor Types is just a way to distinguish how a certain Factor works, basically in order to be able to group factors by its authentication mechanism. We mainly use this term to explain the concepts of Quasr, there is no particular relevance from a technical or implementation perspective to it.
Username (ID)
Password
Time-Based One-Time Password (TOTP)
One-Time Password (OTP)
OAuth 2.0 / OpenID Connect Federation
Private Key (SPKI)
Hosted Keys (JWKS)
Personal Token (JWT)
aka "Enrollments" for short, or "Enrolled Factor"
Before an account can use a factor to authenticate (identify) itself, it needs to enroll in this factor. We call this a Factor Enrollment. For example: before an account can use a password to authenticate, it obviously needs to have set this password before at some point. This is the Factor Enrollment.
A Quasr Customer can assign security-related scores to their chosen factors and set thresholds on access using these scores. As such customers can indicate how confident they are with factors and make sure users are appropriately authenticated while providing most flexibility for end users by not carving the login / registration process in stone.
A single-page application (SPA) is a web application or website that interacts with the user by dynamically rewriting the current web page with new data from the web server, instead of the default method of a web browser loading entire new pages. Common technologies used for SPAs are React, Vue, Angular, etc. Most application logic is performed client-side in the web browser.
A tenant is a logically isolated instance of Quasr, containing its own configuration, accounts, factors, etc. Each tenant's data is isolated and remains invisible to other tenants.
Quasr supports multi-tenancy. A tenant is always owned by an Account (see above). Multi-tenancy can help solve various use cases, such as:
splitting between development / staging / production environments
separating environments for different B2B SaaS customers in typical B2B2X scenarios
see for details.
See for details.