We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
So there are two sides of authentication, clients connecting into the bouncer, and then the bouncer authenticating to networks.
This issue roughly goes over the ways clients should be able to authenticate their account (and which network they want to connect to) to the bouncer.
PASS
username/network:password
USER
username/network
We currently support 1, adding 2 for compatibility with ZNC makes sense. 3 seems pretty obvious and shouldn't be too difficult for me to implement.
4 is a bit weird, but I think doing auth with TLS client certs makes sense to look at some point a fair ways down the road.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
So there are two sides of authentication, clients connecting into the bouncer, and then the bouncer authenticating to networks.
This issue roughly goes over the ways clients should be able to authenticate their account (and which network they want to connect to) to the bouncer.
PASS
) ofusername/network:password
- mimics ZNC.USER
ofusername/network
and server connection password (PASS
) of the account password - mimics ZNC.USER
.USER
.We currently support 1, adding 2 for compatibility with ZNC makes sense. 3 seems pretty obvious and shouldn't be too difficult for me to implement.
4 is a bit weird, but I think doing auth with TLS client certs makes sense to look at some point a fair ways down the road.
The text was updated successfully, but these errors were encountered: