php

• CreateVpnOverrides.php
  CreateVpnOverrides.php
• DeleteAllOverridesForUsers.php
  DeleteAllOverridesForUsers.php
• DeleteOverridesForUser.php
  DeleteOverridesForUser.php
• GetOverrides.php
  GetOverrides.php

reference

• createObjects
  Create Softlayer portal user VPN overrides.
• deleteObject
  Use this method to delete a single SoftLayer portal VPN user subnet override.
• deleteObjects
  Use this method to delete a collection of SoftLayer portal VPN user subnet overrides.
• getObject
  Retrieve a SoftLayer_Network_Service_Vpn_Overrides record.
• getSubnet
  Subnet components accessible by a SoftLayer VPN portal user.
• getUser
  SoftLayer VPN portal user.
• SoftLayer_Network_Service_Vpn_Overrides
  The SoftLayer_Network_Service_Vpn_Overrides data type contains information relating user ids to subnet ids when VPN access is manually configured. It is essentially an entry in a 'white list' of subnets a SoftLayer portal VPN user may access.
• SoftLayer_Network_Service_Vpn_Overrides
  Use to manually decide which subnets within your virtual private address space a SoftLayer portal VPN user may access. Stores a 'white list' consisting of a collection of subnet ids matched up against user ids. This class will reject any subnets or users, that don't belong to the account holder. Note that simply assigning overrides to a user does not enforce the rule change. You must set the manual override flag for the VPN user in the SoftLayer_User_Customer class. It is recommended that before you create new VPN subnet overrides, you delete any old ones for a user, since the VPN authentication system limits the number of accessible subnets by a single user to sixty four. This holds true regardless of whether the VPN user accesses the network via SSL or PPTP. After making any changes to a user's VPN settings, you should call SoftLayer_User_Customer::updateVpnUser() on that customer object.