Try OpenEdge Now
skip to main content
Administration
REST Administration : REST Management Agent and REST Web Application Security Configurations : Security configuration models
 

Security configuration models

OpenEdge provides several security configuration models for the OpenEdge REST Management Agent and the REST Web applications. This section describes the default configurations.
For more information on working with security configurations, see Working with security configurations.
OpenEdge provides the following security configuration models:
Table 84. REST Security Configurations
Configuration Model
OpenEdge Configuration template
Description
Basic
appSecurity-basic-local.xml
This is the default configuration model for the OpenEdge REST Management Agent.
The Basic configuration authenticates clients using HTTP Basic authentication for user accounts, based on the user information in the users.properties file of the REST Management Agent.
appSecurity-basic-ldap.xml
This configuration model authenticates clients using HTTP Basic authentication for user accounts, based on the user information stored in the directory governed by LDAP (Lightweight Directory Access Protocol).
If you choose this security model, proceed toUsing LDAP in security configurations to follow the instructions on applying the security configurations.
appSecurity-basic-oerealm.xml
This configuration model authenticates clients using HTTP Basic authentication for user accounts stored in the OpenEdge Database.
If you choose this security model, proceed to Using Single Point of Authentication security configurations to follow the instructions on applying the security configurations.
appSecurity-basic-saml.xml
This configuration model authenticates clients using HTTP Basic authentication for user accounts stored in the database specified by SAML security specifications.
If you choose this security model, proceed to Using SAML in security configurations to follow the instructions on applying the security configurations.
Form
appSecurity-form-local.xml
This model is very similar to the Basic configuration Model, which authenticates the user accounts based on the user information in the users.properties file of the REST Management Agent.
This model authenticates clients using the generic HTTP Form login authentication for user accounts, based on the users.properties file of the OpenEdge REST Management Agent.
For more information on managing local user accounts, see the Spring Security framework documentation.
appSecurity-form-ldap.xml
This model authenticates clients using the generic HTTP Form login authentication for user accounts stored in the directory governed by LDAP (Lightweight Directory Access Protocol).
If you choose this security model, proceed to Using LDAP in security configurations to follow the instructions on applying the security configurations.
appSecurity-form-oerealm.xml
This model authenticates clients using the generic HTTP Form login authentication for user accounts stored in the OpenEdge Database.
If you choose this security model, proceed to Using Single Point of Authentication security configurations to follow the instructions on applying the security configurations.
appSecurity-form-saml.xml
This configuration model authenticates clients using HTTP Form login authentication for user accounts stored in the database specified by SAML security specifications.
If you choose this security model, proceed to Using SAML in security configurations to follow the instructions on applying the security configurations.
Anonymous
appSecurity-anonymous.xml
This is the default configuration model for the REST Web applications you develop.
With the anonymous security model, you make the Web service public. That is, any user can make requests to the Web service.
Container
appSecurity-container.xml
This model integrates Spring Security framework with the authentication service of the Java container.
The Java container authenticates, and the Spring Security framework controls the authorization to REST Web application resources.
For example, if Tomcat is your choice of Web server, you apply security configurations in the tomcat-users.xml (By default, this document is loaded from $CATALINA_BASE/conf/ folder).
For more information on container configuration, see the Tomcat documentation.
The OpenEdge security configuration templates are available in the WEB-INF folder of the REST Management Agent or application after you install it and start your Web server.
You choose and apply the security model using the web application's web.xml configuration file. For more information, see Choosing and applying a security configuration.
For more information on the installation and location of the REST Management Agent, see the Installing and Configuring REST Management Agent. For instance, if you are using a Tomcat Web server, the configuration templates will be available at <tomcat-installation-directory>\webapps\oerm\WEB-INF.
Note: The Spring Security framework enables you to implement other types of authentication systems. For more information on implementing authentication systems, see the Spring Security framework documentation.