You're viewing help content for version:

Learn how to administer user accounts and services that, although required in a private development environment, are not required in a production environment of AEM Forms on JEE.

Generally, developers do not use the production environment to build and test their applications. Therefore, you must administer user accounts and services that, although required in a private development environment, are not required in a production environment.

This article describes methods for reducing the overall attack surface through administration options that AEM Forms on JEE provides.

Disabling non-essential remote access to services

After AEM Forms on JEE is installed and configured, many services are available for remote invocation over SOAP and Enterprise JavaBeans™ (EJB).The term remote, in this case, refers to any caller that has network access to the SOAP, EJB, or Action Message Format (AMF) ports for the application server.

Although the AEM Forms on JEE services require valid credentials to be passed for an authorized caller, you should allow only remote access to the services that you need to be remotely accessible. To achieve limited accessibility, you should reduce the set of remotely accessible services to the minimum possible for a functioning system and then enable remote invocation for the additional services that you need.

AEM Forms on JEE services always need at least SOAP access. These services are typically required for use by Workbench but also include services that are called by the Workspace web application.

Complete this procedure using the Applications and Services web page in Administration Console:

  1. Log in to Administration Console by typing the following URL in a web browser:

             http://[host name]:[port]/adminui
  2. Click Services > Applications and Services > Preferences.

  3. Set the Preferences to view up to 200 services and endpoints on the same page.

  4. Click Services > Applications and Services > Endpoint Management.

  5. Select EJB from the Provider list and then click Filter.

  6. To disable all EJB endpoints, select the check box beside each one in the list and click Disable.

  7. Click Next and repeat the previous step for all EJB endpoints. Ensure that EJB is listed in the Provider column before you disable endpoints.

  8. Select SOAP from the Provider list and then click Filter.

  9. To remove SOAP endpoints, select the check box beside each one in the list and click Remove. Do not remove the following endpoints:

    • AuthenticationManagerService

    • DirectoryManagerService

    • JobManager

    • event_management_service

    • event_configuration_service

    • ProcessManager

    • TemplateManager

    • RepositoryService

    • TaskManagerService

    • TaskQueueManager

    • TaskManagerQueryService

    • WorkspaceSingleSignOn

    • ApplicationManager

  10. Click Next and repeat the previous step for SOAP endpoints that are not in the above list. Ensure that SOAP is listed in the Provider column before you remove endpoints.

Disabling non-essential anonymous access to services

Some forms server services permit unauthenticated (anonymous) invocation for some operations. This means that one or more operations exposed by the service may be invoked as any authenticated user or as no authenticated user at all.

  1. Log in to administration console by typing the following URL in a web browser:

             http://[host name]:[port]/adminui
  2. Click Services > Applications and Services > Service Management.

  3. Click the name of the service that you want to disable (for example, AuthenticationManagerService).

  4. Click the Security tab,deselect Anonymous Access Allowed, and click Save.

  5. Complete steps 3 and 4 for the following services:

    • AuthenticationManagerService

    • EJB

    • Email

    • JobManager

    • WatchedFolder

    • UsermanagerUtilService

    • Remoting

    • RepositoryProviderService

    • EMCDocumentumRepositoryProvider

    • IBMFilenetRepositoryProvider

    • FormAugmenter

    • TaskManagerService

    • TaskManagerConnector

    • TaskManagerQueryService

    • TaskQueueManager

    • TaskEndpointManager

    • UserService

    • WorkspaceSearchTemplateService

    • WorkspacePropertyService

    • OutputService

    • FormsService

    If you intend to expose any of these services for remote invocation, you should also consider disabling anonymous access for these services. Otherwise, any caller with network access to this service may invoke the service without passing valid credentials.

    Anonymous access should be disabled for any services that are not needed. Many internal services require anonymous authentication to be enabled because they need to be invoked by potentially any user in the system without being preauthorized.

Changing the default global time-out

End users can authenticate to AEM Forms through Workbench, AEM Forms web applications, or custom applications that invoke AEM Forms server services. One global time-out setting is used to specify how long such users can interact with AEM Forms (using a SAML-based Assertion) before they are forced to reauthenticate. The default setting is two hours. On a production environment, the amount of time needs to be reduced to the minimum number of minutes acceptable.

Minimize reauthentication time limit

  1. Log in to administration console by typing the following URL in a web browser:

             http://[host name]:[port]/adminui
  2. Click Settings > User Management > Configuration > Import And Export Configuration Files.

  3. Click Export to produce a config.xml file with the existing AEM Forms settings.

  4. Open the XML file in an editor and locate the following entry:

    <entry key=”assertionValidityInMinutes” value=”120”/>

  5. Change the value to any number greater than 5 (in minutes) and save the file.

  6. In administration console, navigate to the Import And Export Configuration Files page.

  7. Enter the path to the modified config.xml file or click Browse to navigate to it.

  8. Click Import to upload the modified config.xml file and then click OK.

This work is licensed under a Creative Commons Attribution-Noncommercial-Share Alike 3.0 Unported License  Twitter™ and Facebook posts are not covered under the terms of Creative Commons.

Legal Notices   |   Online Privacy Policy