Configuring Big Match web application security (V18.104.22.168 and earlier)
The Big Match offering includes three distinct web applications. By default, security is enabled for all three. To manage security for the web applications, edit the server.xml configuration file associated with the WebSphere® Liberty Profile instance.
Before you begin
About this task
The Big Match offering takes advantage of the security features provided by IBM® WebSphere Liberty profile. Specifically, the Basic Registry creates and stores user credentials. For more detail about Hortonworks security, including information about users and groups, see the links at the end of this topic.
- BigMatchConfigUser - The BigMatchConfigUser security role governs access to the InfoSphere® Big Match Console application.
- BigMatchUser - The BigMatchUser security role governs access to the InfoSphere Big Match Search interface sample. To configure the search interface sample itself, see the link at the end of this topic about installing and configuring the interface sample.
For more information about the syntax for specifying security roles, see the link at the end of this topic about getting started with WebSphere Liberty Profile security.
<security-role name="BigMatchConfigUser"> <user name ="jsmith"/> <user name="jdoe"/> </security-role> <security-role name="BigMatchUser"> <group name="financeDept"/> </security-role>
By default the Big Match WebSphere Liberty Profile instance will use the same Java installation that is running Ambari Server. This can be modified by editing the /usr/ibmpacks/current/bigmatch/wlp/usr/servers/bigmatch-server/server.env file and setting the value of JAVA_HOME to some other JDK/JRE.