Applies To:
Show VersionsBIG-IP APM
- 13.0.1, 13.0.0
About rewrite profiles for Portal Access
A Portal Access rewrite profile defines certificate settings for Java patching, client caching settings for a virtual server, split tunneling settings, and URI translation settings. You can configure a rewrite profile and select the rewrite profile when you configure the virtual server for a portal access policy. Alternatively, you can use the default Portal Access rewrite profile, rewrite-portal.
Portal access rewrite profile Portal Access settings
Use these properties to configure a resource item for a portal access resource.
In the rewrite profile Portal Access settings, you can configure settings for client caching and split tunneling.
These options are available for Portal Access in the rewrite profile.
Client Cache setting | Description |
---|---|
CSS and JavaScript | Caches CSS and JavaScript. This is the default rewrite caching configuration, and provides a balance between performance and security. |
CSS, Images and JavaScript | Caches CSS, images, and JavaScript. This provides faster client performance but is slightly less secure because of cached images in the client browser cache. |
No Cache | Caches nothing. This provides the slowest client performance and is the most secure. |
Cache All | Uses the unmodified cache headers from the backend server. |
Enable split tunneling: Set this option to Yes to enable split tunneling for portal access sessions that use this rewrite profile. Set this option to No to force all traffic through the tunnel for portal access sessions that use this rewrite profile.
About split tunneling with rewrite profiles
Consider these factors when split tunneling is enabled:
- Access Policy Manager matches the URI to the expressions specified on the Bypass list first. If an expression matches, then the URI is bypassed and links are not rewritten.
- If the URI does not match the Bypass list, then it is compared to the Rewrite list. If the URI matches the expressions specified on the Rewrite list, the URI links are rewritten. If there are no matches, links are not rewritten.
- If the URI does not match anything on the Bypass or Rewrite lists, and if the host name in the URI is a short name, not a fully qualified domain name, then links for that URI are rewritten.
Portal access rewrite profile JavaPatcher settings
Use these properties to configure a resource item for a portal access resource.
In a rewrite profile, you can configure settings for Java patching. These settings configure certificate authorities, signing rights, and certificate revocation that is required for to patch some Java apps.
These options are available for JavaPatcher in the rewrite profile.
Setting | Value | Description |
---|---|---|
Trusted Certificate Authorities | List selection | Select the certificate authority to use for Java app link rewriting from the list of predefined Certificate authorities on the system, to use with Java app rewriting. |
Signer | List selection | Select the Java app signer to use for app re-signing, from a list of existing signers on the system. Select None if the app is unsigned. |
Signing Key | List selection | Select the private key from a list of existing keys on the system for Java app re-signing. Select None if the app is unsigned or does not require a signing key. |
Signing Key Pass Phrase | Text (obscured) | To encrypt the private signing key with a passphrase, type the private key pass phrase. |
Certificate Revocation List (CRL) | List selection | Select the CRL from the list, if one is defined on the system. |
Portal access rewrite profile URI translation settings
Use these properties to configure URI translation for a rewrite profile with Portal Access.
In a rewrite profile, you can configure settings for rewriting headers in the request and the response.
These options are available for URI translation in Request Settings.
Property | Description |
---|---|
Rewrite Headers | Select this option to rewrite headers in Request Settings. |
Insert X-Forwarded For Header | Select this option to add the X-Forwarded For (XFF) header, to specify the originating IP address of the client. |
Insert X-Forwarded Proto Header | Select this option to add the X-Forwarded Proto header, to specify the originating protocol of the client. |
Insert X-Forwarded Host Header | Select this option to add the X-Forwarded Host header, to specify the originating host of the client. |
These options are available for URI translation in Response Settings.
Property | Description |
---|---|
Rewrite Headers | Select this option to rewrite headers in the response. |
Rewrite Content | Select this option to rewrite links in content in the response. |