AW: Callback supplied no password for: null

Brian,

did you use the parameter "encryptUser" that defines
the "recieving user" of the encrypted message. The sender has
to use the public key of the receiver to encrypt, thus
you have to use this parameter.

During Signature the the private key of the "sending user" 
is used to sign the request message (the parameter "user")

Regards,
Werner


> -----Ursprüngliche Nachricht-----
> Von: Brian Shields 
> [mailto:brian.shields-0L/3q/7SXVYvgfZh3HfYAwisQyUhxotx@xxxxxxxxxxxxxxxx] 
> Gesendet: Mittwoch, 28. September 2005 22:58
> An: wss4j-dev-28n8OjmUYWfNLxjTenLetw@xxxxxxxxxxxxxxxx
> Betreff: Callback supplied no password for: null
> 
> 
> Hi all,
> I am having trouble encrypting portions of the SOAP message. What I 
> (think) i have got working is sending a username and password 
> digest to 
> a service, envoking the service sucessfully and getting my 
> response. I 
> am using the PasswordCallback class. However, i am now trying 
> to encrypt 
> the username token in the Security tag of the soap header. 
> When this is 
> sent to the server and decrypted (i can only assume successfully as i 
> get no error), I get returned the error
> org.apache.ws.security.WSSecurityException: General security error 
> (WSSecurityEngine: Callback supplied no password for: null)
> Does this mean that the message was not decrypted 
> successfully? It seems 
> to pass the decryption stage and get stuck in the Callback class, 
> obviously there is no password associated with "null".
> 
> Brian.
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: 
> wss4j-dev-unsubscribe-28n8OjmUYWfNLxjTenLetw@xxxxxxxxxxxxxxxx
> For additional commands, e-mail: 
> wss4j-dev-help-28n8OjmUYWfNLxjTenLetw@xxxxxxxxxxxxxxxx
> 
>