Devdojo Auth

Hi there,

You should be able to remove the GOOGLE_CLIENT_ID and GOOGLE_CLIENT_SECRET secrets from your .env file and your site will not be able to connect to the Google auth anymore.

Also the Auth package uses the Socialite package, for anything more specific you can also refer to the docs here:

https://socialiteproviders.com/

Hi, thanks for the reply, I mean to allow a way for the user to disconnect their connection from social provider?

and if they do, is there a way for them to set the username and password before disconnection? Thanks

I don't think that this is possible with Socialite, there has been a similar discussion about this a few years ago here.

The suggestion there is to use the vendor API directly.

I'm sorry to highjack this thread but I was unable to create my own due to inability to verify my phone number during registration. I never receive the text. Not sure what's going wrong? I tried several different phone numbers and none receive the text.

Aside from that, I have a few questions of my own. I have installed Wave and went through the installation and configuration options. When I have "Registration Require Email Verification" turned on, I get unexpected results. I sign up, I get sent the verification email, but if ignore the email and click logout at the bottom, then try to login again, I am able to access my account. I expected that upon attempting to login I would be redirected and gated at the /auth/verify screen. As far as I can tell, enabling this setting has no noticeable effect.

Also, if I have this setting enabled and I have subscribed middleware enabled instead of auth on my dashboard and other settings pages, when I first click the verify email link in the email, I get redirected to /admin and a Forbidden message. If I close the window and click the verify link a second time, then it redirects to the account.

Next, when I sign up as a new user, the public profile page is a 404. It works when I log in as the admin.

Finally, in my app, there is no "free" tier and every sign-up requires a subscription. Is there a way to make a user choose a subscription upon registration?

Hi there,

I've manually gone ahead and verified your account.

We will look into the verification issue with the auth package! Thanks for reporting that.

The 404 on the public profile is something that I've not been able to reproduce on my end. Do you have any special characters in the username or have you made any changes that could affect this?

Also, if I have this setting enabled and I have subscribed middleware enabled instead of auth on my dashboard and other settings pages, when I first click the verify email link in the email, I get redirected to /admin and a Forbidden message.

Can you clarify where exactly are you making that change?

Can you clarify where exactly are you making that change?

Sure, I will share my /config/devdojo/auth/settings.php:

/*
 * These are some default authentication settings
 */
return [
    'redirect_after_auth' => '/dashboard',
    'registration_enabled' => true,
    'registration_show_password_same_screen' => true,
    'registration_include_name_field' => false,
    'registration_include_password_confirmation_field' => true,
    'registration_require_email_verification' => true,
    'enable_branding' => false,
    'dev_mode' => false,
    'enable_2fa' => true, // Enable or disable 2FA functionality globally
    'enable_email_registration' => true,
    'login_show_social_providers' => true,
    'center_align_social_provider_button_content' => true,
    'center_align_text' => false,
    'social_providers_location' => 'bottom',
    'check_account_exists_before_login' => true,
];

Then, in some of the /resources/themes/anchor/pages/ files (dashboard/index.blade.php, settings/api.blade.php, settings/profile.blade.php, settings/security.blade.php, I changed middleware('auth') to middleware('subscribed'). I left invoices and subscription on 'auth' since those should always be accessible to my user. Perhaps some of my choices may change in the future but this is what I have setup for now.

The 404 on the public profile is something that I've not been able to reproduce on my end. Do you have any special characters in the username or have you made any changes that could affect this?

I don't have the user create a username at all. I thought I saw somewhere in the files that it is generated automatically somehow. The user only enters their email and password (and password confirmation) to sign up. Maybe that's why they don't have a profile, but I don't see a place to create this. I don't ask for their name on sign up. If I click public profile, it directs me to /profile and I get a 404. It doesn't include anything after "profile".

Here is a video demonstration of the email verification failure: https://streamable.com/tgsdx1

Edit: OK, so after playing around a bit I discovered this problem only occurs after a specific circumstance that would often be unlikely encountered outside of testing.

1. I am logged into my admin account to check the users table to delete the newly created user.
2. I log out of my admin account and go to the sign up page to recreate the user I just deleted.
3. Email verification fails because it tries to take me back to my recently logged out admin account.

I assume this is due to some sort of session cookie/cache issue. If I delete the user, log out, clear my browser data, close the browser, and start the sign up process over again, it doesn't occur.

Also, I realized that the 404 profile error occurs when you don't ask the user for name upon registration. If it's an email only registration then no profile is created. If you disable both name and email registration, the sign up form disappears.

Wondering if you are running that app locally? I noticed ".test" in the app domain.

Can your local machine hosting send out emails? Personally I don't have any emails sent out from my dev machine, I use Mailpit to catch all emails going out from my local apps.

https://mailpit.axllent.org/

Needs .env file setup, something like

MAIL_DRIVER=smtp
MAIL_HOST=127.0.0.1
MAIL_PORT=1025
MAIL_USERNAME=null
MAIL_PASSWORD=null
MAIL_ENCRYPTION=null
MAIL_FROM_ADDRESS="[email protected]"
MAIL_FROM_NAME="${APP_NAME}"

Yes I am running locally and I did set up an SMTP server. Emails are going out. I was also able to solve the email verification issue. I did not have 'verified' in my middleware, I just had subscribed. That fixed it!