My Oracle Support Banner

Config-Backend Has User 'Admin' Hardcoded Inside Script (Doc ID 1439849.1)

Last updated on NOVEMBER 15, 2017

Applies to:

Oracle Communications Calendar Server - Version 7.1 and later
Information in this document applies to any platform.

Goal


Setting:
* Comms Suite 7U2, no additional patches applied
* davserver deployed, with admin account named gfadmin instead of admin

Commands like davadmin config  will work with -u gfadmin, but not with -u admin.

However, configuration of calendar backends, using the (generated) config-backend script partly fails.

It seems config-backend, while attempting to populate the davserver, fails due to use of -u admin, which is hard-coded in the script.

See line 375 and 377 in config-backend: (default location: /opt/sun/comms/davserver/sbin)

375 $Cmd = "${DAVADMIN} backend create -u admin -n $backendid -j \"$jndiname\" -d \"$dbdir\""
376 } else {
377 $Cmd = "${DAVADMIN} backend create -u admin -n $backendid -j \"$jndiname\" -S $ashost -P $asport"


It's fairly easy to edit this script before deploying it, but is this a known issue?

Solution

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.