Hey everyone, new-ish member here 👋. I've been using Okta at my company for about a year now, mostly for internal app SSO. I was really excited when the Auth0 merger happened, thinking it would mean more features and maybe even a simpler dev experience.
But lately, as we've started looking at building a customer-facing login for a new product, I'm feeling a bit overwhelmed. The console seems to have *two* ways of doing everything now. For example, when I went to set up a new OIDC integration, I found the "Okta Integration Network" section, but then there's also the "Auth0 Dashboard" feel for applications. My team lead can't decide whether to use "Okta Classic Engine" or "Okta Identity Engine."
I'm trying to keep up, but as someone still building their skills, the mental overhead is real. Has anyone else navigated this recently? I'm specifically trying to understand:
* For a simple web app with a React frontend, should we be using Auth0's quickstart docs or Okta's?
* Is the complexity mostly on the admin/configuration side, or does it also change the actual implementation code?
For instance, a basic code snippet from the docs now has me checking which SDK to use:
```javascript
// Okta's SDK
const oktaSignIn = new OktaSignIn({
baseUrl: 'https://dev-123456.okta.com',
clientId: '0oa1bc...',
redirectUri: 'https://localhost:3000/callback'
});
// Versus Auth0's SDK
const auth0 = new auth0.WebAuth({
domain: 'dev-abc123.us.auth0.com',
clientID: 'xyz987...',
redirectUri: 'https://localhost:3000/callback'
});
```
Are we essentially maintaining two parallel skill sets now, or is there a clear path forming for which use cases go where? Any guidance or shared experiences would be super helpful.