OEAG: Class not found error configuring Domain of type _oeusertable

stsclientutil fails with error 400 Bad Credentials when trying to authenticate with _oeusertable Domain configuration with auth provider _oeusertable returns error: ** 'OpenEdge.Security.DB.OEDBAuthProvider' was not found. (293)

Jun 9, 2022
Knowledge

Title

URL Name

Class-not-found-error-configuring-Domain-of-type-oeusertable

Article Number

000212567

Environment

Product: OpenEdge Version: 11.7.x,12.2.x OS: All supported platforms Other: OEAG

Question/Problem Description

Setting up a domain configuration on _oeusertable, returns error 400 Bad Credentials when trying to authenticate with stsclientutil.

oeauthserver.agent.log shows:
038832 039712 1 AS-4 ?:?:? -- ** 'OpenEdge.Security.DB.OEDBAuthProvider' was not found. (293)
038832 039712 1 AS-4 ?:?:? -- Cannot load class 'OpenEdge.Security.DB.OEDBAuthProvider' (16815)
038832 039712 1 AS-4 ?:?:? -- OpenEdge.Security.DB.OEDBAuthProvider Singleton object instantiation ended with an ERROR condition. (16819)

oeauthserver.log shows:
ERROR [thd-5] c.p.a.s.sts.OEDBUserDetailsImpl - Username load error for oeaguser re: Realm o4gl run-time error: com.progress.open4gl.RunTime4GLErrorException: ERROR condition: OpenEdge.Security.DB.OEDBAuthProvider Singleton object instantiation ended with an ERROR condition. (16819) (7211) (18930)

Steps to Reproduce

Clarifying Information

_oeusertable has been set as authProvider for domain in domains.json:

”authProvider” : “_oeusertable”,

The following mapping is present in sts-context.xml:

        <b:property name='authenticationProviders'>
            <b:map>
                ...
                <b:entry key='_oeusertable' value-ref='OEDBAuthProvider'></b:entry>
                ...
            </b:map>
        </b:property>

Error Message

Defect Number

OCTA-44337

Enhancement Number

Cause

The exact cause is not known at this time.

Resolution

Fixed version(s): OpenEdge 12.6

Workaround

Please follow these steps for blank domains:

In <OEAG install>/webapps/ROOT/WEB-INF/config/domains.json confirm that the domain is blank and enabled for authentication. For example:

"domains": [
{
   "name" : "",
"enabled" : true,
"description" : "Default domain",
"actions" : {
"authenticate" : {
   "enabled" : true,
   "options" : ""
},
"exchange" : {
   "enabled" : false,
   "options" : ""
},
"sso" : {
   "enabled" : false,
   "options" : ""
},
"refresh" : {
   "enabled" : false,
   "options" : ""
}
}

In <OEAG install>/conf/openedge.properties, make sure that the database with the users in it is connected with a logical name of STSDB. For example:

agentStartupParam=-T "${catalina.base}/temp" -db wrk122/dbusers -ld STSDB

In <OEAG install>/webapps/ROOT/WEB-INF/config/sts.properties, change the value of the sts.oedbrealm.user.realmClass property to be OpenEdge.Security.Provider.UserTableAuthProvider .
Restart the OEAG instance. For example:

tcman pasoestart -restart

If a named (non-blank) domain is used follow these steps:

Make sure that the domain is defined in both the OEAG client database (e.g. the database that connects to the OEAG instance) and the database that contains the users.
Follow the steps for the blank domain, but make sure that the domain name is not empty and that the -useFQUserIds switch is added to the actions.authenticate.options property in the domains.json file. This switch allows for multi-domain support. Once added, the OEAG will pass a fully qualified OpenEdge user ID to whichever authentication provider (“authProvider”) is configured. For example:

"domains": [
{
   "name" : "domain1",
"enabled" : true,
"description" : "Default domain",
"actions" : {
"authenticate" : {
   "enabled" : true,
   "options" : "-useFQUserIds"
},
"exchange" : {
   "enabled" : false,
   "options" : ""
},
"sso" : {
   "enabled" : false,
   "options" : ""
},
"refresh" : {
   "enabled" : false,
   "options" : ""
}
}

Add the domain name and its password to the <OEAG install>/webapps/ROOT/WEB-INF/config/domains.csv file, and generate the domains.keystore. For example:

gendomreg mydomainsks.csv domains.keystore

Note: The password is the Domain Access Code that was used when creating the domain in the OEAG client database.

Set the sts.oedbrealm.multiTenant property in <OEAG install>/webapps/ROOT/WEB-INF/config/sts.properties to true . This will allow usernames with ampersand '@'.
Restart the OEAG instance. For example:

tcman pasoestart -restart

Note:
The database logical name has to be STSDB.
STSDB can leave the allow bank user on to avoid specifying user credentials on agentStartupParam.

Notes

References to Other Documentation:
https://docs.progress.com/bundle/openedge-authentication-gateway/page/Configure-domains.html

Documentation bug OCTA-44338 has been logged to reflect which credential providers are supported.

Keyword Phrase

Last Modified Date

10/23/2023 12:07 PM

OEAG: Class not found error configuring Domain of type _oeusertable

Files(0)

Was this article helpful?

Was this article helpful?

OEAG: Class not found error configuring Domain of type _oeusertable

Information

Related Articles