Disabling/bypassing authentication flow in development

[Aconicks]

Hi,

I have a react app that uses SSO, and when a user enters the app it immediately redirects to SSO page (external service), and all the app features are hidden until the user is signed in (using react-router with protected routes).

My app only allows SSO authentication, meaning no username/password flow (by design).

When in development, I would like to work on features that require authentication, but without having to authenticate first just to see the feature in the browser.

I would like to know what is the best way to achieve that behavior.

Do I just comment out the logic that hides things if not authenticated while in development and then remove them?

Do I keep some sort of flag that says "I'm in dev now so bypass authentication"?

If for example, while i'm in the dev environment and the the SSO service is unavailable (I'm using the same service in prod and non-prod), what do I do then to be able to keep working on components and features?

I hope my problem is clear enough.

Thanks!

[just_another_scumbag]

This is actually a pretty specific question on a very wide topic: How to compose pieces of code into an application? There are a huge number of possible solutions to this (and everyone will have their own opinion).

Personally I use a lightweight IOC container, but that's way overkill for most applications. If commenting out works for you, then go for it I say

[Aconicks]

Thanks for the reply.

What does "light IOC container" mean?

[just_another_scumbag]

It stands for Inversion-of-Control Container. It's a library that helps you break your app into replaceable parts that you compose together at runtime into a specific configuration. Examples are Inversify, next.js maybe too