Currently Stefan has implemented a JBoss STS building on the object model in the JBoss Identity project. http://www.jboss.org/community/docs/DOC-13642 Given this, from an user's perspective, there are two options: Option A: ==== User configures the JBoss STS from JBID. In this case, the delegation of the core WS functionality needs to be sent to the JBossWS stack (irrespective of which underlying stack exists - native, cxf or metro). I think Stefan is pretty clear on this end (except that the client code has some JBossWS classes). Apart from that, it is plain Jax-WS usage. Option B: ===== User would like to use the WS-Sec implementation that is present in the JBossWS stack. During the usage, the user would like to delegate the ws-trust token handling to the JBID infrastructure. For this use case, Stefan needs to know what handlers/interceptor chain or such exists in the JBossWS stack to provide token handlers for ws-t (saml token profile, x509 etc). View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4228420#... Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&a...