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

Do not allow commenting from disabled auth provider #1660

Closed
cowsay1 opened this issue Aug 20, 2023 · 5 comments
Closed

Do not allow commenting from disabled auth provider #1660

cowsay1 opened this issue Aug 20, 2023 · 5 comments
Labels
Milestone

Comments

@cowsay1
Copy link

cowsay1 commented Aug 20, 2023

If the user logged in (worst case is anon), and after that we turn off auth provider that he used, he can still leave comments until he logged out.

@umputun
Copy link
Owner

umputun commented Aug 20, 2023

There is a workaround to invalidate all tokens by changing the secret. This should work but can be too extreme as it will force relogin for all the users. Alternatively, you can wait until the cookie expires; eventually, the user with a turned-off provider will be kicked off.

To address it properly, I have created go-pkgz/auth#176, which will check user id and will reject users with invalidated providers right away.

@umputun
Copy link
Owner

umputun commented Aug 20, 2023

@paskal Initially, I've tried to add this verification as a part of token.ValidatorFunc with smth like this:

func (s *ServerCommand) isAllowedProvider(userID string) bool {
	p := strings.Split(userID, "_")[0] // user id has "provider_" suffix
	switch p {
	case "anonymous":
		return s.Auth.Anonymous
	case "email":
		return s.Auth.Email.Enable
	case "telegram":
		return s.Auth.Telegram
	case "github":
		return s.Auth.Github.CID != "" && s.Auth.Github.CSEC != ""
	case "google":
		return s.Auth.Google.CID != "" && s.Auth.Google.CSEC != ""
	case "facebook":
		return s.Auth.Facebook.CID != "" && s.Auth.Facebook.CSEC != ""
	case "microsoft":
		return s.Auth.Microsoft.CID != "" && s.Auth.Microsoft.CSEC != ""
	case "yandex":
		return s.Auth.Yandex.CID != "" && s.Auth.Yandex.CSEC != ""
	case "twitter":
		return s.Auth.Twitter.CID != "" && s.Auth.Twitter.CSEC != ""
	case "patreon":
		return s.Auth.Patreon.CID != "" && s.Auth.Patreon.CSEC != ""
	case "apple":
		return s.Auth.Apple.CID != "" && s.Auth.Apple.TID != "" && s.Auth.Apple.KID != ""
	default:
		return true
	}
}

This code is clear and easy to read; however, I didn't like it as it adds another place to maintain as we add a new provider. So, the final approach I picked is to add this check directly to auth library which is based on the list of all the active/registered providers.

umputun added a commit that referenced this issue Aug 20, 2023
@paskal paskal added the backend label Aug 20, 2023
umputun added a commit that referenced this issue Aug 21, 2023
adopt tests for the mandatory provider check

fix leftover test for the server
@umputun
Copy link
Owner

umputun commented Aug 21, 2023

@cowsay1 The change I made to auth library was integrated. Pls, check the master image and let me know if there are any issues. If all good I'll release a hotfix version

@cowsay1
Copy link
Author

cowsay1 commented Aug 21, 2023

Looks like all good 👍

@umputun
Copy link
Owner

umputun commented Aug 21, 2023

tagged as v1.21.1

@umputun umputun closed this as completed Aug 21, 2023
@paskal paskal added this to the v1.12.1 milestone Sep 16, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants