EJB Allowlist and Flex Access Validation
The cesejb application validates EJB method calls received through the OMA/Flex request queue. REST_ALLOWLIST controls which methods may be invoked for each application and server. These checks supplement existing authentication and EJB authorization.
Install and Maintain the Allowlist
The standard NMS setup path loads nms_schema_rest_allowlist.sql and nms_rest_allowlist.sql as an administrator. The generated product data is derived from EJB calls discovered in nms-ws.jar, including valid calls without a direct REST endpoint. Use this product baseline before adding project-specific restrictions. Maintain project additions or overrides in the project's rest_allowlist SQL family using the standard NMS SQL setup conventions.
REST_ALLOWLIST contains these columns:
• REST_ALLOWLIST_ID: generated row identifier.
• APP: application match value, such as FLEX or OMA.
• SERVER: server-name match value. The name is the hostname unless overridden by the nms.servername system property.
• HTTP, REST_PATH, REST_CLASS: endpoint metadata for tracing a row to its REST entry point. These values may be null for calls without a direct endpoint.
• BEAN: EJB interface name.
• METHOD: EJB method name.
• ACTIVE: Y enables the row; N excludes it from the active allowlist.
The runtime checks active APP, SERVER, BEAN, and METHOD values; an asterisk (*) is a supported wildcard in those match values. HTTP, REST_PATH, and REST_CLASS are traceability metadata, not additional runtime request checks. Disabling one endpoint's row does not block an EJB method if another active row, including a wildcard or non-endpoint row, still permits the same method for that application/server. Review all matching rows when restricting access.
Configure Production Enforcement
In the deployed server configuration derived from $NMS_CONFIG/jconfig/server/CentricityServer.properties, explicitly set:
nms-ws.learning_mode = false
With learning mode disabled, a queued call without an active matching allowlist entry is rejected. Verify the effective deployed value rather than assuming the installed template disables learning mode. Restrict allowlist maintenance to authorized database administrators. Normal runtime access requires SELECT; additional DML privileges are needed only for learning mode.
After changing the allowlist or these server properties, reload the configuration with:
Action any.pub* ejb refresh
This command refreshes publisher state and other caches as well as the mobile security rules. Coordinate it with normal operational procedures. A managed-server restart also reloads the configuration.
Flex Group and User‑Type Validation
Flex requests also undergo group and user-type checks in cesejb. Configure the following comma-delimited pattern lists in CentricityServer.properties to match the site's approved WebLogic groups and Flex user types:
flex.read_only_groups
flex.read_write_groups
flex.read_only_user_types
flex.read_write_user_types
An asterisk (*) is supported in these pattern lists. For a group or user type matching both read-only and read-write patterns, the read-only classification takes precedence. In the normal Flex validation path, a request is denied if no configured group matches, no configured Flex user type matches, or a read-write group is asserted without a matching read-write user type. Use narrowly scoped group patterns and review WebLogic role mappings to avoid admitting privileged administrator or service groups through broad patterns. These Flex checks do not replace the OMA mobile-user permissions and application-key validation described below.
Controlled Learning Mode
Use learning mode only in a controlled non-production environment to discover required calls missing from the allowlist:
1. Have a database administrator verify SELECT and the required INSERT, UPDATE, and DELETE privileges on the underlying REST_ALLOWLIST table for CES_RW. Check the actual installed grants before adding or removing privileges.
2. Set nms-ws.learning_mode = true and reload the configuration as described above.
3. Exercise only approved OMA/Flex workflows. A previously unlisted call is logged and inserted as an active row using its runtime APP, SERVER, BEAN, and METHOD values, then allowed to execute if the insert succeeds. The learned row has no REST endpoint metadata. Learning mode does not bypass the separate Flex identity checks.
4. Review the learned rows and maintain approved entries in the project configuration; remove entries that should not be allowed.
5. Set nms-ws.learning_mode = false, withdraw temporary DML privileges that are no longer required, and reload again before validating normal enforcement.
Never leave learning mode enabled in production.
Troubleshooting
Search the cesejb application-server logs for nms-security when an OMA/Flex request is denied. Inspect the reported method and reason, active allowlist rows for the application/server, and, for Flex, the user's group and user-type configuration. Resolve the missing approved entry or identity configuration instead of enabling learning mode in production.