Access tokens define what a user can access on your server.
When a user signs up or logs into your application, they receive an access token in their browser as a cookie. Your frontend should send this access token to your server, and your server should verify and decode the access token to determine which user is making the request along with what they are allowed to do.
For more information about how to use access tokens, see Concepts › JWT Access Tokens › Using JWTs.
Where users should be redirected upon logging in.
Defaults to /dashboard.
Can be edited on the Redirect paths page in the Userfront dashboard.
Where users should be redirected upon logging out.
Defaults to /login.
Can be edited on the Redirect paths page in the Userfront dashboard.
Where users should be redirected upon signing up.
Defaults to your After-login path mentioned above.
Can be edited on the Redirect paths page in the Userfront dashboard.
The users that will be using your application. These users will not interact with the userfront dashboard.
ID tokens have information about the user for frontend display purposes.
When a user signs up or logs into your application, they receive an ID token in their browser as a cookie. Your frontend can read this cookie for information such as the user's email address, image, name, and more.
For more information about how to use ID tokens, see Concepts › JWT Access Tokens › Using JWTs.
A type of signed, secure token that contains information in the form of an encoded JSON object.
Acronym for JSON Web Token. JWT is pronounced "jot".
For your applications production environment. See more here
MFA, or multifactor authentication is optional by default, but can be set to required for each end user.
Where users should be redirected to reset their password after clicking the link in the reset email.
Defaults to /reset.
Can be edited on the Redirect paths page in the Userfront dashboard.
Refresh tokens are used to obtain new access and ID tokens.
Roles are given to end users and define what level of access that user has within your application. Roles are used to apply access control for users within your application and can be used application-wide or to specific Tenants within your application.
RSA is an algorithm used for signing tokens. The algorithm uses a public key, which can be shared with anyone so that they can verify the token is authentic, and a private key, which is known only to the token creator, and is used to create tokens.
Userfront uses RSA to sign your users' access tokens and ID tokens.
You can find your public RSA key(s) in the Settings section of the Userfront dashboard. Userfront maintains your private RSA keys in a secure manner.
A team member is a user that has access to the workspace in userfront, this is different from an End User in that they are not users of your application, rather users that will have access to your workspace in the userfront application.
For your applications development or testing environments. This allows users to have a way to test their login experience without creating test users in their production environment, as well as be able to test new features to their login/toolkit such as a new auth factor before releasing to their end users. See more here
Tenants allow you to sub-divide your application so that certain users only have access to certain parts.
For example, your workspace could have Tenant A and Tenant B. You could give some users access to Tenant A, some users access to Tenant B, some users access to both Tenants, and some users access to neither Tenant.
The ID for a tenant created within your workspace. Your tenants can be found on the Tenants page in the Userfront dashboard.
a1b2c3d4.UI Toolkit is a ready to use form that can be customized for login, sign up and password reset. Configure, style and install your toolkit here
Also referred to as project/company name during setup. Each workspace has its own UI Toolkit, end users, roles and team members.
The ID for your workspace. The workspace ID can be found when you are logged into the Userfront dashboard:
https://userfront.com/dashboard
Workspace IDs are a type of tenant ID, which are 8-character alphanumeric IDs, like a1b2c3d4.