: Ruchith Fernando [mailto:ruchith.ferna...@gmail.com]
Sent: Wednesday, January 30, 2013 8:33 AM
To: java-dev@axis.apache.org
Subject: Re: Rampart STS Username service not returning password in callback
On Jan 30, 2013 9:05 AM, "Ruchith Fernando"
wrote:
>
> Hi Brian,
>
> On
On Jan 30, 2013 9:05 AM, "Ruchith Fernando"
wrote:
>
> Hi Brian,
>
> On Wed, Jan 30, 2013 at 8:44 AM, Brian Reinhold
> wrote:
> > Interesting! I will need to look at these
> >
> > What I did instead was to change the UsernameTokenValidator.java file in
> > WSS4J. In that file when the callback wa
Hi Brian,
On Wed, Jan 30, 2013 at 8:44 AM, Brian Reinhold
wrote:
> Interesting! I will need to look at these
>
> What I did instead was to change the UsernameTokenValidator.java file in
> WSS4J. In that file when the callback was being created they simply placed
> null for the password. I removed
: Ruchith Fernando [mailto:ruchith.ferna...@gmail.com]
Sent: Wednesday, January 30, 2013 8:37 AM
To: java-dev@axis.apache.org
Subject: Re: Rampart STS Username service not returning password in callback
Hi Brian,
Please see the following two changes:
http://svn.apache.org/viewvc?view=revision
uary 30, 2013 1:34 AM
> To: java-dev@axis.apache.org
> Subject: Re: Rampart STS Username service not returning password in callback
>
> This issue is fixed in rampart trunk now.
> With this fix the callback instance contains the incoming password for the
> user
@axis.apache.org
Subject: Re: Rampart STS Username service not returning password in callback
This issue is fixed in rampart trunk now.
With this fix the callback instance contains the incoming password for the
user to validate as required. Callback usage is set to
WSPasswordCallback.USERNAME_TOKEN.
Thanks
1_6_4/src/main/java/org/apache/ws/security/validate/UsernameTokenValidator.java
>
>
> On Mon, Jan 21, 2013 at 6:59 AM, Martin Gainty wrote:
>>
>>
>>
>>
>> From: brianreinh...@lampreynetworks.com
>> To: java-dev@axis.apache.org
>
/UsernameTokenValidator.java
On Mon, Jan 21, 2013 at 6:59 AM, Martin Gainty wrote:
>
>
>
>
> From: brianreinh...@lampreynetworks.com
> To: java-dev@axis.apache.org
> Subject: RE: Rampart STS Username service not returning password in callback
> Date: Sun, 20
: Martin Gainty [mailto:mgai...@hotmail.com]
Sent: Saturday, January 19, 2013 7:40 PM
To: java-dev@axis.apache.org
Subject: RE: Rampart STS Username service not returning password in callback
_
From: brianreinh...@lampreynetworks.com
To: java-dev@axis.apache.org
Subject: RE: Rampart STS
From: brianreinh...@lampreynetworks.com
To: java-dev@axis.apache.org
Subject: RE: Rampart STS Username service not returning password in callback
Date: Sat, 19 Jan 2013 08:58:15 -0500
Hi Martin, I did something different. The problem is in WSS4J. In the
UsernameTokenValidation file I simply
passwords as hashes and be interoperable with the
WS-Trust standard.
Brian
From: Martin Gainty [mailto:mgai...@hotmail.com]
Sent: Friday, January 18, 2013 11:24 PM
To: java-dev@axis.apache.org
Subject: RE: Rampart STS Username service not returning password in callback
Hi Brian
assume your
gatoire. Étant donné que les email peuvent facilement
être sujets à la manipulation, nous ne pouvons accepter aucune responsabilité
pour le contenu fourni.
From: brianreinh...@lampreynetworks.com
To: java-dev@axis.apache.org
Subject: RE: Rampart STS Username service not returning password in callba
:mgai...@hotmail.com]
Sent: Wednesday, January 16, 2013 5:14 PM
To: java-dev@axis.apache.org
Subject: RE: Rampart STS Username service not returning password in callback
http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.
0.xsd
i think I found an element we can use
(where
service not returning password in callback
http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.
0.xsd
i think I found an element we can use
(where both noonce and Password would be child elements of
wsc:DerivedKeyToken) so here is the TestCase
http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd
i think I found an element we can use
(where both noonce and Password would be child elements of wsc:DerivedKeyToken)
so here is the TestCase org.apache.rampart.handler.config.OutflowConfiguration
ofc = new or
XSD's)
MG
From: brianreinh...@lampreynetworks.com
To: java-dev@axis.apache.org
Subject: RE: Rampart STS Username service not returning password in callback
Date: Wed, 16 Jan 2013 13:21:30 -0500
Brian: It has nothing to do with my case. I do happen to have a time stamp
security element and it
t: RE: Rampart STS Username service not returning password in callback
Date: Wed, 16 Jan 2013 13:21:30 -0500
Brian: It has nothing to do with my case. I do happen to have a time stamp
security element and it works as expected. I’m just looking to get the
password. From: Martin Gainty [mailto
: Rampart STS Username service not returning password in callback
looks like rampart can transmit and receive Created and Expired Timestamps
in RequestSecurityToken (OASIS WS-Trust)
http://schemas.xmlsoap.org/ws/2005/02/trust";>
http://schemas.xmlsoap.org/ws/2005/02/trust/Iss
then run client.04
does this fit your testcase
Martin
__
Please...do not alter or disrupt this message..Thank You
From: brianreinh...@lampreynetworks.com
To: java-dev@axis.apache.org
Subject: RE: Rampart STS Username service not returning pass
From: Brian Reinhold [mailto:brianreinh...@lampreynetworks.com]
Sent: Wednesday, January 16, 2013 8:50 AM
To: java-dev@axis.apache.org
Subject: RE: Rampart STS Username service not returning password in callback
Well, thats what I am doing for a current work a round. I am performing
I get the
callback, cb.getPassoword() returns null.
Brian
From: George Stanchev [mailto:gstanc...@serena.com]
Sent: Wednesday, January 16, 2013 8:57 AM
To: java-dev@axis.apache.org
Subject: RE: Rampart STS Username service not returning password in callback
Brian,
According to the
[mailto:brianreinh...@lampreynetworks.com]
Sent: Wednesday, January 16, 2013 8:50 AM
To: java-dev@axis.apache.org
Subject: RE: Rampart STS Username service not returning password in callback
Well, thats what I am doing for a current work a round. I am performing the
hash on the client side and
]
George
[1] http://wso2.org/library/3733
From: Brian Reinhold [mailto:brianreinh...@lampreynetworks.com]
Sent: Wednesday, January 16, 2013 6:50 AM
To: java-dev@axis.apache.org
Subject: RE: Rampart STS Username service not returning password in callback
Well, that's what I am doing for a current
-hashed-password-in.html
From: Brian Reinhold [mailto:brianreinh...@lampreynetworks.com]
Sent: Tuesday, January 15, 2013 3:33 PM
To: java-dev@axis.apache.org
Subject: RE: Rampart STS Username service not returning password in callback
Martin,
I looked in the code and it stated that the
ashed-password-in.html
From: Brian Reinhold [mailto:brianreinh...@lampreynetworks.com]
Sent: Tuesday, January 15, 2013 3:33 PM
To: java-dev@axis.apache.org
Subject: RE: Rampart STS Username service not returning password in callback
Martin,
I looked in the code and it stated that the callback must provid
...@hotmail.com]
Sent: Tuesday, January 15, 2013 9:07 PM
To: java-dev@axis.apache.org
Subject: RE: Rampart STS Username service not returning password in callback
*Update to change algo to SHA*
Update: Apparently the chinese have broken MD5 with collision attacks
...perhaps we should consider
y 15, 2013 4:26 PM
To: java-dev@axis.apache.org
Subject: RE: Rampart STS Username service not returning password in callback Hi
Brian
assuming rampart implements this configuration:
http://schemas.xmlsoap.org/soap/envelope/";>
http://www.w3.org/2005/08/addressing";>
h
e sujets à la manipulation, nous ne
pouvons accepter aucune responsabilité pour le contenu fourni.
> From: brianreinh...@lampreynetworks.com
> To: java-dev@axis.apache.org
> Subject: Rampart STS Username service not returning password in callback
> Date: Tue, 15 Jan 2013 15:00:53 -0500
>
From: Martin Gainty [mailto:mgai...@hotmail.com]
Sent: Tuesday, January 15, 2013 4:26 PM
To: java-dev@axis.apache.org
Subject: RE: Rampart STS Username service not returning password in callback
Hi Brian
assuming rampart implements this configuration:
http://schemas.xmlsoap.org/soap
diffusion non autorisée ou la copie de ceci est
interdite. Ce message sert à l'information seulement et n'aura pas n'importe
quel effet légalement obligatoire. Étant donné que les email peuvent facilement
être sujets à la manipulation, nous ne pouvons accepter aucune responsabil
PART A:
Has anyone else had this problem? I have a simple STS Username token request
for a SAML token where the username token is as follows:
myName
http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-username-token
-profile-1.0#PasswordText">myPassword
On the receive sid
Has anyone else had this problem? I have a simple STS Username token request
for a SAML token where the username token is as follows:
myName
http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-username-token
-profile-1.0#PasswordText">myPassword
On the receive side there i
32 matches
Mail list logo
