You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I followed the setup instructions and got the UI running on port 4000 and the server on 5000. I changed the "linkedin" client config to use "live" (Microsoft) and entered my client ID and put my secret in the server's config.development.js file.
I can log in to Live on port 4000 but then the UI tries to reach /auth/live on port 4000 instead of 5000.
Did I miss a step where I need to tell aurelia-auth to use 5000 for the token exchange call?
The text was updated successfully, but these errors were encountered:
Hi,
In the builds folder, there is serve.js and there you will learn that things a proxied.
Obviously, the proxying happens only in the DEV environment, when moving the production you should adapt to your own server side config.
Cheers
paul.
I followed the setup instructions and got the UI running on port 4000 and the server on 5000. I changed the "linkedin" client config to use "live" (Microsoft) and entered my client ID and put my secret in the server's config.development.js file.
I can log in to Live on port 4000 but then the UI tries to reach /auth/live on port 4000 instead of 5000.
Did I miss a step where I need to tell aurelia-auth to use 5000 for the token exchange call?
The text was updated successfully, but these errors were encountered: