How do you propose your average enterprise should manage auth for these legacy systems without using SCIM?
1,819 karma · joined July 20, 2017
How do you propose your average enterprise should manage auth for these legacy systems without using SCIM?
The answer is for the third-party apps to add modern auth, but this is dependent on the vendor, not Okta. The only alternative is to have unmanaged logins, which is arguably worse than SCIM.
SCIM is there as a last resort, its use is heavily discouraged.
That leaves you with 4 days a week to work on your own projects.
An economy is not a society. There is more to the human experience than "number goes up".
Until AI has a sense of good taste and can carefully blend multiple styles into a new genre, the human cannot be replaced. And at that point we're basically at the singularity.
Recruiters can be great to avoid the networking dance. Make sure to look at salary surveys so you have a ballpark for pay, ask the recruiter what % cut they are taking, and always engage with at least three separate recruiters for calibration. If a recruiter pressures you into being exclusive, laugh and hang up.
https://mediachomp.com/theyre-made-out-of-meat-sci-fi-short-...
There's also a lot more people trying to meme who are really awkward at it - see every Minions meme ever.
The problem is when the lead dev has been huffing the architecture paint too hard and starts prematurely spinning up microservices because it feels good.
It should be obvious, but apparently it's not. So many architecture astronauts drinking the kool-aid and making a mess. Premature microservices can easily kill a product.
It's a recurring theme in Korean media eg Parasite and Snowpiercer.
The food elimination diet is very scientific - you add items back in one at a time to test if they cause a negative reaction to your particular physiology.