March 2025 Summaries

FusionAuth is a flexible authentication platform that can be hosted, downloaded, or deployed in the cloud. To set up FusionAuth on Google Kubernetes Engine (GKE), you need to have access to Google Cloud Platform, gcloud CLI, kubectl, and Helm. You will also need to create a project, enable billing, and configure the network for private communication. Once your project is set up, you can create a GKE cluster, update the Kubernetes configuration, verify the cluster configuration, create a database, configure the default user, take a break, add the Helm chart repository, configure the values file, search configuration, pod labels, deploy FusionAuth to the cluster, and access FusionAuth.

You can configure a custom domain with a FusionAuth Hosting package or using AWS CloudFront, offering flexibility and control over authentication management. To set up an AWS CloudFront distribution for a custom domain, you need to obtain an SSL certificate from AWS Certificate Manager, create a CNAME DNS entry with your domain provider, and then set up the CloudFront distribution. Once complete, you can configure the DNS to point to the distribution when a user enters the custom domain, allowing secure access to your FusionAuth instance. With this setup, you can use the custom domain as you would the original URL, working seamlessly with applications and APIs.

With software as a service (SaaS), businesses often build applications for multiple customers, each with their own users, to create a business-to-business-to-consumer (B2B2C) or business-to-business-to-employee (B2B2E) model. In B2B2U models, the SaaS business creates an application sold to intermediate businesses that then provide access to end users. These applications introduce complexity around customer and user modeling, requiring balance between meeting customer requirements and delivering value to ultimate users. Examples of B2B2U platforms include private-labeled job boards, diagramming software for employees, and LLM chatbots for enterprises. The relevant entities in these systems are the SaaS business, intermediate businesses, and end users. B2B2C platforms focus on consumers paying or potentially paying the intermediate business, while B2B2E models target employees or contractors of intermediate businesses. Both types require balancing technical flexibility, security, scalability, customization capabilities, and user-centric design. However, B2B2C platforms prioritize acquisition, conversion, and retention features, whereas B2B2E systems focus on enterprise control and access management. SaaS providers must develop flexible applications that accommodate varied business requirements, complex authentication protocols, and bespoke security needs while balancing security, performance, and user experience across multiple organizational boundaries.

FusionAuth has released version 1.56.0, focusing on API security and introducing new flexibility in SSO sessions. The release includes secured storage for API keys, which are now optionally secured before being stored to reduce risks in case of a database compromise. Custom domains are also enabled for all hosting plans, allowing users to keep their domain name front and center during the authentication process. Additionally, this version enhances seamless SSO across applications, ensuring users stay logged in across multiple services without interruption. Other improvements include tackling several bugs, enhancing admin application security, improving overall system performance, and adding minor features.

The text discusses the advantages of using FusionAuth, a single-tenant authentication platform designed for developers and engineering teams, which provides flexibility, control, and cost-effectiveness by allowing users to deploy it locally or in the cloud. FusionAuth emphasizes the benefits of owning one's authentication infrastructure, such as improved security, customization, and compliance with data residency requirements, as opposed to relying on multi-tenant SaaS solutions that often prioritize vendor efficiency over user needs. The platform supports easy testing and development without the constraints of SaaS providers' uptime or rate limits, reducing the risk of bugs caused by environment inconsistencies. The narrative highlights the misconceptions around the cost-effectiveness of multi-tenant architectures and argues for the competitive pricing and privacy benefits of single-tenant solutions, using FusionAuth as a model for how authentication should complement, rather than dictate, application architecture. The text concludes by encouraging users to take control of their authentication processes with FusionAuth, offering a free start and inviting them to Authcon, an event dedicated to customer identity.

The FusionAuth Swift SDK for iOS Beta streamlines mobile development by offering equally powerful backend capabilities and seamless integration with preferred frameworks. The SDK eliminates boilerplate code, leading to cleaner and more efficient applications. It provides a simple and trustworthy interface to authenticate mobile users with FusionAuth, allowing developers to use OAuth 2.0 and OpenID Connect functionality in their iOS apps. The SDK is written in Swift and compatible with Object-C, and it uses AppAuth-iOS for the OAuth 2.0 Authorization Code Grant flow and OpenID Connect functionality. It simplifies authentication flows, introduces standardized usage, handles best practice defaults, saves time, maintains flexibility, and provides a secure way to authenticate users. The SDK is designed to be easy to use, with a single import and simple configuration that handles all dependencies and best practice defaults. Developers can use the SDK to retrieve user info, call APIs with access tokens, and sign out users, while FusionAuth takes care of security features such as account locking, password rules, webhook notifications, and more. The SDK also allows for customization of the look and feel of hosted login pages, including themes and Tailwind CSS examples.