New user role selection not being saved on signup.

[coldridj]

Clean analytics server installation. New user (developer) created. After logging in various API calls calls fail with HTTP error 403 in different sessions

/game/public

/api/roles

[coldridj]

Upon further investigation, the developer role is not being assigned to the new user reliably. When added via the admin user management screen this issue is no longer present.

[coldridj]

This should not be closed, I can consistently repeat this error. User roles are not present on user after signup via /api/proxy/afront/signup - role selection can be seen in POST data.

POST: /api/signup {"username":"Test4","email":"jack+test4@playgen.com","password":"password","role":"developer","prefix":"gleaner"}

[gorco]

I forgot to comment when I closed the issue.

The user with developer role doesn't have permissions for /game/public (this is intentioned like https://github.com/e-ucm/rage-analytics/issues/34) And the same with /api/roles route (only the admin have permissions to see the roles list)

Both are design decisions.

So the problem is like https://github.com/e-ucm/rage-analytics/issues/34 (I closed it for that reason, the problem is the same) We'll remove the console log and the call for the developer in a future, but for now is usefull for us.

[coldridj]

I have changed the title of this issue - the issue is that the selected role is not being set on the new user despite having been selected in the signup form. The http errors were misleading.

[gorco]

Ok, we'll check this.