Administrative user management

This section describes how to set up users and user rights for accessing administrative instruments.

Administrative access to FEJ can be obtained through:

The configuration of users and their access rights is performed by using Spring Security.

For details on monitoring and management using a remote shell, refer to FIXEdge Java Administration.

Security configuration

FEJ uses Spring Security for authentication purposes. Security configuration is stored in the fej-security.xml file.

File-based authentication

By default, for testing purposes, the FEJ container uses simple, in-memory authentication with the NoOpPasswordEncoder encoder and plain-text credentials.

For other password encoder options, please check Spring Security 5.0

If you need a more complex authentication solution, please refer to Spring Security documentation.

<!-- Password encode bean to support passwords encripted with BCrypt way in -->
<!--<bean id="passwordEncoder" class=""/>-->

<bean id="passwordEncoder" class="" factory-method="getInstance"/>

<sec:authentication-manager id="authenticationManager">
        <sec:password-encoder ref="passwordEncoder"/>
        <sec:user-service id="userDetailsService" properties=""/>

There are several defined user roles, that can be used :

Users are defined by the external properties file named 

# Spring security file format
# password depends on configured spring PasswordEncoder (hash or plain text)
# Format: username=password,grantedAuthority[,grantedAuthority][,enabled|disabled]

# password is plain text

# password is hash (bcrypt)

FEJ also supports authentication against an LDAP server.LDAP authentication

Before getting deep into LDAP authentication, let’s get familiar with some LDAP terms.



Distinguished name, a unique name that is used to find a user on an LDAP server, for example, in the Microsoft Active Directory.


Organization unit


LDAP Bind is an operation in which LDAP clients send bindRequest to an LDAP user, including a username and password. If
the LDAP server finds that the user and password is correct, it grants access to the LDAP server.


LDAP search is an operation that is performed to retrieve the Dn of a user by using some user credentials.


LDAP directory’s top element, like the root of a tree.


Branch in an LDAP tree that can be used as a base for the LDAP search operation.

To activate the authentication of administrative users with LDAP, it needs to replace the authentication-manager bean definition in fej-security.xml file:

<ldap-server url="ldap://,dc=com" /

See more details about configuration authentication with the LDAP server in Spring Documentation.

Administrative shell configuration

To configure access to the interactive shell, shell configuration properties are used.

Shell configuration properties are defined by the file.

NameDefault valueDescription



Authentication mechanism



SSH server port



Authentication timeout of the SSH server (in milliseconds)



Idle timeout of the SSH server (in milliseconds)



Character encoding

FEJ uses the Java shell called ‘CRaSH’. For more information about configuration properties, please refer to the CRaSH reference documentation.

Administrative JMX configuration

The file contains settings for defining the JMX port and the URL for accessing the JMX service.

For details, refer to the official Java documentation.

Monitoring and management by using the JMX technology is described at the Management over JMX section.

FIXICC access configuration

For details on FIXICC access configuration, refer to the FIXICC & FEJ Integration User Guide.