-
Notifications
You must be signed in to change notification settings - Fork 140
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
flask-cors authenticated requests with current_user #220
Comments
I figured out the issue. I had to send |
Ahh, sorry to hear you had trouble!
Is there any chance you have the time to make a pull request to add the
information you’d like to see? I’d really appreciate the help!
Thanks,
Cory
On Sun, May 6, 2018 at 12:55 AM Jay Jodiwal ***@***.***> wrote:
Reopened #220 <#220>.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#220 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAbRqfzH6CaoTWx-eAgGheN-N067bSzeks5tvqxmgaJpZM4Tz6_S>
.
--
@corydolphin <https://twitter.com/CoryDolphin>
339-440-3020 <javascript:void(0);>
|
Sure. I'll be glad to do that. By adding the info you mean in readme, right ? Edit |
I have added after creating flask app instance
CORS(app, supports_credentials=True)
for login and checking authentication I am using
current_user.is_authenticated results false. But works perfectly fine in postman. Also if I remove CORS and try current_user.is_authenticated it works. So I'm sure issue is related with CORS.
Many similar issues are already present. Looking through them suggests that session problem is solved by using
supports_credentials=True
but current_user returns anonymous for me even after setting this argumentThe text was updated successfully, but these errors were encountered: