In the OEHybrid realm, the OpenEdge AppServer-based single point of authentication (SPA) service authenticates users against the OpenEdge database to which the AppServer is connected, while the JDBC realm supports Business Process Server for groups, user attributes, and permissions.
You can create the SPA service by implementing the built-in Progress.Security.Realm.IHybridRealm interface. You must implement the interface as a SINGLETON class. An interface implementation OpenEdge.Security.Realm.HybridRealm.cls class file is available in your Progress OpenEdge installation directory at $DLC\src\samples\security\OpenEdge\Security\Realm. A utility class OpenEdge.Security.Util.Properties.cls for property file support is available in $DLC\src\samples\security\OpenEdge\Security\Util.
Before configuring the BP Server to use the SPA service, you must deploy the authentication service class file OpenEdge.Security.Realm.HybridRealm.cls and property file OpenEdge.Security.Util.Properties.cls on an OpenEdge AppServer running in state-free operating mode.
Note: By default, the bpsbroker defined for an AppServer is in state-free operating mode and the asbroker defined for an AppServer is in state-reset operating mode.
The reference implementation uses the _User table of the OpenEdge database to which the AppServer is connected to access an user's account information. For more information on configuring reference implementation and populating _User table of an OpenEdge database, see the OpenEdge Single Point of Authentication (SPAInstructions.pdf) document in your OpenEdge installation directory at $DLC\src\samples\security.
In addition, refer to the Progress Developer Studio for OpenEdge Guide for information on creating an OpenEdge database, and associating the database to an OpenEdge AppServer.