Enabling cross launch to Mid Tier
When you want to open to Mid Tier from different applications, the HttpHeaderSecurityFilter filter might block the x-FRAME-OPTIONS header. To overcome this issue, use one of the following options:
- In the Centralized Configuration, set the arsystem.security_iframe_allowfromurls parameter to Self or URI.
- Go to installationDirectoy\BMC Software\ARsystem\midtier\WEB-INF folder and open the web.xml file. In the HttpHeaderSecurityFilter filter modify the ClickJackMode parameter.
To open Mid Tier from Centralized Configuration
- Log in toMid Tier.
- Select AR System Administration > AR System Administration Console
- Select System > General > Centralized Configuration.
- In the Component Name list, select arsystem.bmc.arsys.midtier component.
This component is displayed only if you configure the AR System serverby using Centralized Configuration. - In the Setting Name list, select the arsystem.security_iframe_allowfromurls parameter.
Select the Self or URI option to set the parameter value.
The following table lists the options:Option
Description
Self
(Default) Allows the current site to render the content.
URI
Allows the specified URI to render the page.
You can pass multiple URIs.
The URIs must be space-separated; for example,None
Prevents any domain from rendering the content.
- Click Apply, and then click Close.
To enable Mid Tiercross-launch by using the web.xml file
Use the ClickJackMode parameter in the web.xml file:
To disable Mid Tiercross-launch by using the web.xml file
Use the ClickJackEnable parameter in the web.xml file:
Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*