GDBusAuthObserver: Fix mixup between authentication and authorization

Authentication is about proving who I am; authorization is about
whether, given the knowledge of who I am, I am allowed to do something.
GDBusServer and GDBusConnection carry out authentication automatically,
but rely on the library user to carry out authorization.

Signed-off-by: Simon McVittie <smcv@collabora.com>
This commit is contained in:
Simon McVittie 2019-06-05 13:47:09 +01:00 committed by Philip Withnall
parent f5a01e0e4a
commit 1da3280b9e

View File

@ -39,7 +39,7 @@
* signals you are interested in. Note that new signals may be added
* in the future
*
* ## Controlling Authentication # {#auth-observer}
* ## Controlling Authorization # {#auth-observer}
*
* By default, a #GDBusServer or server-side #GDBusConnection will accept
* connections from any successfully authenticated user (but not from