What to Do When Your ERP System Can’t Handle OAuth and Basic Auth Is Being Phased Out?

0
11
Asked By QuirkyNinja7 On

I have a legacy ERP system built in 2008 that only supports basic authentication. Unfortunately, the vendor hasn't been around since 2019, and now Microsoft is discontinuing basic auth next month. We rely on this system for workflows that pull orders from Exchange using SMTP with plaintext credentials. A consultant said migrating to OAuth would require extensive rewrites throughout the code, with an estimated cost of $400,000 and a nine-month timeline. My CFO isn't on board with that and wants a cheaper solution. I'm at a loss; it feels like we're stuck between needing to fix a legacy system no one wants to invest in and the reality that we can't function without it. Has anyone faced a similar situation?

4 Answers

Answered By OldTimeyHacker On

You should check out Microsoft's recent updates. They've actually pushed the deadline back a year, so you might have more time than you think. Look at options like SMTP relays or even developing an in-house solution that bridges the gap while you search for a more permanent fix.

LazyDeveloper87 -

Nice! That could buy you some crucial time to plan properly.

GadgetGuru -

For sure! It’s always good to stay updated with the latest announcements.

Answered By TechSavvySteve On

It's a tough spot, for sure! Sounds like you might want to consider a middleware solution that can manage the authentication transition without needing a total system rewrite. There are smaller software solutions that can handle basic auth and translate that to OAuth for you. I'm sure there's something out there ready to go that could save you a ton of hassle and cost!

LegacyRescuer -

Great advice! Middleware could be a game-changer without the massive overhaul.

OldSchoolCoder -

Yeah, I've seen similar setups work quite well. It's worth exploring!

Answered By SystemSavior22 On

Honestly, replacing that ERP might be your best bet. I totally understand the pushback from the CFO, but if you wait too long, you could face serious operational risks. Maybe it's time to escalate this issue to higher-ups and lay out all the potential impacts. Sometimes a political approach can yield better results than just looking at the tech side.

FutureBuilder01 -

Absolutely, the longer you stay on an outdated system, the more at risk your operations become!

CautiousITGuy -

It's all about balancing costs, but you're right. Sometimes you need to make a strong case!

Answered By OverworkedAdmin On

I feel for you—this is a common issue with legacy systems. They're often neglected until the ticking clock runs out. Definitely document everything—risks, costs, and the dire need for action. Sometimes management needs a clear picture to make a decision.

RiskReducer -

Exactly! Highlighting those risks can often push management to reconsider.

DepressedDev -

So true—it’s like waiting for the crisis to happen before anyone cares!

Related Questions

LEAVE A REPLY

Please enter your comment!
Please enter your name here

This site uses Akismet to reduce spam. Learn how your comment data is processed.