@dan Ok, it would seem that the 'response.response.user' object does not contain a 'registrations' entry if the user doesn't have any registrations at all.
I've forked, fixed and created a PR.
@dan Ok, it would seem that the 'response.response.user' object does not contain a 'registrations' entry if the user doesn't have any registrations at all.
I've forked, fixed and created a PR.
@dan Thank you, but the example app now no longer works for me. Clicking the 'login' link on the example page now gives the following error on the Node.js console:
in error
{}
This appears to have been triggered by line 34 of routes/index.js.
The breakage seems to have been introduced by commit 5d55150 -- my only changes are to the clientId, clientSecret and the auth URLs (I'm not running on localhost:9011) and the example was working fine for me immediately prior to this commit.
I've changed every timezone setting I can find, but the UI is still showing dates in American format. How can I change this, and is there a way of setting the default timezone for all new users, etc?
I'm just starting out with FusionAuth. I'm following the '5-Minute Setup Guide' and am using the fusionauth-node-example on GitHub.
At the point where I create the test user I thought I'd try logging in to the application, to verify that the login is rejected without the application registration. To my surprise I find that the test application accepts the user login without requiring a registration. What have I done wrong?