This chapter explains several customizations you can make to Oracle Authorization Policy Manager, the Oracle Entitlements Server Administration Console. It contains the following sections:
All customizations described in this chapter require modifying data in the following files:
$ORACLE_HOME$/apm/modules/oracle.security.apm_11.1.1/oracle.security.apm.ear $ORACLE_HOME$/apm/modules/oracle.security.apm_ 11.1.1/oracle.security.apm.core.view.war
Customizations applied to a version of Authorization Policy Manager must be specified anew every time a new version of the tool is installed.
Tip:
Before you begin, it is recommended that you backup the Authorization Policy Manager EAR and WAR files listed above.
To customize Authorization Policy Manager, proceed as follows:
Unzip the tool's EAR and WAR files, and the view WAR file, as illustrated by the following commands:
$ unzip -d $tempDir/ear $ORACLE_HOME$/apm/modules/oracle.security.apm_ 11.1.1/oracle.security.apm.ear $ unzip -d $tempDir/war $tempDir/ear/oracle.security.apm.war $ unzip -d $tempDir/viewWar $ORACLE_HOME$/apm/modules/ oracle.security.apm_11.1.1/oracle.security.apm.core.view.war
Modify one or more unzipped files, as explained in the remaining sections of this chapter.
Zip anew the tool's EAR and WAR files, and the view WAR file, as illustrated by the following commands:
$ zip $tempDir/ear/oracle.security.apm.war $tempDir/war/* $ zip $ORACLE_HOME$/apm/modules/oracle.security.apm_ 11.1.1/oracle.security.apm.ear $tempDir/ear/* $ zip $ORACLE_HOME$/apm/modules/oracle.security.apm_ 11.1.1/oracle.security.apm.core.view.war $temp/viewWar/*
Redeploy Authorization Policy Manager.
To customize headers, footers, and logo, proceed as follows:
Unzip the view WAR file. For details, see Customizing Authorization Policy Manager.
Open for edit the file AuthPolicyMgr.jspx and apply any of the following modifications, as appropriate.
To specify a new branding title, modify the branding facet as illustrated in the following snippet:
<f:facet name="branding"> <af:outputText value="My Custom Application Title" noWrap="true" id="ot1"/> </f:facet>
To specify a new footer, modify the appAbout and appCopyright facets as illustrated in the following snippet:
<f:facet name="appAbout"> <af:outputText value="My Custom Footer at Right" noWrap="true" id="ot2"/> </f:facet> <f:facet name="appCopyright"> <af:outputText value="My Custom Footer at Left" noWrap="true" id="ot3"/> </f:facet>
To specify a new logo image, proceed as follows:
Insert your resource in the metaContainer facet as illustrated in the following snippet (leave all other content inside the facet as is):
<f:facet name="metaContainer">
....
<af:resource type="css">
.MyCustomBrandingLogo {
background-image:url(/apm/images/world_36x20.png);
background-position:center;
background-repeat:no-repeat; display:block;
height:2.5em; width:119px;
}
</af:resource>
...
</f:facet>
Specify that style class name as the input attribute to the pageTemplate tag, as illustrated in the following snippet (leave all other content inside the tag as is):
<af:pageTemplate viewId="/templates/IdmShell.jspx"
value="#{bindings.pageTemplateBinding}" id="pt1">
...
<f:attribute name="brandingLogoCls" value="MyCustomBrandingLogo"/>
...
Assuming that you have a new skin available to customize the color scheme, proceed as follows:
Unzip the tool's EAR and WAR files. For details, see Customizing Authorization Policy Manager.
Open for edit the file Trinidad-config.xml, typically located in the folder WAR/WEB-INF.
In that file, specify the value of the new skin in the skin-family tag, as illustrated in the following snippet:
<trinidad-config xmlns="http://myfaces.apache.org/trinidad/config"> ... <skin-family>MyCustomSkin</skin-family> ... </trinidad-config>
To customize the login page and login error page, proceed as follows:
Unzip the tool's EAR file. For details, seeCustomizing Authorization Policy Manager.
Open for edit the file web.xml, typically located in the folder EAR/WEB-INF.
In that file, specify the appropriate values for the form-login-page and form-error-page, under the element form-login-config, as illustrated in the following snippet:
<login-config> <form-login-config> <form-login-page>/MyCustomLoginPage.html</form-login-page> <form-error-page> MyCustomLoginErrorPage.html </form-error-page> </form-login-config> </login-config>