Connecting to OD base server from Open Deploy Admin GUI server

Hello All,

We are having issues connecting to OD base server from OD base and OD Admin GUI server.

1.We have installed 6.0.2 OD base and OD Admin GUI in machineA
2.We have installed TS6.5 and 6.0.2 OD base in machineB
3. we have created OD bootstarp users in machineA and machineB

when i am trying to connect from machineA admin gui to machineB od bootstrap user getting following error
Failed to authenticate user.Invalid username/password combination. machineA\odadmin

Please let us know if anything is missing here.

ENV: Windows SP2, OD6.0.2

Thanks

Find more posts tagged with

Comments

moonkhanna

Why are you trying to authenticate yourself as machineA\odadmin .. Shouldnt you be uising machineB\odadmin? Please post your deploy.cfg of machine B

ccpro

thanks for quick reply, i am able to login using machineB\odadmin and trying to login with machineA\odadmin. all our users login into OD Admin GUI server as a domain users from server machineA

Ex: user name: domain\userid
Password: domain password
Server: machineA
Role: user/admin

Thanks,
------

#
# deploy.cfg
#
# This deploy configuration file is a Java property file and must
# be named deploy.cfg.
# It is read by the OpenDeploy server during startup.
#
# Unless otherwise specified, each configuration property is public,
# has a case sensitive name, has a case insensitive value,
# and is stripped of leading and trailing whitespace during use.
#

#--- The server config file name. Case sensitive.
#
# The server config file must be located in OpenDeploy
# home's etc directory. Only the file name is specified here.
#
# This property is REQUIRED.
#
# Example: for a OD base: Deploy.serverConfig: odbase.xml
# Example: for a OD receiver: Deploy.serverConfig: odrcvr.xml
#
Deploy.serverConfig: odbase.xml

#--- The server nodes file. Case sensitive.
#
# The server nodes file must be located in OpenDeploy
# home's etc directory. Only the file name is specified here.
#
# This property is REQUIRED.
#
# Example: Deploy.serverNodesConfig: odnodes.xml
#
Deploy.serverNodesConfig: odnodes.xml

#--- The bootstrap user name. Case insensitive.
#
# Whenever the Open Deploy server (base or receiver) starts up,
# it will add the bootstrap user specified here to the OD server's
# od-admin role database.
#
# The bootstrap user is usually the first user you use to login
# to the OD Admin GUI so you can create other users.
#
# The bootstrap user *MUST* be a valid od-admin role user
# on the Operations Server that is servicing this OD server.
# The Operation server performs the authentication check when
# a user logs into the OD Admin GUI.
# Note that the Operating System platform of the
# Operation Server and the OD Server can be different.
#
# For a Windows Operations Server, the format is:
#
# domain-name\\user-name
#
# Example: Deploy.bootStrapUserName: FINANCE\\john
# where FINANCE is the user's domain or workgroup,
# john is the user name
#
# For a Unix Operations Server, the format is:
#
# user-name
#
# Example: Deploy.bootStrapUserName: john
# where john is the user name
#
# In addition to the bootstrap user specified here, the OD server
# automatically adds two other default bootstrap users:
#
# \\Administrator
# root
#
# This property is OPTIONAL.
# To comment it out, place a # at the beginning of the line.
#

Deploy.bootStrapUserName: machineB\\odadmin

#--- Allow default bootstrap users. Case insensitive.
#
# When the OpenDeploy server (base or receiver) starts up
# and there is no od-admin role file /db/od-admin,
# OpenDeploy automatically adds the following default bootstrap
# users to the od-admin role:
#
# \Administrator
# root
#
# If you prefer OpenDeploy server not to create these default
# bootstrap users, you can do so by setting this property to "no".
#
# The od-admin role file doesn't exist when it is the very
# first time OpenDeploy is starting up or when the file was
# manually removed.
#
# If the od-admin role file already exists, setting this
# property to "no" will cause OpenDeploy server at startup time
# to lookup the default bootstrap users and delete them if they exist.
#
# The valid input values are "yes" or "no". The default is "yes".
# If the value specified is not "yes" or "no", the default
# setting of "yes" will be used.
#
# This property is OPTIONAL.
# To comment it out, place a # at the beginning of the line.
#
#Deploy.allowDefaultBootStrapUser: yes

