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

Client authentication #189

Closed
alexsilva opened this issue Mar 8, 2016 · 2 comments
Closed

Client authentication #189

alexsilva opened this issue Mar 8, 2016 · 2 comments

Comments

@alexsilva
Copy link

@alexsilva alexsilva commented Mar 8, 2016

The document clearly explains how the server must do to authenticate crendenciais sent by the client, but fails to explain how the client sends authentication.

It does not have an api to send authentication data ?

@alexsilva
Copy link
Author

@alexsilva alexsilva commented Mar 8, 2016

It was very difficult to understand how the authentication flow works,
but some have done it in a simple way.

NorthCat

client
server

The reason not be simple should be a native api.

@coldfix coldfix closed this in c4cb20e Jul 9, 2017
@coldfix
Copy link
Contributor

@coldfix coldfix commented Jul 9, 2017

I've added a reference to the corresponding client side function.

coldfix added a commit that referenced this issue Jul 26, 2017
- Add missing endpoints config in ThreadPoolServer (#222)
- Fix jython support (#156,#171)
- Improve documentation (#158,#185,#189,#198 and more)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants