Authenticate device is ignoring username field on https?

Local Setup
1

Hello,

When running on a http server and creating a new user with AuthenticateDeviceAsync and the username field, it works normally. When running on https server with the same parameters, it seems to ignore the username field and generate a random username.

2

Hi @crowie,

I don’t see how the protocol would affect user creation logic. Can you provide a reproducible example?

Best

3

image
image1893×471 50.6 KB

image
image409×101 6.75 KB

image
image434×101 6.88 KB

image
image197×195 3.52 KB

Using the same code just changing, scheme from http to https and port from 7350 to 443.
USERNAMECHECK is created on http, but swapping to https generates a random name.

I am using Unity 6000.1.2f1 and Nakama 3.15.0

4

Something isn’t adding up - how did you set up https on Nakama?

Also, I’d urge you to upgrade to the latest Nakama version and the latest SDK as well.

5

I have updated both and still the same result.

http for host is using an ip address hosted to a docker container.
https for host is using a domain from cloudfront that is taking http traffic into https

6

@crowie are the query params being forwarded correctly to the server? Because I can’t replicate the issue locally.

7

I haven’t changed any settings besides what I’ve shown. How would I check the query params?

8

I mean your cloudfront proxy.