[SOLVED] Discord Oauth not save cookie in development

Is it possible to config it or am I forced to add another redirection? Appwrite is self-hosted behind a proxy.

Adding an extra redirect url in discord developer protal works bc my proxy automatic forward the traffic, but is there any other way to set the redirect_uri to https

and for the Discord Oauth2 I really dislike how Appwrite is using the email and handler for the user. What if the user changed their Discord linked email? Is it possible to use the user ID or something like that instead

and I'm facing the same issue as #channel, maybe it's the cookie reason? I'm running Appwrite behind Apache2, maybe that might cause some issue?

This is because I have to link a backend which is a discord bot to the frontend. Just by reading the email I have no idea who is who because the backend stores the user id. Is there any workaround for this? And I see there is a optional argument for the scope, is there anyway I can receive that information in my app after the redirection?

You should be proxying to Appwrite using https

I tried, things got broken and I stayed. I use my own SSL and stuffs, with other services running as well

Is there any config or anything that tells appwrite to redirect to https?

The appwrite session that is created should have a provider user id. If that isn't the right value, you can probably use the provider access token to make API calls to discord and fetch the username.

Appwrite uses traffic or whatever that proxy service called and I use Apache2, bit of incompatibility

Yes, Appwrite has a feature to redirect http to https

Your SSL in front of your proxy shouldnt matter

How to check?

Ye, but for some reason a lot of problem occurs when I proxy https to https, so I just stayed

Get the session: https://appwrite.io/docs/client/account?sdk=web-default#accountGetSession

What problems?

Such as login fails, or page not being served. It's been a while ago can't remember all

Weird...I highly recommend proxying to Appwrite using https

I'll try next time I get on

But HTTP works tho

Even realtime

So basically not use the appwrite auth system?

You already ran into the http redirect problem. You may also run into a cookie problem

No, you get the session after logging in

It did turns out fine when I add another redirect in discord dev portal, and it's just the problem the the url parameter that appwrite redirected named "redirect_uri=http..."