#--- The RMI Connection ports.
#
# OpenDeploy requires 2 sets of RMI connection ports.
# One set is for server administration.
# Thes other set is for event reporting.
#
# Within each set of RMI connection ports, each port can be a
# unique port number or they can share the same port number(s).
# This implies OpenDeploy requires a minimum of 2 different
# connection port numbers for RMI, one for each set.
#
# Valid port range is 1 - 65535 where 1-1024 are considered
# to be reserved ports by the Operating System. Also, 0 can be used
# to allow the Operating System to choose any available port.
#
# The default value for the server administration RMI connection ports:
# Deploy.rmiConnectionPort1: 24071
# Deploy.rmiConnectionPort2: 24071
# Deploy.rmiConnectionPort3: 24071
# Deploy.rmiConnectionPort4: 24071
# Deploy.rmiConnectionPort5: 24071
# Deploy.rmiConnectionPort6: 24071
# Deploy.rmiConnectionPort7: 24071
#
# The default values for the event reporting RMI connection ports:
# Deploy.rmiConnectionPort8: 24078
# Deploy.rmiConnectionPort9: 24078
# Deploy.rmiConnectionPort10: 24078
# Deploy.rmiConnectionPort11: 24078
# Deploy.rmiConnectionPort12: 24078
# Deploy.rmiConnectionPort13: 24078
# Deploy.rmiConnectionPort14: 24078
# Deploy.rmiConnectionPort15: 24078
#
# In case any of the default ports are in use by other processes,
# you can modify all or any of these properties to your own
# port numbers.
#
# If a non-integer port number or a port number outside of the
# valid range is specified, OpenDeploy will use the default value
# for that port.
#
# If a duplicate port is specified between the 2 sets of ports,
# OpenDeploy will not use any of the specified ports and will
# use all default ports instead.
#
# These properties are OPTIONAL.
# Remove # at the beginning of the line to make property active.
#

#-- server administration RMI connection ports:
Deploy.rmiConnectionPort1: 24071
Deploy.rmiConnectionPort2: 24071
Deploy.rmiConnectionPort3: 24071
Deploy.rmiConnectionPort4: 24071
Deploy.rmiConnectionPort5: 24071
Deploy.rmiConnectionPort6: 24071
Deploy.rmiConnectionPort7: 24071
#
#-- event reporting RMI connection ports:
Deploy.rmiConnectionPort8: 24078
Deploy.rmiConnectionPort9: 24078
Deploy.rmiConnectionPort10: 24078
Deploy.rmiConnectionPort11: 24078
Deploy.rmiConnectionPort12: 24078
Deploy.rmiConnectionPort13: 24078
Deploy.rmiConnectionPort14: 24078
Deploy.rmiConnectionPort15: 24078

#--- The RMI server binding IP Address or hostname. Case sensitive.
#
# The RMI server binding IP address or hostname is used to specify
# a specific IP address or hostname OpenDeploy should use
# in setting up its RMI services.
# The RMI services are used for servicing the OpenDeploy
# Administration server and for supporting event reporting.
#
# This property is useful when the host where the OpenDeploy
# base/receiver server is installed has multiple hostnames/IP addresses.
# This property allows the user to tell the OpenDeploy base/receiver
# server which hostname/IP address it should use to communicate to the
# OpenDeploy Administration server.
#
# Please make sure the value specified is correct.
# This value is passed to Java RMI as a property. The result
# is unpredictable when the value is invalid.
#
# If this property is not specified, by default, OpenDeploy will use
# the local hostname.
#
# This property is OPTIONAL.
# Remove # at the beginning of the line to make property active.
#
# Examples:
# Deploy.rmiServerBind: 10.234.567.890
# Deploy.rmiServerBind: VWDTUA10
#
#Deploy.rmiServerBind: VWDTUA10

#--- The RMI server port number.
#
# The RMI server port number is used to specify
# a specific TCP port number that OpenDeploy should use
# in setting up its RMI registry service.
# The RMI registry is used for servicing the OpenDeploy
# Administration server and for supporting event reporting.
#
# Please make sure the value specified is correct.
#
# If this property is not specified, by default, OpenDeploy will use
# port 9173.
#
# This property is OPTIONAL.
# Remove # at the beginning of the line to make property active.
#
# Examples:
# Deploy.rmiServerPort: 9173
#
Deploy.rmiServerPort: 9173

#--- The CLT Proxy Options
#
# The CLT Proxy is a socket listener that by default will
# bind on localhost port 3434 and only allow localhost requests.
# The following options can be used to customize operation.
#
# Deploy.cltProxyEnable is used to enable/disable the proxy
# values: y/n
# Deploy.cltProxyPort is used to specify a port to use
# values: numeric port
# Deploy.cltProxyHost is used to specify address that listener will bind on
# values: dot-notation or long/short hostname
# For localhost, use "localhost"
# Deploy.cltProxyAllowedHost is used to specify comma delimited list of
# allowed remote hosts
# values: dot-notation or long/short hostname
# For localhost, use "localhost"
#
# These properties are OPTIONAL.
# Remove # at the beginning of the line to make property active.
#
Deploy.cltProxyEnable: y
Deploy.cltProxyPort: 3434
Deploy.cltProxyHost: localhost
Deploy.cltProxyAllowedHost: machineB, localhost, machineA

#--- The key file for access control. Case sensitive.
#
# The key file for access control must be located in
# OpenDeploy home etc directory. Only the file name is specified here.
#
# This key file is used to control which OpenDeploy
# Admin server can access this OpenDeploy server.
#
# Each OpenDeploy Admin server is configured to
# use a specific ContentServices Foundation (CSF) Access Service
# for authenicating users at login time.
# The CSF Access Service uses a key file which is located
# in /etc directory. The key file
# is unique to the specific Access Service.
#
# For added security, it is possible to do the following:
# In order for the OpenDeploy Admin Server to access
# this OpenDeploy server, the key file from the Access Service
# the OpenDeploy Admin Server is configured to use must be copied
# into the OpenDeploy server etc directory (/etc).
# The name of the key file can be different between the
# Access Service and OpenDeploy server but the content
# must be the same.
#
# The above always applies to OpenDeploy Web Service clients.
# Each OpenDeploy Web Service client for this OpenDeploy
# server must authenicate with the Access Service whose
# key file is same as this OpenDeploy server.
#
# Deploy.accessKeyFile:
#
# This property is use to tell OpenDeploy the name of the
# key file in /etc.
# There can only be 1 key file specified.
# Default is passphrase.
#
# Deploy.useAccessKeyFileForAdmin:
#
# OpenDeploy Web Service always requires a key file in OpenDeploy.
# It is possible to configure the OpenDeploy server to not
# require the usage of a key file for OpenDeploy Admin accesses.
# This property is used to do this. Valid values:
# n = not require a key file for OpenDeploy Admin accesses
# y = require a key file for OpenDeploy accesses
# Default is n.
#
# These properties are OPTIONAL. Examples:
#
# Deploy.useAccessKeyFileForAdmin: n
# Deploy.accessKeyFile: passphrase
#
Deploy.useAccessKeyFileForAdmin: n
Deploy.accessKeyFile: passphrase

#

ccpro

i am trying to setup user access from machineA(TS and OD base server)

Thanks

Adam Stoller

Are you using local-server accounts (machineA\odadmin, machineB\odadmin) or domain accounts (DOMAIN\odadmin)

You should be using domain accounts if you want to be able to authenticate on both machineA and machineB - otherwise you can only authenticate with the actual machine's account.

If you make sure you specify a domain account in the deploy.cfg on both servers and restart the OD service on both servers, you should be able to access both servers through the OD Admin GUI (there might be another step, I rarely use the GUI)

ccpro

Thanks for your reply

we are using domain accounts only and trying to setup domain accounts from machineA(TS and OD base) on machineB(OD Admin and OD base).

current dev env has same setup and working good.

we are trying to create stand by server setup in different data center location, then we are seeing above issues.

any thoughts?

ccpro

deploy.cfg has both users

machineA\\odadmin
machineB\\odadmin

moonkhanna

deploy.cfg has both users

machineA\\odadmin
machineB\\odadmin

ccpro - this does not work this way. Machine A and Machine B are not domain names. Also none of them is trusted by the other.. As suggested above, use an acceptable domain name if you want to use the same user on both servers.. for eg. domain1\user 1. Remember the domain should be a trusted domain for both the servers

ccpro

thanks for reply munish !!

do we need to configure any settings for access domain1\user1 from OD Admin GUI and OD base server as another OD base server.

machineA: TS and OD base server
machineB: OD GUI and OD base server

1.we are able to login using machineB

ex: User Name: domain1\user1
Password: domain password
Server: machineB
Role: admin

2.we are unable to login using machineA

ex: User Name: domain1\user1
Password: domain password
Server: machineA
Role: admin

how can we make it work step2?

Thanks in advance...

sample.zip