598868

Apple iOS Implementierung Manual

42
Zoom out
Zoom in
Previous page
1/88
Next page
Chapter 4 Infrastructure and integration 42
Cellular and Wi-Fi devices
If your organization chooses to deploy Always-on VPN for iOS devices with both cellular and
Wi-Fi interfaces, two simultaneous IKEv2 tunnels will be established from the device. There are
two scenarios using cellular and Wi-Fi devices:
•
Cellular tunnel and Wi-Fi tunnel terminating on separate IKEv2 servers
Always-on VPN per-interface tunnel conguration keys allow your organization to congure
devices establishing a cellular tunnel to one IKEv2 server and Wi-Fi tunnel to a second IKEv2
server. One benet of this model is that a device can use the same client identify (that is, client
certicate or user/password) for both tunnels since the tunnels terminate on dierent servers.
With dierent servers, your organization also has greater exibility on per-interface-type trac
(cellular trac vs Wi-Fi trac) segregation and control. The drawback is that your organization
has to maintain two dierent IKEv2 servers with identical client authentication policies.
•
Cellular tunnel and Wi-Fi tunnel terminating on same IKEv2 servers
Always-on VPN per-interface tunnel conguration also lets your organization congure a
device to establish the cellular tunnel and the Wi-Fi tunnel to the same IKEv2 server.
Client identity usage:
•
One client identity per device: Your organization can congure the same client identity (that
is, one client certicate or one user/password pair) for both a cellular tunnel and Wi-Fi
tunnel, if the IKEv2 server supports multiple tunnels per client. The benet is that you can
avoid the extra client identity per device and the extra conguration/resource burden on
the server. The drawback is that as a device moves in and out of networks, new tunnels get
established and old tunnels become stale. Depending on the server implementation, the
server may not be able to clean up stale tunnels eciently and accurately. Your organization
must implement a strategy for stale tunnel cleanup on the server.
•
Two client identities per device: Your organization can congure two client identities (that is,
two client certicates or two user/password pairs), one for a cellular tunnel and one for a
Wi-Fi tunnel. The IKEv2 server sees two dierent clients establishing their own tunnel. The
benet of this model is that it works with most server implementations, since many servers
dierentiate tunnels by their client identities and only allow one tunnel per client. The
drawback of this model is doubled client identity management and doubled conguration
and resource management on the server.
Always-on VPN conguration prole
An Always-on VPN conguration prole can be composed either manually, using one of the
Apple conguration prole editors such as Prole Manager, Apple Congurator, or a third-party
MDM vendor. For more information, see Prole Manager Help or Apple Congurator Help.
User interaction keys
To keep users from deactivating the Always-on VPN feature, disallow removal of the Always-on
VPN prole by setting the top-level prole key “PayloadRemovalDisallowed” to true.
To keep users from altering Always-on VPN feature behavior by installing other conguration
proles, disallow UI prole installation by setting the allowUICongurationProleInstallation
key to false under the com.apple.applicationaccess payload. Your organization can implement
additional restrictions using other supported keys under the same payload.
100% resize factor
… 42 …


Need help? Post your question in this forum.

Forumrules


Report abuse

Libble takes abuse of its services very seriously. We're committed to dealing with such abuse according to the laws in your country of residence. When you submit a report, we'll investigate it and take the appropriate action. We'll get back to you only if we require additional details or have more information to share.

Product:

For example, Anti-Semitic content, racist content, or material that could result in a violent physical act.

For example, a credit card number, a personal identification number, or an unlisted home address. Note that email addresses and full names are not considered private information.

Forumrules

To achieve meaningful questions, we apply the following rules:

Register

Register getting emails for Apple iOS Implementierung at:


You will receive an email to register for one or both of the options.


Get your user manual by e-mail

Enter your email address to receive the manual of Apple iOS Implementierung in the language / languages: English as an attachment in your email.

The manual is 2,32 mb in size.

 

You will receive the manual in your email within minutes. If you have not received an email, then probably have entered the wrong email address or your mailbox is too full. In addition, it may be that your ISP may have a maximum size for emails to receive.

Others manual(s) of Apple iOS Implementierung

Apple iOS Implementierung User Manual - German - 99 pages

Apple iOS Implementierung User Manual - Dutch - 100 pages


The manual is sent by email. Check your email

If you have not received an email with the manual within fifteen minutes, it may be that you have a entered a wrong email address or that your ISP has set a maximum size to receive email that is smaller than the size of the manual.

The email address you have provided is not correct.

Please check the email address and correct it.

Your question is posted on this page

Would you like to receive an email when new answers and questions are posted? Please enter your email address.



Info