diff options
author | Thomas Haller <thaller@redhat.com> | 2018-04-09 16:04:46 +0200 |
---|---|---|
committer | Thomas Haller <thaller@redhat.com> | 2018-04-13 09:09:46 +0200 |
commit | 798b2a7527bddadcec37b48183da313fbc961e45 (patch) | |
tree | a8511cd7685eb37694be96a00cade2a0fdd5e8b2 /introspection/org.freedesktop.NetworkManager.VPN.Plugin.xml | |
parent | 41abf9f8e81423eff0ef888d17a5454d0b5750bf (diff) | |
download | NetworkManager-798b2a7527bddadcec37b48183da313fbc961e45.tar.gz |
auth-manager: let NMAuthChain always call to NMAuthManager for dummy requests
NMAuthChain's nm_auth_chain_add_call() used to add special handling for
the NMAuthSubject. This handling really belongs to NMAuthManager for two
reasons:
- NMAuthManager already goes through the effort of scheduling an idle
handler to handle the case where no GDBusProxy is present. It can
just as well handle the special cases where polkit-auth is disabled
or when we have internal requests.
- by NMAuthChain doing special handling, it makes it more complicated
to call nm_auth_manager_check_authorization() directly. Previously,
the NMAuthChain had additional logic, which means you either were
forced to create an NMAuthChain, or you had to reimplement special
handling like nm_auth_chain_add_call().
Diffstat (limited to 'introspection/org.freedesktop.NetworkManager.VPN.Plugin.xml')
0 files changed, 0 insertions, 0 deletions