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
Hi,
It seems README is missing one fix for the "authorize" route:
$ sed -i '' 's?"authorize"?"http://localhost:8081/lockdin/authorize"?g' data/parameters.json
If you don't make this change then the first step of the authorization code process requests the <CLIENT_URL>/lockdin/authorize instead of <SERVER_URL>/lockdin/authorize.
The demo however will still work because both server and client use the same sqlite db. But if you make true server and client from two copies of the source code, you'll get the error.
The text was updated successfully, but these errors were encountered:
Hi,
It seems README is missing one fix for the "authorize" route:
If you don't make this change then the first step of the authorization code process requests the
<CLIENT_URL>/lockdin/authorize
instead of<SERVER_URL>/lockdin/authorize
.The demo however will still work because both server and client use the same sqlite db. But if you make true server and client from two copies of the source code, you'll get the error.
The text was updated successfully, but these errors were encountered: