Open-event-server: Register doesn't recognises 'string@string' as valid Email

[kushthedude]

Describe the bug

Register user produces an unexpected error upon registering with email of type 'string@string'.

To Reproduce:
Steps to reproduce the behaviour:
1.)Go to'/Register'.
2.)Register with email of type 'string@string'
3.)See the error

Expected behavior
It should recognise it has an email as 'string@string' is a valid email format.

Additional details (please complete the following information):

• OS: MacOS
• Python Version: 3.7

ScreenShot:

[kushthedude]

@uds5501 i was trying to find where the rules of email are specified but i was not able to find as everywhere its just using email as an attribute. Any help?

[uds5501]

@kushthedude In the server, authorisation is being handled by flask_login and maybe this 422 error is from there only.

{
    "jsonapi": {
        "version": "1.0"
    },
    "errors": [
        {
            "status": "422",
            "title": "Validation error",
            "source": {
                "pointer": "/data/attributes/email"
            },
            "detail": "Not a valid email address."
        }
    ]
}

This is the error trace that I am getting and yeah, this is not being handled by the project so it must be flask_login . Kindly check the documentation for the same

[iamareebjamal]

This has surfaced recently. Even normal emails are denied

[kushthedude]

@iamareebjamal Can i work on it?

[iamareebjamal]

First work on normal email validation failure such as '[email protected]'

[kushthedude]

I am still working for it😅

On Fri, 22 Mar 2019 at 11:45 AM, Saicharan Reddy [e-mail]
wrote:

@kushthedude https://github.com/kushthedude Still working on this?
Would like to take it up if you're involved in other bugs.

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/fossasia/open-event-server/issues/5660#issuecomment-475506509,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AqDJriiCISM4ZrInAej4vMm2KNVfW1Kzks5vZHUOgaJpZM4bd_dm
.

[angmas1]

Still not working, I think it's a major bug. Please resolve this on priority.

[shreyanshdwivedi]

@kushthedude are you working on this? Please resolve this asap or let other contributor try :)

[kushthedude]

@shreyanshdwivedi i completely forgot about it , if anyone wants to takeover please be my guest as i have not started doing anything on it

[shreyanshdwivedi]

Okay. I'm working on it then

[kushthedude]

Btw @shreyanshdwivedi i did some ground work about it and found that this error is gettin causes by flask_login and i am afraid should we modify the external dependancy or not ?

[shreyanshdwivedi]

@kushthedude if this is the case, I think @iamareebjamal can decide it. However I'll once take a look at it to find out the reason for this error

[kushthedude]

@shreyanshdwivedi cool have a look yourself

[iamareebjamal]

Not needed then. Will see if a customer support request comes. Closing. Still comment if you find anything @shreyanshdwivedi

[kushthedude]

Should i closw the issue than @shreyanshdwivedi @iamareebjamal