[jboss-identity-issues] [JBoss JIRA] Updated: (JBID-189) Add 'TokenElement' and 'TokenElementNS' to the SAML20TokenPovider in jboss-sts.xml

Add 'TokenElement' and 'TokenElementNS' to the SAML20TokenPovider in jboss-sts.xml ---------------------------------------------------------------------------------- Key: JBID-189 URL: https://jira.jboss.org/jira/browse/JBID-189 Project: JBoss Identity Issue Type: Task Components: Identity-Federation Affects Versions: IDFED-1.0.0.beta1 Reporter: Daniel Bevenius Assignee: Anil Saldhana Priority: Minor Fix For: IDFED-1.0.0.beta2 To get token validation to work using a saml assertion I needed to add the TokenElement and TokenElementNS to jboss-sts.xml: <TokenProvider ProviderClass="org.jboss.identity.federation.core.wstrust.plugins.saml.SAML20TokenProvider" TokenType="http://docs.oasis-open.org/wss/oasis-wss-saml-token-profi... TokenElement="Assertion" TokenElementNS="urn:oasis:names:tc:SAML:2.0:assertion"/> Without this in jboss-sts.xml no provider will be found and a NullPointerException will be throw: 16:44:11,343 ERROR [SOAPFaultHelperJAXWS] SOAP request exception java.lang.NullPointerException at org.jboss.identity.federation.core.wstrust.StandardRequestHandler.validate(StandardRequestHandler.java:336) at org.jboss.identity.federation.bindings.jboss.wstrust.JBossSTS.handleTokenRequest(JBossSTS.java:142) at org.jboss.identity.federation.bindings.jboss.wstrust.JBossSTS.invoke(JBossSTS.java:90) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) Perhaps a check in StandardRequestHander that gives some more info would help: if (provider == null) throw new WSTrustException("No SecurityTokenProvider configured for " + securityToken.getNamespaceURI() + ":" + securityToken.getLocalName());