icegridadmin bugs

icegridadmin bugs
1、icegridadmin --Ice.Default.Locator=<proxy> could not work as manul write.
ice-3.1.0.pdf
36.19.1
icegridadmin --Ice.Default.Locator=<proxy>

test
$ icegridadmin --Ice.Default.Locator=DemoGrid/Locator:default -p 12000
could not work

$ icegridadmin --Ice.Default.Locator=config.grid
can work
IceGrid.InstanceName=DemoGrid

#
# The IceGrid locator proxy.
#
Ice.Default.Locator=DemoGrid/Locator:default -p 12000

#
# Trace properties.
#
IceGrid.Node.Trace.Activator=1
IceGrid.Node.Trace.Patch=1
#IceGrid.Node.Trace.Adapter=2
#IceGrid.Node.Trace.Server=3

2、icegridadmin can access registry without certify

gridregistry config as

IceGrid.InstanceName=DemoGrid

#
# The IceGrid locator proxy.
#
Ice.Default.Locator=DemoGrid/Locator:default -p 12000

#
# IceGrid registry configuration.
#
IceGrid.Registry.Client.Endpoints=default -p 12000
IceGrid.Registry.Server.Endpoints=default
IceGrid.Registry.Internal.Endpoints=default
IceGrid.Registry.Admin.Endpoints=default
IceGrid.Registry.Data=D:/demogrid/db/registry
#IceGrid.Registry.PermissionsVerifier=DemoGrid/NullPermissionsVerifier
#IceGrid.Registry.AdminPermissionsVerifier=DemoGrid/NullPermissionsVerifier
IceGrid.Registry.CryptPasswords=D:/demogrid/certs/passwords
IceGrid.Registry.AdminCryptPasswords=D:/demogrid/certs/passwords


use IceGrid.AdminGUI to admin grid should input correct password before admin,this is correct way.

however icegridadmin could admin without certify
it could listnodes,and servers,even start,stop server
icegridadmin use config as below

#
# The IceGrid locator proxy.
#
Ice.Default.Locator=DemoGrid/Locator:default -p 12000

#
# Trace properties.
#
IceGrid.Node.Trace.Activator=1
IceGrid.Node.Trace.Patch=1
#IceGrid.Node.Trace.Adapter=2
#IceGrid.Node.Trace.Server=3

Comments

  • benoitbenoit Rennes, FranceBenoit FoucherOrganization: ZeroC, Inc.Project: IceAdministrators, ZeroC Staff ZeroC Staff
    Hi,

    On the command line, you need to specify the proxy within quotes, try the folllowing instead:
    $ icegridadmin --Ice.Default.Locator="DemoGrid/Locator:default -p 12000"

    As for your second point, you're not supposed to let anyone access the IceGrid.Registry.Admin endpoints. You should secure and restrict access to these endpoints using IceSSL.

    I agree that the "icegridadmin" tool could also provide username/password authentication like the IceGrid GUI (to provide administrative access to the registry through the IceGrid.Registry.Client endpoints), we'll add this to our TODO list.

    Cheers,
    Benoit.
  • hellocyfhellocyf Member
    thanks reply

    I feel confused that gridadmingui should authentication before admin grids
    with property set as
    IceGrid.Registry.Admin.Endpoints=default(it si not ssl endpoint)

    I thinks that with set the property
    (IceGrid.Registry.AdminCryptPasswords=D:/demogrid/certs/passwords)
    IceRegistry server will reject adminclients to create adminsession untill be certified.
    so I think Icegridnode should modify at first.
  • benoitbenoit Rennes, FranceBenoit FoucherOrganization: ZeroC, Inc.Project: IceAdministrators, ZeroC Staff ZeroC Staff
    Hi,

    The difference between the IceGrid GUI and the icegridadmin tool is that the GUI needs to establish a session with the registry. Authentication is required for the GUI because it establishes a session through the client endpoints (configured with the IceGrid.Registry.Client.Endpoints property) whereas the icegridadmin tool is accessing the administrative interface through the administrative endpoints (configued with the IceGrid.Registry.Admin.Endpoints property). I understand this might be confusing, we'll look into improving this in the next releases!

    Cheers,
    Benoit.
  • hellocyfhellocyf Member
    o yea

    ok ,waiting for next release!
Sign In or Register to comment.