Skip to content

Recommend authenticating as only one user per connection #1384

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.

Sign up for GitHub

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

Closed
wants to merge 1 commit into from
Closed

Recommend authenticating as only one user per connection #1384

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 3 additions & 1 deletion source/core/access-control.txt
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -42,7 +42,9 @@ service is available. See
same database as a different user, the second authentication
invalidates the first. You can, however, log into a *different*
database as a different user and not invalidate your authentication
on other databases.
on other databases, though this is not a recommended approach.
Generally we recommend that each client connection be authenticated
as exactly one user.

.. _authorization:

Expand Down