Common authentication mechanism for database clients
With a common security token to encapsulate user identity, OpenEdge employs the same basic user authentication mechanism for all OpenEdge database clients, including:
Database connections for ABL clients, SQL clients, and database utilities
Individual ABL sessions of all types
ABL applications of all configurations, including client-server, multi-tier, service-oriented (SOA), and software as a service (SaaS)
The available authentication features, however, depend on the OpenEdge components involved, the configuration of their security domains, and in the case of ABL sessions and applications, the design of the application authentication model. Authorization support also differs, with one authorization system for SQL clients and another for all other OpenEdge components.