In my last post, “Introduction to Web Apps with Next.js”, we went through the steps of setting up a new Next.js project, customizing a landing page, and implementing a very simple web application. In this post, we’ll implement an Open Authentication (OAuth) based Single Sign-On (SSO) API within Next.js using NextAuth.js. We’ll be using GitHub as our provider, but the steps here are very similar for other platforms, such as Google or Discord. This will allow us to place portions of our website behind a login screen, restricting access to certain content or APIs for anonymous visitors.
SBOMs: A Recipe for Software Success
While working with a client a few years ago, I was introduced to the concept of a Software Bill of Materials, colloquially known as an SBOM. It didn’t take long before I recognized its immense value and importance in improving security and integrity in software development. Hopefully, over the next few minutes as you read this blog, you’ll start to see that as well.
The topic of SBOMs has become more and more popular over the past several years and is increasingly critical in this technology-driven world. We’ve all heard of numerous enterprise-level data attacks, exposures, and leaks in recent years, and almost all are caused by some sort of security vulnerability. Many of these incidents could have been realized and possibly even mitigated before disaster struck if an SBOM had been in play.
What are Ways to Secure Your Microservices Architecture?
In today’s rapidly advancing digital landscape, securing microservices architecture is paramount to the success and resilience of modern organizations. At Keyhole Software, we understand the critical imperatives of protecting against unauthorized access and safeguarding sensitive data. This guide explores key strategies to fortify your microservices architecture’s security, highlighting the comprehensive services we offer to help you navigate and implement these …
Navigating the Maze of Authentication Options: A Solo Developer’s Guide
In web development, choosing the right authentication strategy is a pivotal decision, especially for solo developers or small teams working with limited resources. After extensive research, I’ve adopted a hybrid approach that combines the security and ease of 3rd party services like Google and Microsoft with the control of an in-house solution.
This hybrid approach addresses my core concerns: cost, control, and user convenience while keeping the in-house method at the forefront. As we explore this topic, I’ll share the considerations and insights that shaped my strategy, aiming to guide you toward the authentication system that best fits your project’s unique demands.
What are the Common Software Security Issues & How Do I Prevent Them?
In the world of software development, addressing the common software security issues and how you can prevent them is crucial. At Keyhole, we understand the importance of prioritizing security right from the project’s inception. This approach is not just a recommendation but a necessity in today’s digital landscape. Integrating security measures from the start significantly reduces the risk of encountering …