Home / Companies / PropelAuth / Blog / February 2023

February 2023 Summaries

6 posts from PropelAuth

Filter
Month: Year:
Post Summaries Back to Blog
Passwordless authentication allows users to access websites and applications without traditional passwords by verifying identity through methods such as biometric scans, physical security tokens, one-time codes, or email-based “magic links.” These approaches can reduce password-related problems including forgotten credentials, account-reset friction, password reuse across services, and restrictive password policies that may weaken security or discourage users. Passwordless systems can also provide faster, more convenient login experiences, often using mobile devices or email access. However, they still carry risks, including spoofed or stolen biometric data, intercepted codes sent through insecure channels, and delivery issues when login emails are filtered into spam or promotional folders.
Feb 24, 2023 514 words in the original blog post.
Two-factor authentication (2FA) strengthens account security by requiring two distinct identity-verification factors, typically combining something a user knows, such as a password, with something they have or are, such as a phone-generated code, hardware token, fingerprint, or facial scan. A common login process begins with a username and password, followed by a second verification step before access is granted. This additional layer can limit damage from stolen passwords and phishing attempts because credentials alone are insufficient to enter an account. Common methods include SMS codes, authenticator apps using time-based one-time passwords, biometric verification, and physical security keys or smart cards. When single sign-on (SSO) is used, an identity provider such as Google may enforce 2FA centrally, allowing connected products to benefit from stronger authentication without independently implementing the feature.
Feb 24, 2023 554 words in the original blog post.
Single sign-on (SSO) is an authentication method that lets users access multiple applications with one account rather than maintaining separate usernames and passwords for each service. Common examples include choosing “Continue with Google” or Facebook when signing into another product; in a typical flow, the identity provider requests the user’s consent, returns a token to the application, and the application uses that token to retrieve approved information such as a name or email address. Subsequent logins can often proceed without renewed consent, making access faster and more convenient. SSO can also improve security by reducing password burden and making it easier for users to adopt additional protections, although enterprise implementations commonly use an organization’s internal identity provider instead of external OAuth providers such as Google or Facebook.
Feb 21, 2023 554 words in the original blog post.
Although Rust has provided a safe, expressive, and reliable foundation for the company’s backend, its author argues that it would not be the preferred choice for an early-stage startup starting over. Rust’s strong type system, memory safety, compile-time tooling, concise error handling, and features such as algebraic types and pattern matching reduce common runtime mistakes and support maintainable production code. However, the learning curve and time spent satisfying the compiler can slow MVP development and customer-driven iteration, while hiring or training developers unfamiliar with Rust adds further friction. Performance advantages may also be less urgent for startups that can use cloud-provider credits to scale infrastructure temporarily. Rust is presented as most valuable once a product direction is established, performance becomes important, or technical debt must be controlled; despite this retrospective view, the company is not rewriting its existing system because its Rust codebase, internal tooling, and accumulated expertise now enable fast and safe development.
Feb 17, 2023 791 words in the original blog post.
The guide demonstrates how to build a B2B React application with PropelAuth for authentication and a Rust/Axum backend for protected APIs, covering signup, login, logout, user account details, authenticated requests, and organization membership. It begins by configuring PropelAuth hosted authentication pages and optional capabilities such as social login, user metadata, profile pictures, and B2B organization support, then integrates the React SDK through an application-wide AuthProvider and React Router. React components use PropelAuth hooks and wrappers to conditionally render content, redirect users to hosted login, signup, and organization-creation pages, display user data, and attach access tokens as Bearer credentials when calling backend endpoints. On the backend, the Rust application initializes the PropelAuth SDK using environment-based credentials, applies an Axum authentication layer to validate tokens, returns user information through a protected whoami route, and verifies organization membership before returning organization-specific data. The walkthrough also addresses local CORS concerns through a React proxy configuration and concludes that managed authentication reduces the need to build login interfaces, email flows, invitations, and token-validation logic from scratch.
Feb 09, 2023 3,294 words in the original blog post.
OpenAI’s Next.js quickstart template provides a simple foundation for AI applications using Serverless API Routes and can be deployed easily to platforms such as Vercel or Cloudflare, but it lacks production essentials including authentication and usage controls. The walkthrough shows how to adapt the template’s frontend form and OpenAI completion API route for other prompt-driven products, then integrate PropelAuth to provide hosted signup, login, profiles, and optional social sign-on. Authentication is enforced on the frontend through protected providers and on the backend by passing an access token in request headers and validating it with PropelAuth’s Node SDK before allowing API access. The approach can support either consumer accounts or B2B organizations, with organization features such as invitations, roles, permissions, and enterprise SSO. To control costs and enable billing, the application records requests by user or organization ID in a selected data store, such as Postgres or Cloudflare Durable Objects, and can periodically aggregate request counts for reporting to a billing system like Stripe.
Feb 01, 2023 1,872 words in the original blog post.