Help with Extracting Additional Query Parameters during Social Login Redirect in Django-AllAuth

[iamunadike]

Hello @cdcarter @tomdee @quique @krizh-p @jezdez @pennersr @pacesm @jplehmann @PabloCastellano @tomdee @oalamoudi @quique @fabiocerqueira @facugaich @fdobrovolny @fengsi,

I'm currently facing an issue with Django AllAuth and would greatly appreciate your insights.

Here’s my setup:

from allauth.account.adapter import DefaultAccountAdapter
from allauth.socialaccount.adapter import DefaultSocialAccountAdapter
from django.conf import settings
from authx.views import role_based_redirect

class SocialAccountAdapter(DefaultSocialAccountAdapter):
    def post_login(self, *args, **kwargs):
        resp = super().post_login(*args, **kwargs)
        next_url = kwargs.get('redirect_url', '')
        import pdb; pdb.set_trace()
        sociallogin = kwargs.get('signal_kwargs', {}).get('sociallogin')
        if sociallogin:
            return role_based_redirect(sociallogin.user, next_url)
        return resp

    def get_login_redirect_url(self, request):
        import pdb; pdb.set_trace()
        next_url = request.GET.get('next', "")
        return '/me/posts/'
        # return role_based_redirect(request.user, next_url)

class GAccountAdapter(DefaultAccountAdapter):
    def post_login(self, *args, **kwargs):
        resp = super().post_login(*args, **kwargs)
        next_url = kwargs.get('redirect_url', '')
        import pdb; pdb.set_trace()
        sociallogin = kwargs.get('signal_kwargs', {}).get('sociallogin')
        if sociallogin:
            return role_based_redirect(sociallogin.user, next_url)
        return resp

    def get_login_redirect_url(self, request):
        import pdb; pdb.set_trace()
        next_url = request.GET.get('next', "")
        return '/me/posts/'

I'm trying to manage redirect URLs in django-allauth using the query parameters. Specifically, I'm looking to capture a parameter like type=customer in a URL structured as http://localhost:8000/auth/signin/?next=//shop.apps.local:8000/store/checkout&type=customer.

I’m currently setting is_safe_url to True for handling domains, but I'm unsure how to access the type parameter within django-allauth during the redirect process. Could you advise on the best way to capture and utilize type=customer within the custom adapter?

Any help on this would be invaluable—thank you in advance!

[iamunadike]

@andrenbrandao @marjoripomarole @radek-senfeld @quique @jacksund @dakrer @quique @RoPP @aaronvanderlip @kappataumu @tomdee @vmavromatis @xfxf @Jeffxz @tomdee @quique @pennersr @apekatten
Please can any one help to the answers above

[pennersr]

@iamunadike I already told you (#3881 (reply in thread)) , what you are doing is not helping you at all. Yet, here you are again, paging over 30 people.

And over here, #4141 (reply in thread), you are barging into an unrelated discussion forcing attention on your topic. Also this:

Remeber this project is created by you and i could not find a fix from the docs

Did you ever read the license?

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND

And with respect to this:

Please help on this as I am trying to ship fast

We all are.

If I knew the answer to your issue I wouldn't be withholding it, but I simply have no idea what it is that you are doing. That http://localhost:8000/auth/signin/ is not an allauth URL. Try to grasp your scenario takes time, which is valuable to me.

Know that the way you are approaching things puts people off.

[iamunadike]

@pennersr

Thank you so much for your reply—it means a lot. I also want to apologize for tagging multiple people earlier. Since your last response already addressed part of my issue, I thought it would be okay to follow up with this related question.

I’m trying to track multiple &parameters appended to URLs. For example, if the URL is localhost:8000/auth/signin or even the default one based on django-allauth, how can I effectively track parameters such as:

localhost:8000/auth/signin/?next=next_url&type=firstvalue&c=secondvalue

To provide some context, the next redirect URL has been resolved using the is_safe_url modification in my custom adapter. My question now is: which method or approach should I use to track or capture these additional URL parameters (type, c, etc.)?

Any guidance would be greatly appreciated.

Thanks in advance!

Let me know if you'd like any further adjustments or additional details added!

[pennersr]

which method or approach should I use to track or capture these additional URL parameters (type, c, etc.)?

It is not clear to me to which allauth/view/url these parameters are being passed. As mentioned, /auth/signin/ has nothing to do with allauth. Then you mention:

even the default one based on django-allauth

Which "one" are you referring to?

[iamunadike]

okay , sorry I skipped that , so I am presuming a use case of /accounts/login/ with parameters now my observation with respect to

I am working with a use case where I have the URL /accounts/login/ with parameters such as next, type, c, and etc. I'm implementing Google social authentication with Django-Allauth, and during the redirect from Google, I want to track these parameters.

For example, the URL might look like this: localhost:8000/accounts/login?next=next_url&type=firstvalue&c=secondvalue&etc=.... After Google authentication and the redirect, I want to intercept and capture these parameters.

Which method can I override in a custom adapter to achieve this, and how should I go about it?

Thanks!

[pennersr]

So, you are at /accounts/login/?next=A&type=B, and from there you are performing e.g. the Google handshake? Only the next parameter is preserved, assuming you hand it over properly. So, if you construct a URL like this in your page:

{% provider_login_url "google" next="/success/url/?type=B" %}

... that should get you going.