[
https://issues.apache.org/jira/browse/WSS-62?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Colm O hEigeartaigh updated WSS-62:
-----------------------------------
Fix Version/s: 1.5.5
Affects Version/s: 1.5.4
> the crypto file not being retrieved in the doReceiverAction method for the
> Saml Signed Token
> --------------------------------------------------------------------------------------------
>
> Key: WSS-62
> URL: https://issues.apache.org/jira/browse/WSS-62
> Project: WSS4J
> Issue Type: Bug
> Affects Versions: 1.5.4
> Environment: WSS4J 1.5.0, OpenSaml 1.0.1
> Reporter: Marie Rizzo
> Assignee: Colm O hEigeartaigh
> Fix For: 1.5.5
>
>
> I have a client which should send a signed saml token to the service. I'm
> allowing the WSHandler to build the signed SAML token from the client
> request, which gives no problems. The problem arises when the WSHandler tries
> to verify the request before it allows the client access to the service. From
> my traces it seems that the doReceiverAction does not retrieve the crypto
> file used to build the saml token and signature. Later, when the tokens are
> being processed by the WSSecurityEngine, the Saml token is processed with no
> problems. However, the next token is the signature, which calls the
> SignatureProcessor class to verify the signature... at this point it blows
> up.
> Can someone please check whether I'm doing something wrong or whether this is
> a bug?
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
