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

Clientauth skip lists do not work when user/database names are mixed case #265

Closed
adamguo0 opened this issue Jan 30, 2024 · 1 comment
Closed
Labels
bug Something isn't working

Comments

@adamguo0
Copy link
Contributor

adamguo0 commented Jan 30, 2024

Description

Users/databases on pgtle.clientauth_users_to_skip and pgtle.clientauth_databases_to_skip do not take effect if their names are mixed case.

Steps to reproduce

  1. Register a clientauth function
  2. Create a role with a mixed case name, e.g. CREATE ROLE "MixedCase";
  3. Add it to pgtle.clientauth_users_to_skip and reload config: ALTER SYSTEM SET pgtle.clientauth_users_to_skip = 'MixedCase'; SELECT pg_reload_conf()
  4. Connect as MixedCase

Expected outcome

Clientauth function should be skipped for MixedCase.

Actual outcome

Clientauth function is executed.

This behaviour can be reproduced similarly for mixed-case database names.

@TianzeMYou
Copy link
Contributor

Merged

@adamguo0 adamguo0 closed this as completed Mar 8, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants