Skip to content

"authorize_route" needs to be replaced too #59

@ruslanbes

Description

@ruslanbes

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.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions