Hi , 
can you help me to find the problem, 
it can be the java class that create a custom jUDDI Authentificator because
I have this problem, i don't know .

the error:
?xml versionfiltered="1.0" encoding="UTF-8"?><soapenv:Envelope
xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/";
xmlns:xsd="http://www.w3.org/2001/XMLSchema";
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";>
 <soapenv:Body>
  <soapenv:Fault>
   <faultcode
xmlns:ns1="http://xml.apache.org/axis/";>ns1:Server.generalException</faultcode>
   <faultstring></faultstring>
   <faultactor></faultactor>
   <detail/>
  </soapenv:Fault>
 </soapenv:Body>
</soapenv:Envelope>
 


 Merci d'avance





khiz wrote:
> 
> thank you for quick reply,
> i checked it: get_authToken works even if cred is not supplied. 
> pubid shall be valid pubid from publisher table.
> bye.
> 
> avinh wrote:
>> 
>> khiz,
>> 
>> I believe the "cred" field in the request is typically the password for 
>> the user as I have seen in some of their other sql statements. However, 
>> the PUBLISHER table that was created using their provided sql statement 
>> has NO column for the password field, so I don't think the "cred" field 
>> is being used at this time in their request - we must keep in mind that 
>> the "console" is a beta product and it may not have everything they want 
>> implemented in it yet.
>> 
>> By credential I mean whatever user that you have created using their 
>> supplied sql statement (see example below). In their example, the userID 
>> is "jdoe" (PUBLISHER_NAME=John Doe). In your case, it looks like your 
>> userID is "pubid1". Notice below that the sql statement used to insert 
>> the user into the jUDDI database does have fields such as IS_ENABLED and 
>> IS_ADMIN but nothing for the password hence I don't think the "cred" 
>> field is being checked/used. If you create another user and insert that 
>> user ID into the "userID" field of the request, it would also work 
>> because that new user ID will also be present in the jUDDI database.
>> 
>> INSERT INTO PUBLISHER 
>> (PUBLISHER_ID,PUBLISHER_NAME,EMAIL_ADDRESS,IS_ENABLED,IS_ADMIN)
>> VALUES ('jdoe','John Doe','[EMAIL PROTECTED]','true','true');
>> 
>> Go into mysql and run the following sql statements and all of your users 
>> listed in the PUBLISHER table will be displayed:
>> 
>> mysql> use juddi;
>> mysql> select * from PUBLISHER;
>> 
>> You should get something like the following output:
>> 
>> +------------------+--------------------------------------+----------------------+-------------+----------------+
>>  
>> 
>> | PUBLISHER_ID | PUBLISHER_NAME                        | EMAIL_ADDRESS  
>> | IS_ADMIN | IS_ENABLED |
>> +------------------+--------------------------------------+----------------------+-------------+----------------+
>>  
>> 
>> | jdoe                     | John Doe                                   
>>         | [EMAIL PROTECTED] | true             | true                 
>> |
>> | pubid1                 | Whatever you have put here                | 
>> [EMAIL PROTECTED]      | true             | true                  |
>> +------------------+--------------------------------------+-----------------------+------------+----------------+
>>  
>> 
>> 
>> Alan
>> 
>> khiz wrote:
>>> hi alan
>>>
>>> thanks for the help, i followed the link its working fine now. 
>>>
>>> i still have a doubt 
>>>
>>>  <get_authToken generic="2.0" xmlns="urn:uddi-org:api_v2" 
>>>       userID="pubid1" 
>>>       cred="***"/>
>>>
>>> what shall i specify in the place of cred="***", what doset it mean by
>>> credentials.
>>>
>>> what do you mean by
>>>
>>> You'll have to change the credential accordingly with your "publisher"
>>> information ?
>>>
>>> thank you again
>>> bye.
>>>
>>>   
>> 
>> 
>> 
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [EMAIL PROTECTED]
>> For additional commands, e-mail: [EMAIL PROTECTED]
>> 
>> 
>> 
> 
> 

-- 
View this message in context: 
http://www.nabble.com/get_authToken-problem-tf1986179.html#a6772654
Sent from the jUDDI - User mailing list archive at Nabble.com.


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to