Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Combine public/private API endpoints from services #66

Closed
defuz opened this issue Apr 25, 2017 · 1 comment · Fixed by #104
Closed

Combine public/private API endpoints from services #66

defuz opened this issue Apr 25, 2017 · 1 comment · Fixed by #104
Assignees
Milestone

Comments

@defuz
Copy link
Contributor

defuz commented Apr 25, 2017

No description provided.

@defuz defuz mentioned this issue Apr 25, 2017
23 tasks
@defuz defuz added this to the Release 0.1 milestone Apr 25, 2017
@dj8yfo
Copy link
Contributor

dj8yfo commented Apr 25, 2017

@defuz rename to public/private api endpoints.
As i see it, each node should to have 2 api ports:

  1. for handling public requests from anyone (all public endpoints from all services combined here).
  2. for handling private requests from node maintainer/s (all private endpoints from all services combined here). The only case this is actual now is for configuration service: the node signs propose or vote with its machine key on behalf of the entity, who put request onto private endpoint.
    If not, we may have to add other means of authentication and, probably, combine with Separate keys for signing consensus messages and transactions #62

@slowli

@defuz defuz changed the title Combine public API endpoints from services Combine public/private API endpoints from services Apr 25, 2017
stanislav-tkach added a commit to stanislav-tkach/exonum that referenced this issue Feb 10, 2018
stanislav-tkach pushed a commit to stanislav-tkach/exonum that referenced this issue Apr 4, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging a pull request may close this issue.

3 participants