Cannot specify externalAuth true and a proxy user.

[APop123]

1. What versions are you using?

>     process.platform
'win32'
>     process.version
'v18.12.1'
>     process.arch
'x64'
>     require('oracledb').versionString
'6.2.0'
>     require('oracledb').oracleClientVersionString
undefined

Server version unrelated - error ocurs before connection.

2. Describe the problem

Following example 4 from https://blogs.oracle.com/opal/post/external-and-proxy-connection-syntax-examples-for-node-oracledb.

With externalAuth true and proxy user set results in the error:

Error: NJS-136: user name and password cannot be set when using external authentication

Is there any way to use external auth and proxy user with current version of the library?

4. Include a runnable Node.js script that shows the problem.

const oracledb = require('oracledb');

async function run() {
    oracledb.initOracleClient();

    await oracledb.getConnection({
        connectString: 'db.example.com:1521/myservice',
        externalAuth: true,
        user: '[myproxyuser]'
    });
}

run()

[cjbj]

Are you sure you're using Thick mode? NJS-136 is shown in Thin mode with your testcase when I remove the initOracleClient() call. This particular message seems like a buglet to me - I would have expected NJS-089: External Authentication is not supported by node-oracledb in Thin mode

[APop123]

Hi, yes definitely in thick mode (oracledb.thin is false). The issue is caused by this bit of _verifyOptions:

node-oracledb/lib/oracledb.js

Lines 500 to 503 in 39db941

	// Check external Auth config
	if (outOptions.token === undefined && outOptions.externalAuth && (outOptions.user || outOptions.password)) {
	errors.throwErr(errors.ERR_WRONG_CRED_FOR_EXTAUTH);
	}

Nothing here checks for the valid case of a proxy user and will error whenever user is set.

If I comment out this validation my code will connect to the DB and I can see my proxy user is set by checking sys_context('USERENV', 'PROXY_USER').

[cjbj]

Sounds like a regression to me.

[sharadraju]

The patch for this issue has been added here. It will be fixed in the 6.3 release.

[sharadraju]

This has been fixed as part of the 6.3 release.