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

Authenticating to the bouncer #27

Open
DanielOaks opened this issue Aug 20, 2017 · 0 comments
Open

Authenticating to the bouncer #27

DanielOaks opened this issue Aug 20, 2017 · 0 comments

Comments

@DanielOaks
Copy link
Member

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.

  1. Server connection password (PASS) of username/network:password - mimics ZNC.
  2. USER of username/network and server connection password (PASS) of the account password - mimics ZNC.
  3. SASL PLAIN for the account login, have just the network name in USER.
  4. SASL CERTFP to auth to the account, having just the network name in 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.

@DanielOaks DanielOaks changed the title Authenticating to GoshuBNC Authenticating to the bouncer Aug 20, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant