BTW ... you can also simply construct a UsernameToken element and
insert the username and password as required and add it to the SOAP
header with the security header, by just using axiom :-)
-Ruchith
On Thu, Apr 23, 2009 at 4:23 AM, Ruchith Fernando
wrote:
> Hi Sanjay,
>
> I'm tr
hed/xmlsec-534045-patched.jar
On Wed, Apr 22, 2009 at 11:49 PM, Sanjay Gupta
wrote:
> Hi Ruchith,
> I am using verison 1.4.1.
> xmlsec-1.4.1.jar
>
> Thanks
> Sanjay
>
> -Original Message-
> From: Ruchith Fernando [mailto:ruchith.ferna...@gmail.com]
> Sent: Wednesday
e.java:1045)
> at
> org.apache.catalina.core.StandardEngine.start(StandardEngine.java:443)
> at
> org.apache.catalina.core.StandardService.start(StandardService.java:516)
> at
> org.apache.catalina.core.StandardServer.start(StandardServer.java:710)
>
k that talks
> about this solutions.
> Thanks
> Sanjay
>
> -Original Message-
> From: Ruchith Fernando [mailto:ruchith.ferna...@gmail.com]
> Sent: Thursday, April 16, 2009 4:31 PM
> To: axis-user@ws.apache.org
> Subject: Re: Securing Axis2 REST Style Services
>
Hi,
For the REST style calls you can use HTTPS + Basic Auth
Have a look at this [1] handler from WSO2 WSAS. This will simply add
the UsernameToken into the SOAP representation of the incoming REST
request, which will be processed by Rampart (which you have already
configured).
Thanks,
Ruchith
O
http://wso2.org/library/knowledge-base/run-rampart-samples-apache-tomcat
On Sun, Sep 14, 2008 at 8:32 AM, keith chapman <[EMAIL PROTECTED]> wrote:
> What the rampart samples will be doing is creating a service archive and
> dropping it into the services folder in the axis2 folder. One option will
Please have a look at "samples/policy/sample05" in the rampart
standard binary distribution.
You can subscribe and post Rampart/WS-Trust related issues to
[EMAIL PROTECTED]
Thanks,
Ruchith
On Fri, Sep 12, 2008 at 11:43 AM, Soyer, Muhammed A. <[EMAIL PROTECTED]> wrote:
> Hi,
>
> Does anybody kn
IMHO this is not possible right now with Rampart... and it doesn't
really take the actor/role into account at the moment.
Thanks,
Ruchith
On Fri, May 9, 2008 at 1:01 PM, Daniel Löf <[EMAIL PROTECTED]> wrote:
> Hi!
>
>
>
>
>
> I am using axis2 and Rampart 1.3 and I'm trying to construct a message
;m trying to do that from 3 days, but I met a lot of problems.
> Thank you.
> Mikelantonio
>
> 2008/5/16 Ruchith Fernando <[EMAIL PROTECTED]>:
>>
>> Please have a look at policy/sample04 in the rampart distro.
>>
>&g
Please have a look at policy/sample04 in the rampart distro.
You can try rampart-1.4-RC2 [1] with Axis2-1.4
Thanks,
Ruchith
1. http://people.apache.org/~nandana/rampart-1.4/RC2/dist/
On Thu, May 15, 2008 at 5:25 PM, Michelantonio Trizio
<[EMAIL PROTECTED]> wrote:
> Hi,
> I'd like to know how I
I haven't tried this but I think the following solution will work:
- first implement lifecycle management on the service [1]
- now in the "init" method you can get hold of the AxisService
instance and then you can engage the rampart module on it.
- Finally you can load the policy from a file as an
Why don't you use a static hook in the callback handler class itself?
Thanks,
Ruchith
On Fri, May 2, 2008 at 7:37 AM, Parham, Clinton <[EMAIL PROTECTED]> wrote:
>
>
>
>
> Hi,
>
>
>
> I'm new to Axis2 and still trying to get comfortable with the new
> architecture. I have engaged the Rampart modul
Fixed in the axis2 trunk [1] !
Thanks,
Ruchith
1. http://svn.apache.org/viewvc?rev=653698&view=rev
On Tue, May 6, 2008 at 12:54 PM, Ruchith Fernando
<[EMAIL PROTECTED]> wrote:
> The axis2.xml of the sample needs to be updated!
>
> Thanks,
> Ruchith
>
> On
The axis2.xml of the sample needs to be updated!
Thanks,
Ruchith
On Mon, May 5, 2008 at 6:44 PM, Savitsky, Alex
<[EMAIL PROTECTED]> wrote:
> Nandana,
>
> Thanks for your suggestion, it has resolved the issue.
>
> BTW, my axis2.xml was taken directly from the example java-first-jaxws
> (Axis2 1
Rampart nightly builds are available here :
http://people.apache.org/~ruchithf/rampart/SNAPSHOT/
These are compatible with the latest Axis2 nightly builds:
http://people.apache.org/dist/axis2/nightly/
Thanks,
Ruchith
On Sun, Apr 13, 2008 at 10:24 PM, Sukma Agung Verdianto
<[EMAIL PROTECTED]> w
#2 is sorted with
https://issues.apache.org/jira/browse/AXIS2-3711
Thanks,
Ruchith
On Mon, Apr 7, 2008 at 3:06 PM, Amila Suriarachchi
<[EMAIL PROTECTED]> wrote:
> hi dims,
> Sorry to mention this at this time.
> I had some test with the Rampart and found following issues.
>
> 1. org/apache/axis2
lem.
>
> Is it necessary to change something in my client side?
>
>
>
> Thanks,
>
>
>
> Nuria
>
>
>
>
> 2008/3/7, Ruchith Fernando <[EMAIL PROTECTED]>:
> > I believe there will be another release of Axiom close to the release
> > of Axis
I think this is probably due to this : [1] problem.
Can you please replace your xmlsec-.jar file with the
xmlsec-1.4.1.jar from here [2]
Thanks,
Ruchith
1. https://issues.apache.org/jira/browse/RAMPART-101
2. http://xml.apache.org/security/dist/java-library/xml-security-bin-1_4_1.zip
On Sat, Ma
t;
> Regards,
> Nuria
>
>
>
>
> 2008/3/7, Ruchith Fernando <[EMAIL PROTECTED]>:
> >
> >
> >
> > Hi Nuria,
> >
> > This is a bug in DOOM, the AXIOM DOM implementation.
> >
> > I just fixed this and checked it in. [1]
> &
Please specify "signaturePropFile" element in your "inflowSecurity" parameter :
Timestamp Encrypt
test.PasswordHandler
client.properties
..
Thanks,
Ruchith
On Wed, Feb 20, 2008 at 5:42 PM, Paul Ryan <[EMAIL PROTECTED]> wrote:
> Hi,
>
>
HI Sanjay,
Your services.xml looks fine ... but the only situation that Axis2 can
throw this error is when the services.xml does not specify the
messageReceiver. Please check the services.xml file in your deployed
service archive.
Thanks,
Ruchith
On Tue, Mar 4, 2008 at 2:31 PM, Sanjay Vivek
<[EM
Hi Nuria,
This is a bug in DOOM, the AXIOM DOM implementation.
I just fixed this and checked it in. [1]
Thanks,
Ruchith
1. http://svn.apache.org/viewvc?rev=634561&view=rev
On Thu, Mar 6, 2008 at 5:59 PM, Nuria Rodríguez García
<[EMAIL PROTECTED]> wrote:
> Hi,
> I can't add information in SOAPH
Hi,
Can you please specify the security operations you apply on the message?
Thanks,
Ruchith
On Thu, Mar 6, 2008 at 8:02 PM, Uygar Yüzsüren <[EMAIL PROTECTED]> wrote:
> Hi everyone,
>
> We have been developing a web service for domain registration with axis2
> version 1.2 and rampart security mo
IMHO we have to improve both Axis2 and Rampart if we are to support
policy alternatives.
A service can express a set of alternatives that it can handle and
right now we should be able to fix Rampart to support this.
However at the client side we should have some way of picking the
alternative. At
Hi Hardev,
Your messages exchanges sounds fine up to the point where the callback
handler accesses the STS to obtain the symm key. IMHO WS-Trust doesn't
provide a specific way to obtain a key at this point of a standard
WS-Trust exchange.
We have you use case implemented in a slightly different a
On Jan 4, 2008 10:14 PM, red dog <[EMAIL PROTECTED]> wrote:
> Hi everyone,
>
> Is there any resolution to this? I'm facing the same issue and I'm using
> Axis 2 and rampart module 1.3.
>
> If I just send a SOAP message with an empty security header my method gets
> called.
This is a bug in the par
Which version of Sandesha2 are you using?
Thanks,
Ruchith
On Jan 8, 2008 6:42 PM, Sanjay Vivek <[EMAIL PROTECTED]> wrote:
> Hi everyone,
>
> I'm attempting to call a simple Web Service (an Echo Service) that is
> protected by WS-Security UsernameToken. I'm using Axis2-1.3 and Rampart
> 1.3. Howev
Rampart should have an option for users to add custom tokens in.
Please file a JIRA.
https://issues.apache.org/jira/browse/RAMPART
Thanks,
Ruchith
On Jan 9, 2008 2:59 PM, <[EMAIL PROTECTED]> wrote:
> Hi all,
>
> i'm using axis2 1.3 with rampart 1.3 for ws-security.
> I have a runnig exsample wi
[EMAIL PROTECTED]
to subscribe : [EMAIL PROTECTED]
Please subscribe first and then post your messages.
Thanks,
Ruchith
On Jan 16, 2008 3:52 PM, Antonio Manuel Muñiz Martín
<[EMAIL PROTECTED]> wrote:
> Which is the adderss of Rampart list?
>
> 2008/1/15, Nandana Mihindukulasooriya <[EMAIL PROTE
On Jan 18, 2008 7:17 PM, Jose Luis Alba <[EMAIL PROTECTED]> wrote:
> Hi All,
>
> It's possible to encrypt a message using an embedded key (for symmetric
> encryption) and send that key using the transport key encryption?
I don't think we can do this in the context of WS-Sec* specifications.
Howev
You should be able to use a provider that has support for all required
algorithms.
I haven't used used WSS4J with any other and I get errors due to
missing algo implementations
when using the default Sun JCE impls.
Thanks,
Ruchith
On Jan 17, 2008 2:46 AM, George Stanchev <[EMAIL PROTECTED]> wrote
xs2/Rampart 1.1(.1).
Thanks,
Ruchith
>
> Thanks & Best Rgds,
> Niu
>
> -Original Message-
> From: Ruchith Fernando [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, January 08, 2008 9:17 AM
> To: axis-user@ws.apache.org
>
> Subject: Re: [Axis2 1.1.1] Security policy not
Yes ... you can move your configuration to policy based model to
overcome this issue as well.
Thanks,
Ruchith
On Jan 7, 2008 4:47 PM, Paul Fremantle <[EMAIL PROTECTED]> wrote:
> Ruchith
>
> Is it another fix to use the Policy-based model instead?
>
> Paul
>
>
> O
Hi,
This is a bug in the wss4j library and it occurs when you use the
parameter based configuration.
This can be patched by using another handler to check the
configuration and for security results.
Will post this solution shortly!
Thanks,
Ruchith
On Jan 7, 2008 12:35 PM, Niu <[EMAIL PROTECTED]>
;>
>
>
> class="org.apache.axis2.engine.InstanceDispatcher">
>
>
>
>
>
>
>
>
>
>
>
hs = pain.
>
> I renamed everything to wow.whatever and now I'm onto the .NET interop
> problems, which I will probably be posting about when I get really
> stuck.
>
> Thanks so much.
>
>
> On Dec 5, 2007 7:46 PM, Ruchith Fernando <[EMAIL PROTECTED]> wrote:
&g
Yep ... everything looks fine ... However I'm wondering whether you
have any other client_crypto.properties file in your classpath that
causes the wrong keystore to be picked where there's no key with alias
test123.
Therefore can you please rename the keystore file and the .properties
file and che
Hi,
Please send your services.xml file used in the service archive. Seems
like the you are missing the declaration of the policy namespace with
prefix "wsp" .
Thanks,
Ruchith
p.s. Please try not to cross post to all three axis-user, axis-dev and
rampart-dev lists.
Rajesh, Peter (CLAIMS, WIP) wr
Hi,
Please see my comments below:
On 11/2/07, Massimiliano Masi <[EMAIL PROTECTED]> wrote:
> Hi All,
>
> I'm very frustrated: I'm developing policies for getting a SAML 2 token
> from a WS-Trust STS implemented using Rahas.
>
> I've to put it in the wsse:Security. So I created the following polic
HI Folks,
I will be in San Jose on the 1st November and will be conducting a
training session on Apache Rampart[1]. Anyone interested? Register
here [2].
Also I'll be in Indianapolis for a week (10-17 Nov) if anybody's
interested we should be able to provide similar training there as
well. Those
Hi Murali,
The NPE was thrown because there was no SOAP header in the request SOAP
envelope. I just fixed this [1].
However, IMHO the way you have specified policy doesn't seem to correct
to me. An example where we use a SAML token to protect a message is
available with WSO2 WSAS [2] - sts-sample
Please see this :
http://wso2.org/library/240
Thanks,
Ruchith
On 8/31/07, Todd Allen <[EMAIL PROTECTED]> wrote:
> I need to implement user name/password authentication in an Axis2 1.1
> web service. Can someone point me to a useful set of samples or a
> good tutorial on Rampart and the user nam
This is the 1.3 release of Apache Rampart.
Apache Rampart 1.3 is a toolkit that provides implementations of the
WS-Sec* specifications for Apache Axis2 1.3, based on Apache WSS4J 1.5.3
and the Apache AXIOM-DOOM 1.2.5 implementations.
You can download the releases from:
http://www.apache.org/dyn/c
It is important that the policy used uses an "IssuedToken" assertion.
https://wso2.org/repos/wso2/trunk/wsas/java/modules/samples/sts-sample/conf/service.policy.xml
Now when RampartMessageData.KEY_CUSTOM_ISSUED_TOKEN property provides
an id of a token in the token store rampart will use that toke
Hi,
org.apache.axis2.wsdl.codegen.extension.ModulePolicyExtension has been
moved to the axis2-codegen.jar and this is not available in the
axis2.war. You will have to add the axis2-codegen-1.3.jar to the
WEB-INF/lib/ dir of the axis2.war to solve this issue.
All rampart samples with work without
Hi,
I did send a mail to the rampart-dev list [1] about the RC release :-)
and apologies about not updating the Rampart site[2].
We should move the axis2 rampart page into the rampart site and link
to the official site from the axis modules page.
Thanks,
Ruchith
1.
http://mail-archives.apache.
Hi Christina,
Rampart supports adding SAML Tokens to the security header in the
policy based implementation. You can see an example here :
http://marc.info/?l=axis-user&m=118665642802630&w=2
By the way note that this requires the service to express it
requirements in policy and this sample uses
Please try the rampart-1.29.mar available in Rampart-1.3-RC1 ...
IMPORTANT - rampart-1.29.mar is not an official release!
Thanks,
Ruchith
On 8/14/07, Alberto Patino <[EMAIL PROTECTED]> wrote:
> Hello!
>
> I'm trying to run the Rampart 1.2 samples with Axis3 but I got a
> service deployment error,
+1
Thanks,
Ruchith
On 8/10/07, Deepal jayasinghe <[EMAIL PROTECTED]> wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Hi all,
>
> I have uploaded Axis2 1.3 (take3) into my Apache home location [1]
> again . As a result of we found a few issues in 1.3 take2 I had to
> upload the artifa
Please see here :
http://marc.info/?l=axis-user&m=118671612624113&w=2
Thanks,
Ruchith
On 8/10/07, Ford, Jennifer M. <[EMAIL PROTECTED]> wrote:
> I've just discovered that digital signature validation appears to work
> with Tomcat 5.0.28, but not with Tomcat 5.5.23. Is this a known bug or
> shou
Argh ... seems like the certs expired on July 21st :(
Please create the client and service keystores as described here :
http://wso2.org/library/174
Thanks,
Ruchith
On 8/10/07, Pavan Madiraju <[EMAIL PROTECTED]> wrote:
> I am trying to get samples\policy\sample2 working but getting the following
Note that the "usage" flag of the
org.apache.ws.security.WSPasswordCallback instance passed into your
callback handler implementation is set to
WSPasswordCallback#USERNAME_TOKEN in the password digest case (since
we need to supply the password to compute the digest) and in the plain
text case it is
Please see this :
http://marc.info/?l=axis-user&m=118665642802630&w=2
Thanks,
Ruchith
On 7/25/07, Chris82KS <[EMAIL PROTECTED]> wrote:
>
> Hello @all!
>
> I want to use a service as security token provider. For this task I've
> chosen Rahas 1.1 in Axis2 1.1.
> Now I want to write a client which
Hi,
Can you please send the axis2.xml file you use with the client. This
error shows that the axis2.xml file picked is incorrect. Have you set
the "axis.xml" system property to point to any other axis2.xml file by
any chance?
Thanks,
Ruchith
On 7/28/07, Ingrid Alongi <[EMAIL PROTECTED]> wrote:
>
Hi,
You can use org.apache.rahas.client.STSClient to obtain a token from
the service. Please have a look at this sample client code [1].
You can see this sample in action in WSO2 WSAS 2.0 [2]
Thanks,
Ruchith
1.
http://wso2.org/repos/wso2/trunk/wsas/java/modules/samples/sts-sample/src/org/wso2/
Can you please post your client and service configuration?
Thanks,
Ruchith
p.s. Please *subscribe* by sending a mail to
[EMAIL PROTECTED] and post rampart related issues in
the rampart-dev@ list
On 8/4/07, Pavan Madiraju <[EMAIL PROTECTED]> wrote:
> I am trying to execute sample 4 from Rampart s
On 8/4/07, Pavan Madiraju <[EMAIL PROTECTED]> wrote:
> Thanks Dimuthu,
> Does anyone have example code for WS security using only digital signature ?
Please see policy/sample02 in the Rampart distro.
Thanks,
Ruchith
>
> Tried to modify the simple example ( Sample4) to implement one way security.
Hi Nagi,
Yes ... Rampart does support protecting messages with IssuedTokens.
But this is not available with the parameter based configuration.
Suport for issued tokens is available with the new policy based
configuration which uses WS-SecurityPolicy.
Right now we do not automatically obtain the t
eToken. ;-(
> -Original Message-
> From: Ruchith Fernando [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, July 10, 2007 10:59 AM
> To: axis-user@ws.apache.org
> Subject: Re: [Rampart] Ignore Timestamp and Addressing from client
>
> Hmm ... this is not possible with Rampart-1.0 st
t is
> not expected? I think this is what Stefan is saying also. Maybe this is
> against ws-security guidelines. I don't know. Thanks.
>
>> -Original Message-
>> From: Ruchith Fernando [mailto:[EMAIL PROTECTED]
>> Sent: Tuesday, July 10, 2007 5:37 AM
>
o configure Rampart to just ignore a
Timestamp since it is not expected? I think this is what Stefan is saying also. Maybe this is against
ws-security guidelines. I don't know. Thanks.
> -Original Message-----
> From: Ruchith Fernando [mailto:[EMAIL PROTECTED]
> Sent: Tuesd
The actions mismatch error occurs when you configure rampart to expect
security actions different to what the incoming message contains. When
you configure Rampart to process all security operations performed on
the message you will able to get rid of this error.
Thanks,
Ruchith
On 7/2/07, stlec
Hi,
On 7/9/07, [EMAIL PROTECTED]
<[EMAIL PROTECTED]> wrote:
Hi,
I didn't see any replies to the question below, so I started digging through
the rampart/wss4j code. I found a workaround that will allow me to hard-code
the private key into my client and server, and not have to have absolute pa
I agree we should not require the
"client.properties" entry.
Can you please try removing it?
Thanks,
Ruchith
On 7/6/07, [EMAIL PROTECTED]
<[EMAIL PROTECTED]> wrote:
Hi,
I'm trying to use Rampart to encrypt my message body using a symetric secret
key.
Sample 9, included with the Rampart dist
You can engage rampart per operation by adding the "" in the operation element of the services.xml. If the
operation dispatching happens before the message reaches the security
in handler then it should work.
Thanks,
Ruchith
On 7/6/07, Jorge Fernandez <[EMAIL PROTECTED]> wrote:
While this issue
Yes we will be releasing Rampart along with Axis2 as soon as 1.3 goes out!
Thanks,
Ruchith
On 7/2/07, stlecho <[EMAIL PROTECTED]> wrote:
Is this cleaning up phase also applicable for the Rampart module or only for
the Axis2 framework ?
In other words, can I vote for JIRA issues related t
Hi,
Can you please post the rampart configuration of the service? (policy
and services.xml)
Thanks,
Ruchith
On 6/16/07, Eduardo Muller <[EMAIL PROTECTED]> wrote:
With this configuration (see
http://www-usr.inf.ufsm.br/~muller/rampart.jpg ),
where the tag is replaced with ,
the web ser
Hi,
Seems like you are missing the wss4j jar in the classpath.
Please include all jars in the lib dir of the rampart-distro in the
classpath in addition to the jars in the axis2 bin distro.
Thanks,
Ruchith
On 6/12/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
Hi all,
I would like to use Ra
My guess is there's some missing config. Remember just engaging
rampart is not sufficient! One MUST provide the policy/configuration
for Rampart to enforce.
Thanks,
Ruchith
On 6/16/07, Glen Mazza <[EMAIL PROTECTED]> wrote:
That would appear, indeed, to be an alarmingly big security hole. We
ar
Hi Anthony,
Rampart-1.2 uses the same WS-Policy and WS-SecurityPolicy based config
that we introduced in RAmpart-1.1
Please look at the samples/policy dir in the rampart-bin distro.
Thanks,
Ruchith
On 6/18/07, Anthony Bull <[EMAIL PROTECTED]> wrote:
Hi, can anyone point me to some examples of
IMHO it involves a bit of changes to WSS4J core. I'll try to get this
fixed in the next release :-)
Thanks,
Ruchith
On 6/12/07, Deepal Jayasinghe <[EMAIL PROTECTED]> wrote:
Ruchith Fernando wrote:
> The rampart inflow handlers are invoked way before the message
>
The rampart inflow handlers are invoked way before the message
receiver. And the MessageContext.getCurrentContext() will only work
after the message receiver is invoked. Therefore calling
MessageContext.getCurrentContext() will not yield anything.
Also at the moment we cannot access the message c
Hi Hailong,
Please capture the req/response (using something like tcpmon[1]) and send!
Thanks,
Ruchith
[1] http://ws.apache.org/commons/tcpmon/
On 6/8/07, Wang, Hailong (NIH/CIT) [C] <[EMAIL PROTECTED]> wrote:
Hi Dims,
It's very urgent and I need your help. When I try to use UsernameToken,
S
You can download the release artifacts from :
http://www.apache.org/dyn/closer.cgi/ws/rampart/1_2
:-)
Thanks,
Ruchith
On 6/2/07, Ruchith Fernando <[EMAIL PROTECTED]> wrote:
This is the 1.2 release of Apache Rampart.
Apache Rampart 1.2 is a toolkit that provides implementations of the
This is the 1.2 release of Apache Rampart.
Apache Rampart 1.2 is a toolkit that provides implementations of the
WS-Sec* specifications for Apache Axis2 1.2, based on Apache WSS4J 1.5.2
and the Apache AXIOM-DOOM 1.2.4 implementations.
There are two main Apache Axis2 modules provided with this rele
Apache WSS4J Team is happy to announce the WSS4J-1.5.2 release.
You can download the releases from:
http://www.apache.org/dyn/closer.cgi/ws/wss4j/1_5_2
Apart from the binary and source distributions, We have an additional
ZIP file that contains other required JAR files to install and run WSS4J.
Hi Inder,
Axis2 uses AXIOM[1] as the object model and you can use the AXIOM API
[2] to navigate the XML nodes of a SOAP envelope. Also AXIOM has XPath
support [3].
Thanks,
Ruchith
[1] http://ws.apache.org/commons/axiom/
[2] http://ws.apache.org/commons/axiom/OMTutorial.html
[3] http://wso2.org/
Hi Snehil,
Please try the proposed Rampart-1.2 artifacts available here :
http://people.apache.org/~ruchithf/rampart/1_2/
Thanks,
Ruchith
On 5/30/07, snehil Brajpuriya <[EMAIL PROTECTED]> wrote:
Hi,
Referring to issue -
http://mail-archives.apache.org/mod_mbox/ws-wss4j-dev/200705.mbox/[EMAIL
Hi,
MessageContext.getCurrentMessageContext() will return the message
context only after the message reaches the message receiver. The
callback handler is called way before this and at this point this will
be null.
Thanks,
Ruchith
On 5/29/07, Wang, Hailong (NIH/CIT) [C] <[EMAIL PROTECTED]> wrot
Hi,
Rampart depends on WSS4J and we are working to get WSS4J 1.5.2 out as
ASAP. Also I'm working on the Rampart release build to package the
rampart release. Will make the Rampart SNAPSHOTs available (hopefully
today) and we can have 1.2 right after WSS4J release.
Thanks,
Ruchith
On 5/18/07, Da
Hi Mikhail,
Rampart only supports WS-SecurityPolicy 1.1 (July 2005) specification.
The policy you are using seems to be from an older version.
Thanks,
Ruchith
On 5/17/07, Paul Fremantle <[EMAIL PROTECTED]> wrote:
Mikhail
I've seen this error before and in my experience its because the
rampart
"IncludeToken/Once" is not handled properly in Rampart. Please file a bug [1]
Thanks,
Ruchith
[1] https://issues.apache.org/jira/browse/RAMPART
On 5/2/07, Nencho Lupanov <[EMAIL PROTECTED]> wrote:
Hi All ,
I am trying the rampart sample that comes with the distro.
I am going with sample01, on
It should throw a fault! provided that axis2 dispatched up to the
point where policy is applied.
Thanks,
Ruchith
On 5/1/07, Vibhor_Sharma <[EMAIL PROTECTED]> wrote:
Hi
The same service can be accessed by SOAP as well as REST interface. In
case i have enabled rampart secuirty on my servi
Hi,
On 5/8/07, Stefan Magnus Landrø <[EMAIL PROTECTED]> wrote:
Thanks for your reply. I believe I got a bit confused by a
callbackhandler that performs two totally different tasks.
I believe it would be a good idea to restructure some of the examples
in rampart to clarify this. In my opinion it
On 5/3/07, Stefan Magnus Landrø <[EMAIL PROTECTED]> wrote:
Hi,
I've been looking at the rampart examples recently, but there are a
couple things that I don't understand:
How do the sample services in the rampart distribution verify the password?
Why do the services.xml include a reference to a
Hi Vibhor,
On 4/28/07, Vibhor_Sharma <[EMAIL PROTECTED]> wrote:
Hi Ruchith
We are deploying the web services solution created by Axis2 1.1.1 and
security using rampart1.1.
The deployment comprises of the Apache Web server which receives the HTTP
requests and then routes the requests to t
Hi All,
I will be in Maryland, US in the second week of May. Is anybody
interested in attending tutorials on Apache Axis2 and Apache Rampart?
Both are 1/2 day programs.
This would be on Thursday the 10th of May.
Please drop me a note at [EMAIL PROTECTED] and let me know.
Thanks,
Ruchith
--
ww
Apologies for the delay in my response !
According to the scenario explained in the original post ... a web
service calls secured methods on the EJB. When the subject is
authenticated into the web service by Rampart using the callback
handler provided by the user ... a java.security.Principal in
Hi Donald,
Please attach the patches to the JIRA issues and make sure you grant
license to ASF for inclusion in ASF works.
Thanks,
Ruchith
On 3/29/07, donald yang <[EMAIL PROTECTED]> wrote:
Hi, I have fixed some bugs in axis2, but I don't know how to update the
source code repositry. Could you
At each operation invocation we can figure out the user that invoked
that operation [1]
Use MessageContext.getCurrentMessageContext() to obtain the message
context at the service.
Thanks,
Ruchith
[1] http://wso2.org/library/169
On 3/29/07, Jochen Zink <[EMAIL PROTECTED]> wrote:
Hi at all,
I
te the proper stub logic for inserting the WS-Security
headers?
When you codegen the stub will *not* contain any logic related to rampart.
Also, the code sample links are broken on the link you gave me.
The link is now fixed.
Thanks,
Ruchith
Thanks,
Ted
-Original Message-
From: R
Hi Ted,
Please see this :
http://www.wso2.org/library/240
Thanks,
Ruchith
On 3/28/07, Ted Jones <[EMAIL PROTECTED]> wrote:
I have an Axis2 1.1.1 ADB generated client stub that is instantiated using a
client axis2.xml config and pointing to a client repository that has the
rampart and address
a new Rampart release?
Thanks,
- Dennis
Ruchith Fernando wrote:
> Hi,
>
> There were changes to the Module/Handler interfaces in Axis2.
> Therefore Rampart-1.1 will not work with Axis2-1.2-*.
>
> The latest rampart trunk is available here :
>
> https://svn.apache.org/repos/
Hi,
There were changes to the Module/Handler interfaces in Axis2.
Therefore Rampart-1.1 will not work with Axis2-1.2-*.
The latest rampart trunk is available here :
https://svn.apache.org/repos/asf/webservices/rampart/trunk/java
Thanks,
Ruchith
On 3/27/07, Jorge Fernandez <[EMAIL PROTECTED]>
Hi,
Can you please send the message that caused this error?
Thanks,
Ruchith
On 3/24/07, Vibhor_Sharma <[EMAIL PROTECTED]> wrote:
Any reason why this is coming?
[java] org.apache.rampart.RampartException: Error in
extracting message properties
[java] at
org.apache.rampart.hand
Hi,
Can you please create a JIRA issue [1] on this and help us recreate
the issue. Please attach your service/client info to the issue.
Thanks,
Ruchith
[1] https://issues.apache.org/jira/browse/RAMPART
On 3/22/07, Jochen Zink <[EMAIL PROTECTED]> wrote:
Hello,
I have a little Webservice, whic
Rampart works with Axis2 not Axis 1.x.
Thanks,
Ruchith
On 3/22/07, John Kristian <[EMAIL PROTECTED]> wrote:
Rampart can do this, but not easily. Search this mailing list for
'Rampart' to find some problems.
http://ws.apache.org/axis2/modules/rampart/1_0/security-module.html
I sincerely hope s
Hi Vibhor,
Yes to all questions
:-)
Thanks,
Ruchith
On 3/21/07, Vibhor_Sharma <[EMAIL PROTECTED]> wrote:
Hi
We would be exposing our web services and utilize the methodology
described in the article
http://wso2.org/library/255
We want to distribute our certifcates having the public k
now.
Thanks
Vibhor
________
From: Ruchith Fernando [mailto:[EMAIL PROTECTED]
Sent: Tue 3/20/2007 7:43 PM
To: axis-user@ws.apache.org
Subject: Re: Issues with Rampart1.1 and Axis2 1.1.1 (Urgent)
Hi Vibhor,
The value of the "org.apache.ws.security.crypto.provider" proper
Hi,
On 3/21/07, Vibhor_Sharma <[EMAIL PROTECTED]> wrote:
Hi
Few questions about rampart
a) Is it mandatory to use BouncyCastle as the JCE provider for Rampart to
work? or we can plug in any provider with Rampart?
I have not tried any other JCE implementation that with Rampart/WSS4J
1 - 100 of 448 matches
Mail list logo
