# New Replit Auth service not recognized by Agent

**URL:** <https://replit.discourse.group/t/new-replit-auth-service-not-recognized-by-agent/4519>\
**Category:** Bugs\
**Created:** [May 12, 2025, 5:56pm UTC](https://replit.discourse.group/t/new-replit-auth-service-not-recognized-by-agent/4519 "2025-05-12T17:56:45Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![onalius](https://yyz2.discourse-cdn.com/flex010/user_avatar/replit.discourse.group/onalius/32/971_2.png) [@onalius](https://replit.discourse.group/u/onalius)\
**Post date:** [May 12, 2025, 5:56pm UTC](https://replit.discourse.group/t/new-replit-auth-service-not-recognized-by-agent/4519/1 "2025-05-12T17:56:45Z")

</div>

Anyone else having issues with the new Replit Auth service. The Agent informs me that it is not aware of the Replit Auth that uses social logins (OAuth) and tries to install Login with Replit account. instead. Has happened every time since they announced. I can give it a picture of the tweet announcing it and it seems to understand then, but can just as easily revert the installation to Login with Replit account. Ship fast isn’t so fun for paying customers. It’s more like we have to pay Replit to be their testers. And the more buggy, the more we pay.

---

<div class="post-metadata">

**Author:** ![realfunnyeric](https://yyz2.discourse-cdn.com/flex010/user_avatar/replit.discourse.group/realfunnyeric/32/2150_2.png) [@realfunnyeric](https://replit.discourse.group/u/realfunnyeric)\
**Post date:** [May 12, 2025, 6:58pm UTC](https://replit.discourse.group/t/new-replit-auth-service-not-recognized-by-agent/4519/2 "2025-05-12T18:58:19Z")

</div>

Use Firebase. Seriously.

---

<div class="post-metadata">

**Author:** ![kody-replit](https://yyz2.discourse-cdn.com/flex010/user_avatar/replit.discourse.group/kody-replit/32/3_2.png) [@kody-replit](https://replit.discourse.group/u/kody-replit)\
**Post date:** [May 12, 2025, 8:12pm UTC](https://replit.discourse.group/t/new-replit-auth-service-not-recognized-by-agent/4519/3 "2025-05-12T20:12:54Z")

</div>

Can you send me the link to the repl where you’re having this issue?

The way login with Replit works is user auths to Replit, Replit auths to App. You don’t set up any of the Oauths or anything, it just inherits the same Oauths that we have already configured for Replit itself.

---

<div class="post-metadata">

**Author:** ![onalius](https://yyz2.discourse-cdn.com/flex010/user_avatar/replit.discourse.group/onalius/32/971_2.png) [@onalius](https://replit.discourse.group/u/onalius)\
**Post date:** [May 16, 2025, 8:10pm UTC](https://replit.discourse.group/t/new-replit-auth-service-not-recognized-by-agent/4519/4 "2025-05-16T20:10:42Z")

</div>

Thanks Kody. Maybe it is working as built then. Does this mean that someone needs to create a Replit account to use Replit Auth? The very first integration I tried didn’t require that (I think) but subsequent integrations have tried. It may also just be a cookie problem and I need to use ingognito.

---

<div class="post-metadata">

**Author:** ![kody-replit](https://yyz2.discourse-cdn.com/flex010/user_avatar/replit.discourse.group/kody-replit/32/3_2.png) [@kody-replit](https://replit.discourse.group/u/kody-replit)\
**Post date:** [May 16, 2025, 8:45pm UTC](https://replit.discourse.group/t/new-replit-auth-service-not-recognized-by-agent/4519/5 "2025-05-16T20:45:50Z")

</div>

Yes, they auth to Replit through their Replit account, then Replit auths to the account.

---

<div class="post-metadata">

**Author:** ![onalius](https://yyz2.discourse-cdn.com/flex010/user_avatar/replit.discourse.group/onalius/32/971_2.png) [@onalius](https://replit.discourse.group/u/onalius)\
**Post date:** [May 17, 2025, 1:00am UTC](https://replit.discourse.group/t/new-replit-auth-service-not-recognized-by-agent/4519/6 "2025-05-17T01:00:36Z")

</div>

![image](https://canada1.discourse-cdn.com/flex010/uploads/replit/original/2X/c/c218f615776bef911fd3927815f2f7e5389e1aa9.png)  
 ![image](https://canada1.discourse-cdn.com/flex010/uploads/replit/original/2X/1/1eec655f2426c2bcbdbe572a4df6945e8f592fa1.png)  
None of this is working. And now the Agent is building a bypass mechanism instead of fixing the Replit Auth integration.
