We’re making authentication easier to set up and manage with our new Log in with Replit feature for the agent.
It is now available in beta for users in the Explorer group. The document below provides more details about how to get started. We greatly appreciate all feedback.
If a user does not have an existing Replit account, they must create one while trying to use your app. They can do this directly in the same process of logging into your app.
This is usually pretty quick - especially if they sign up with Google or one of the social providers!
OK, that’s cool. Is it possible to reverse engineer it into my app that’s currently just asking for name, email, user and password and adding them to the database? What happens when I want to send users an email? Can I, using this authentication method? Presumably not?
I felt it would be nice to be able to replace the following components for example.
To be more specific, I feel that I should be able to choose the authentication provider.
I often feel that I want to narrow it down to just google, because if there are too many choices, they can get confused and forget which social networking authentication.
So I thought it would be a solution if, for example, authentication methods other than google could be hidden by design.
But this is just my opinion. Many people may feel that more options would be better.I will try a few more things.
I’ve been testing the beta Replit Auth and it does appear the user accounts I setup are receiving the marketing emails from Replit. Let me know if you’d like some samples.
Tested setting this up on a new app tonight and run into many issues. I let Agent try many checkpoints to fix but it wasn’t able to. This is on a new app that was created today. I just had added a database right before trying to add auth with Log In with Replit. I’ve reverted for now.