tree 1511210a2819221f0aa15d92d98e04c7d0ae8c8f
parent 9ad88ce3fe653ddd6cc52c82b15ed7285de08ac6
author Tony Mak <tonymak@google.com> 1464876076 +0100
committer Tony Mak <tonymak@google.com> 1464948366 +0000

OP_ACTIVATE_VPN should not map to DISALLOW_CONFIG_VPN

They are two different things.
OP_ACTIVATE_VPN means can we allow a vpn app to establish without user
interaction while DISALLOW_CONFIG_VPN means can the user modify vpn
config.

Testing:
1. Turn on DISALLOW_CONFIG_VPN, user cannot modify vpn config through
   setting
2. Turn on DISALLOW_CONFIG_VPN, Dpm.setAlwaysOnVpn works.
3. Reboot after 2, vpn established automatically.

Bug: 29086229
Change-Id: I24899d6c7f0dd62bf441a44c6ee66fee35973a11