D10: Re-vet Auth0 (drupal/auth0)

What a great guide written here! →

I followed it through and was successful in getting my Drupal 10 site set up with Auth0:

Video here → 🙂

I don't think it's worthwhile to try to migrate the standard LOGIN settings from Auth0 in D7 to D10. Best practice would also dictate these not even be stored in configuration, but rather set with an override.

We could write a migration for some of the advanced settings though which might be helpful ( I opened this issue to address 📌 Create migration of advanced settings from Drupal 7 to Drupal 10 Active ). Should we wait for that issue to be completed before updating the recommendation? Or do you think that is a "nice to have " - as this module is going to require manual setup anyway.

I updated this recommendation to be...something that might fit...but happy to reevaluate 😀

One small remark, then I'll merge!

But not migrating advanced settings which probably should be reassessed anyway … that does make sense. Can you clarify that in the note, please?

I don't think I described what I was trying to do very well haha 😃 There are 2 aspects of settings for this module:

Login Credentials:

Advanced Settings

The login credentials I don't think would be necessary to migrate.

The advanced settings do contain some data which could prove beneficial to migrate over. For example auth0_role_mapping, contains a mapping of Auth0 role names to Drupal Roles, a la:
s:19:"admin|administrator";

Or the auth0_claim_mapping contains a mapping of Auth0 profile names to Drupal user field names:
s:27:"given_name|field_first_name";

It was these settings which I was thinking might be worthwhile to migrate over so users don't have to copy them manually. But probably a nice to have vs hard blocker.

making me wonder why we'd consider this vetted if it's not

I think i was considering it vetted because I was able to set it up and have a functioning D10 module (after manual setup) - so can confirm it works, but there is no (existing) automated way to get it 100% in place

I think i was considering it vetted because I was able to set it up and have a functioning D10 module (after manual setup) - so can confirm it works, but there is no (existing) automated way to get it 100% in place.

Yep, that's totally fine — there's a lot of gray between all the black and white :)

All I was asking for is a clearer note 😊 Don't say "it's lacking X", say "X requires manual setup, because it needs manual re-evaluation" 👍

All I was asking for is a clearer note 😊 Don't say "it's lacking X", say "X requires manual setup, because it needs manual re-evaluation" 👍

😁 got it -- updated the note in the issue fork MR.

Automatically closed - issue fixed for 2 weeks with no activity.