Re: Problem with invoking a https based service
Hi Divakar, You don't have to set a userName parameter for https transport to work. If you have encrypted the server key using a password it should be given in the SSL_PASSPHRASE parameter. In addition, AFAIK, userName and password parameters are not at all used in axis2/c. HTH -Dumindu. divakar wrote: Hi All, I am facing some problems with invoking a https based .Net webservice using the axis2c client. I am getting Error code 2. It is giving error cannot find the password for user pbsgridworks\\administrator. How can i set the password to this. I am sending axis.xml ,my .c file and client_policy.xml file. Please check and give reply. Thanks Divakar - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Dumindu Pallewela http://blog.dumindu.com GPG ID: 0x9E131672 WSO2 | http://wso2.com | Oxygenating the Web Service Platform signature.asc Description: OpenPGP digital signature
Re: Problem with invoking a https based service
Hi, I commented user name from client_policy.xml . I is giving user name token notspcified error in log. I have one doubt why it is accessing service.xml from /usr/local/axis2c/services/sec_echo/service.xml. should it need for client. Thanks Divakar Dumindu Pallewela wrote: Hi Divakar, You don't have to set a userName parameter for https transport to work. If you have encrypted the server key using a password it should be given in the SSL_PASSPHRASE parameter. In addition, AFAIK, userName and password parameters are not at all used in axis2/c. HTH -Dumindu. divakar wrote: Hi All, I am facing some problems with invoking a https based .Net webservice using the axis2c client. I am getting Error code 2. It is giving error cannot find the password for user pbsgridworks\\administrator. How can i set the password to this. I am sending axis.xml ,my .c file and client_policy.xml file. Please check and give reply. Thanks Divakar - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Problem with invoking a https based service
Hi, You don't need to engage Ramprat to provide transport level security. This is why you get above error. Please remove the line module ref=rampart/ from the axis2.xml. If you are not planning for a message level protection, you don't need to have security polices in the services.xml or in the client_policy.xml. -Kaushalye divakar wrote: Hi, I commented user name from client_policy.xml . I is giving user name token notspcified error in log. I have one doubt why it is accessing service.xml from /usr/local/axis2c/services/sec_echo/service.xml. should it need for client. Thanks Divakar Dumindu Pallewela wrote: Hi Divakar, You don't have to set a userName parameter for https transport to work. If you have encrypted the server key using a password it should be given in the SSL_PASSPHRASE parameter. In addition, AFAIK, userName and password parameters are not at all used in axis2/c. HTH -Dumindu. divakar wrote: Hi All, I am facing some problems with invoking a https based .Net webservice using the axis2c client. I am getting Error code 2. It is giving error cannot find the password for user pbsgridworks\\administrator. How can i set the password to this. I am sending axis.xml ,my .c file and client_policy.xml file. Please check and give reply. Thanks Divakar - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- http://kaushalye.blogspot.com/ http://wso2.org/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Problem with invoking a https based service
Hi divakar,
In your axis2.xml you have commented the following and still engaged
rampart.
!--phase name=Security/--
Please uncomment it and try.
-Manjula.
On Fri, 2007-10-05 at 22:54 +0530, divakar wrote:
Hi All,
If I change axis2.xml like removing message out http
protocol and enable https it is giveing rampart security error. I am
sending axis2.xml and log.
Thanks
divakar
divakar wrote:
Manjula Peiris:
Hi,
I changed as you guided but still getting same. I
am attaching those files log and code please correct me. I think in
log file it showing http error.
thank
Divakar
Manjula Peiris wrote:
Hi Divakr,
Looking at your client code I have some problems. In Your client why are
you building the security header on your own? Because if you engage
rampart/c it will do all the necessary things reguarding soap message
security. IMHO following are things you need to do for your scenario.
1. Specify CA-Cert as you done in the client code.
2. Use the policy file as in the
rampart_src_dir/samples/secpolicy/scenario2/policy.xml 3. put it into
your client-repo
4. To set policy in your client code please refer to the client code at
rampart_src_dir/samples/client/sec_echo/echo.c
Thanks,
-Manjula.
On Tue, 2007-10-02 at 13:08 +0530, Dumindu Pallewela wrote:
Hi Divakar,
I could not find why it didn't work for you, according to the logs.
If you can build Axis2/C from source, you can test if the SSL
transport (i.e., without any SOAP stuff) is working using the
test/core/transport/http/test_http_transport.c test case.
Regards,
Dumindu.
divakar wrote:
Hi All,
I am facing some problems with invoking a https based .Net
webservice using the axis2c client. It is giving the error Error
code:
82 :: Input stream is NULL in msg_ctx in the client log file. I am
attaching the axis2.xml, client log file sample program for your
reference. Please check the same and let me know, if i am making any
mistakes in my client program.
Thanks Regards,
Murali Krishna K
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
#include axiom.h
#include axis2_util.h
#include axis2_const.h
#include axutil_env.h
#include axutil_log_default.h
#include axutil_error_default.h
#include axiom_output.h
#include axiom_xml_writer.h
#include stdio.h
#include axis2_client.h
#include axiom_soap.h
#include axiom_soap_envelope.h
#include rampart_context.h
#include rampart_username_token.h
#include axiom_soap_envelope.h
#include rampart_constants.h
#include neethi_util.h
#include neethi_policy.h
axiom_node_t *getHeaderNode(const axutil_env_t *env)
{
/* Namespace element declarations */
axiom_namespace_t *wsa_ns= NULL;
axiom_namespace_t *wsse_ns=NULL;
axiom_namespace_t *wsu_ns=NULL;
axiom_node_t *header_node=NULL,*to_node=NULL,*action_node=NULL;
axiom_element_t
*header_element=NULL,*to_element=NULL,*action_element=NULL;
axiom_text_t *om_text=NULL;
axiom_node_t *text_node=NULL;
axiom_node_t
*security_node=NULL,*usernametoken_node=NULL,*username_node=NULL,*password_node=NULL;
axiom_element_t
*security_element=NULL,*usernametoken_element=NULL,*username_element=NULL,*password_element=NULL;
axiom_attribute_t
*password_attribute=NULL,*body_attribute=NULL,*to_attribute=NULL;
/* Creating all the namespace elements */
wsa_ns=
axiom_namespace_create(env,http://www.w3.org/2005/08/addressing,wsa;);
wsse_ns=axiom_namespace_create(env,http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd,wsse;);
wsu_ns=axiom_namespace_create(env,http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd,wsu;);
/* SOAP Header element */
header_element=axiom_element_create(env,NULL,Header,NULL,header_node);
security_element=axiom_element_create(env,NULL,Security,wsse_ns,security_node);
/* Usernametoken element to pass the username, password to
HPCPwebservice */
usernametoken_element=axiom_element_create(env,NULL,UsernameToken,wsse_ns,usernametoken_node);
axiom_element_set_namespace(usernametoken_element,env,wsse_ns,usernametoken_node);
Re: Problem with invoking a https based service
Manjula Peiris:
Hi,
I changed as you guided but still getting same. I am
attaching those files log and code please correct me. I think in log
file it showing http error.
thank
Divakar
Manjula Peiris wrote:
Hi Divakr,
Looking at your client code I have some problems. In Your client why are
you building the security header on your own? Because if you engage
rampart/c it will do all the necessary things reguarding soap message
security. IMHO following are things you need to do for your scenario.
1. Specify CA-Cert as you done in the client code.
2. Use the policy file as in the
rampart_src_dir/samples/secpolicy/scenario2/policy.xml
3. put it into your client-repo
4. To set policy in your client code please refer to the client code at
rampart_src_dir/samples/client/sec_echo/echo.c
Thanks,
-Manjula.
On Tue, 2007-10-02 at 13:08 +0530, Dumindu Pallewela wrote:
Hi Divakar,
I could not find why it didn't work for you, according to the logs.
If you can build Axis2/C from source, you can test if the SSL
transport (i.e., without any SOAP stuff) is working using the
test/core/transport/http/test_http_transport.c test case.
Regards,
Dumindu.
divakar wrote:
Hi All,
I am facing some problems with invoking a https based .Net
webservice using the axis2c client. It is giving the error Error code:
82 :: Input stream is NULL in msg_ctx in the client log file. I am
attaching the axis2.xml, client log file sample program for your
reference. Please check the same and let me know, if i am making any
mistakes in my client program.
Thanks Regards,
Murali Krishna K
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
#include axiom.h
#include axis2_util.h
#include axis2_const.h
#include axutil_env.h
#include axutil_log_default.h
#include axutil_error_default.h
#include axiom_output.h
#include axiom_xml_writer.h
#include stdio.h
#include axis2_client.h
#include axiom_soap.h
#include axiom_soap_envelope.h
#include rampart_context.h
#include rampart_username_token.h
#include axiom_soap_envelope.h
#include rampart_constants.h
#include neethi_util.h
#include neethi_policy.h
axiom_node_t *getHeaderNode(const axutil_env_t *env)
{
/* Namespace element declarations */
axiom_namespace_t *wsa_ns= NULL;
axiom_namespace_t *wsse_ns=NULL;
axiom_namespace_t *wsu_ns=NULL;
axiom_node_t *header_node=NULL,*to_node=NULL,*action_node=NULL;
axiom_element_t *header_element=NULL,*to_element=NULL,*action_element=NULL;
axiom_text_t *om_text=NULL;
axiom_node_t *text_node=NULL;
axiom_node_t *security_node=NULL,*usernametoken_node=NULL,*username_node=NULL,*password_node=NULL;
axiom_element_t *security_element=NULL,*usernametoken_element=NULL,*username_element=NULL,*password_element=NULL;
axiom_attribute_t *password_attribute=NULL,*body_attribute=NULL,*to_attribute=NULL;
/* Creating all the namespace elements */
wsa_ns= axiom_namespace_create(env,http://www.w3.org/2005/08/addressing,wsa;);
wsse_ns=axiom_namespace_create(env,http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd,wsse;);
wsu_ns=axiom_namespace_create(env,http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd,wsu;);
/* SOAP Header element */
header_element=axiom_element_create(env,NULL,Header,NULL,header_node);
security_element=axiom_element_create(env,NULL,Security,wsse_ns,security_node);
/* Usernametoken element to pass the username, password to HPCPwebservice */
usernametoken_element=axiom_element_create(env,NULL,UsernameToken,wsse_ns,usernametoken_node);
axiom_element_set_namespace(usernametoken_element,env,wsse_ns,usernametoken_node);
username_element=axiom_element_create(env,NULL,Username,wsse_ns,username_node);
om_text=axiom_text_create(env,username_node,PBSGRIDWORKS\\administrator,text_node);
password_element=axiom_element_create(env,NULL,Password,wsse_ns,password_node);
password_attribute=axiom_attribute_create(env,Type,http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-username-token-profile-1.0#PasswordText,NULL);
axiom_element_add_attribute(password_element,env,password_attribute,password_node);
om_text=axiom_text_create(env,password_node,[EMAIL PROTECTED],text_node);
axiom_node_add_child(usernametoken_node,env,username_node);
axiom_node_add_child(usernametoken_node,env,password_node);
Re: Problem with invoking a https based service
Hi All,
If I change axis2.xml like removing message out http
protocol and enable https it is giveing rampart security error. I am
sending axis2.xml and log.
Thanks
divakar
divakar wrote:
Manjula Peiris:
Hi,
I changed as you guided but still getting same. I
am attaching those files log and code please correct me. I think in
log file it showing http error.
thank
Divakar
Manjula Peiris wrote:
Hi Divakr,
Looking at your client code I have some problems. In Your client why are
you building the security header on your own? Because if you engage
rampart/c it will do all the necessary things reguarding soap message
security. IMHO following are things you need to do for your scenario.
1. Specify CA-Cert as you done in the client code.
2. Use the policy file as in the
rampart_src_dir/samples/secpolicy/scenario2/policy.xml 3. put it into
your client-repo
4. To set policy in your client code please refer to the client code at
rampart_src_dir/samples/client/sec_echo/echo.c
Thanks,
-Manjula.
On Tue, 2007-10-02 at 13:08 +0530, Dumindu Pallewela wrote:
Hi Divakar,
I could not find why it didn't work for you, according to the logs.
If you can build Axis2/C from source, you can test if the SSL
transport (i.e., without any SOAP stuff) is working using the
test/core/transport/http/test_http_transport.c test case.
Regards,
Dumindu.
divakar wrote:
Hi All,
I am facing some problems with invoking a https based .Net
webservice using the axis2c client. It is giving the error Error
code:
82 :: Input stream is NULL in msg_ctx in the client log file. I am
attaching the axis2.xml, client log file sample program for your
reference. Please check the same and let me know, if i am making any
mistakes in my client program.
Thanks Regards,
Murali Krishna K
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
#include axiom.h
#include axis2_util.h
#include axis2_const.h
#include axutil_env.h
#include axutil_log_default.h
#include axutil_error_default.h
#include axiom_output.h
#include axiom_xml_writer.h
#include stdio.h
#include axis2_client.h
#include axiom_soap.h
#include axiom_soap_envelope.h
#include rampart_context.h
#include rampart_username_token.h
#include axiom_soap_envelope.h
#include rampart_constants.h
#include neethi_util.h
#include neethi_policy.h
axiom_node_t *getHeaderNode(const axutil_env_t *env)
{
/* Namespace element declarations */
axiom_namespace_t *wsa_ns= NULL;
axiom_namespace_t *wsse_ns=NULL;
axiom_namespace_t *wsu_ns=NULL;
axiom_node_t *header_node=NULL,*to_node=NULL,*action_node=NULL;
axiom_element_t
*header_element=NULL,*to_element=NULL,*action_element=NULL;
axiom_text_t *om_text=NULL;
axiom_node_t *text_node=NULL;
axiom_node_t
*security_node=NULL,*usernametoken_node=NULL,*username_node=NULL,*password_node=NULL;
axiom_element_t
*security_element=NULL,*usernametoken_element=NULL,*username_element=NULL,*password_element=NULL;
axiom_attribute_t
*password_attribute=NULL,*body_attribute=NULL,*to_attribute=NULL;
/* Creating all the namespace elements */
wsa_ns=
axiom_namespace_create(env,http://www.w3.org/2005/08/addressing,wsa;);
wsse_ns=axiom_namespace_create(env,http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd,wsse;);
wsu_ns=axiom_namespace_create(env,http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd,wsu;);
/* SOAP Header element */
header_element=axiom_element_create(env,NULL,Header,NULL,header_node);
security_element=axiom_element_create(env,NULL,Security,wsse_ns,security_node);
/* Usernametoken element to pass the username, password to
HPCPwebservice */
usernametoken_element=axiom_element_create(env,NULL,UsernameToken,wsse_ns,usernametoken_node);
axiom_element_set_namespace(usernametoken_element,env,wsse_ns,usernametoken_node);
username_element=axiom_element_create(env,NULL,Username,wsse_ns,username_node);
om_text=axiom_text_create(env,username_node,PBSGRIDWORKS\\administrator,text_node);
password_element=axiom_element_create(env,NULL,Password,wsse_ns,password_node);
password_attribute=axiom_attribute_create(env,Type,http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-username-token-profile-1.0#PasswordText,NULL);
Re: Problem with invoking a https based service
Divakar, divakar [EMAIL PROTECTED] writes: If I change axis2.xml like removing message out http protocol and enable https it is giveing rampart security error. I am sending axis2.xml and log. Why are you using rampart? Do you have WS-Security requirement? Or it is just HTTPS. thanks, Dinesh -- Dinesh Premalal http://xydinesh.wordpress.com/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Problem with invoking a https based service
Hi Divakar, I could not find why it didn't work for you, according to the logs. If you can build Axis2/C from source, you can test if the SSL transport (i.e., without any SOAP stuff) is working using the test/core/transport/http/test_http_transport.c test case. Regards, Dumindu. divakar wrote: Hi All, I am facing some problems with invoking a https based .Net webservice using the axis2c client. It is giving the error Error code: 82 :: Input stream is NULL in msg_ctx in the client log file. I am attaching the axis2.xml, client log file sample program for your reference. Please check the same and let me know, if i am making any mistakes in my client program. Thanks Regards, Murali Krishna K - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Dumindu Pallewela http://blog.dumindu.com GPG ID: 0x9E131672 WSO2 | http://wso2.com | Oxygenating the Web Service Platform signature.asc Description: OpenPGP digital signature
Re: Problem with invoking a https based service
Manjula Peiris wrote: Hi Divakar, You have not set the ca-cert in the axis2.xml. You need to set the following parameter in the axis2.xml. parameter name=SERVER_CERT/path/to/ca/certificate/parameter This is not necessary as the SERVER_CERT has been set in the client code. -Dumindu. signature.asc Description: OpenPGP digital signature
