Re: cimcli authentication loop

Kirk Augustin <[email protected]>
Newsgroups gmane.network.open-pegasus.general
Message-ID <[email protected]>
Try different variations.
For example, try it local instead of on a different host, try it without changing user and requiring login, etc.
There are just so many possible things going on, that it would help to work from the simplest way that works, slowly adding things.

 
Kirk & Trish Augustin
11821 NW McNamee Rd
Portland, OR 97231


________________________________
From: Devchandra Leishangthem <[email protected]>
To: [email protected]
Cc: [email protected]
Sent: Wednesday, August 17, 2011 11:29 PM
Subject: Re: cimcli authentication loop


Hi Tony 
cimcli seems to be working fine in my
dev env. 
What are the env variables set? 
Warm Regards
D.L. Meetei
IBM Systems &Technology Lab
6th Floor, EGL -D block
Bangalore, India 



From:      
 Tony Asleson <[email protected]> 
To:      
 [email protected] 
Date:      
 08/18/2011 03:54 AM 
Subject:    
   cimcli authentication
loop 
________________________________
 


Greetings,

This is my first exposure to CIM/WBEM and I have been experimenting with
the openpegasus library.  If I create a very simple client that does
nothing more than connects and enumerates classes on port 5988 (no ssl)
everything works.  If I attempt the same operation using cimcli with
the
following command:

./cimcli ec -v -d -n 'root/ontap' -l 192.168.2.25:5988 -u root -p xxxxxx

the command never returns.

Looking at data going across the socket shows that in my simple example
the client sends a request, which is rejected by the server
(Unauthorized) and the client responds by sending a request utilizing
basic authentication which succeeds and allows the operation to
complete.  Looking at the scenario where I use cimcli the client gets
caught in a loop sending a request and getting an Unauthorized response
every time.

The code in the method (Message* CIMClientRep::_doRequest) is where I am
stuck in a loop.  We repeatedly retrieve the response where
response->getCloseConnect() == true so we disconnect.  We then
reconnect
and send the request and start all over again.

So the simple example code I wrote which uses the CIMClient class
handles the unauthorized response by following up with the basic
authentication which succeeds.  How do I get this same authentication
behavior with cimcli?

Regards and many thanks,
Tony


stdout/stderr

$ ./cimcli ec -v -d  -n 'root/ontap' -l 192.168.2.25:5988 -u root
-p xxxxxx

namespace = root/ontap
role =
resultRole =
location = localhost:5988
filter =
queryLanguage = WQL
User = root
Password = xxxxxx
Output Format = mof
Command = ec
Connect to localhost port=5988 for User=root
EnumerateClasses Namespace= root/ontap, Class= , deepInheritance= false,
localOnly= true, includeQualifiers= true, includeClassOrigin= false

$ ./cimcli --version
Version 2.11.0
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.