STSSecurityHandler: Refactor and have the security token be passed to this handler via the SOAPMessageContext instead of subclassing ------------------------------------------------------------------------------------------------------------------------------------ Key: JBID-216 URL: https://jira.jboss.org/jira/browse/JBID-216 Project: JBoss Identity Issue Type: Task Components: Identity-Federation Affects Versions: IDFED-1.0.0.beta3 Reporter: Daniel Bevenius Assignee: Daniel Bevenius Priority: Minor Currently the STSSecurityHeader is abstract and concrete implementations are expected to implement two methods that return the QName of the Security element and that of the security token that this handler can handle. I think that this was perhaps not a good choice on my part and a better choice would be to push this responsibility to a different handler that would have the responsibility to extract the security token and set that token in the SOAPMessageContext in a known location. This should make this more extendable and less brittle (no subclassing). Users that want to extract a different security token, or simply a different version, only need to change/implement a handler and extract the correct security token and set it in the context. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira