eclipse-ee4j / eclipse-ee4j/metro-wsit
jsr109 Scenario 1 - Client_SUN STS_MS Server_MS : Username Handler Not Configured
- Dominant language
- Java
- Stars
- 6
- Forks
- 21
- Avg merge
- 10h 2m
- Merged PRs (30d)
- 1
Description
Scenario : Scenario 1 - Client_SUN STS_MS Server_MS
this issue look like test configuration issue, not sure why this issue appearing
this test was passing earlier.
Soap Log
=========
ARNING: WSP0019: Suboptimal policy alternative selected on the client side with
fitness "PARTIALLY_SUPPORTED".
May 10, 2010 6:57:28 PM com.sun.xml.wss.impl.misc.DefaultCallbackHandler
handleUsernameCallback
SEVERE: WSS1500: Username Handler Not Configured properly using Callback and is
null. (not cofigured)
May 10, 2010 6:57:28 PM com.sun.xml.wss.impl.misc.DefaultSecurityEnvironmentImpl
getUsername
SEVERE: WSS0216: An Error occurred using Callback Handler for : UsernameCallback
May 10, 2010 6:57:28 PM com.sun.xml.wss.impl.misc.DefaultSecurityEnvironmentImpl
getUsername
SEVERE: WSS0217: An Error occurred using Callback Handler handle() Method.
javax.security.auth.callback.UnsupportedCallbackException: Username Handler Not
Configured
at
com.sun.xml.wss.impl.misc.DefaultCallbackHandler.handleUsernameCallback(DefaultCallbackHandler.java:385)
at
com.sun.xml.wss.impl.misc.DefaultCallbackHandler.handle(DefaultCallbackHandler.java:482)
at
com.sun.xml.wss.impl.misc.DefaultSecurityEnvironmentImpl.getUsername(DefaultSecurityEnvironmentImpl.java:1118)
at
com.sun.xml.wss.impl.filter.AuthenticationTokenFilter.resolveUserNameTokenData(AuthenticationTokenFilter.java:383)
at
com.sun.xml.wss.impl.filter.AuthenticationTokenFilter.addUserNameTokenToMessage(AuthenticationTokenFilter.java:466)
at
com.sun.xml.wss.impl.filter.AuthenticationTokenFilter.processUserNameToken(AuthenticationTokenFilter.java:113)
at com.sun.xml.wss.impl.HarnessUtil.processWSSPolicy(HarnessUtil.java:108)
at com.sun.xml.wss.impl.HarnessUtil.processDeep(HarnessUtil.java:272)
at
com.sun.xml.wss.impl.SecurityAnnotator.processMessagePolicy(SecurityAnnotator.java:189)
at com.sun.xml.wss.impl.SecurityAnnotator.secureMessage(SecurityAnnotator.java:150)
at
com.sun.xml.wss.jaxws.impl.SecurityTubeBase.secureOutboundMessage(SecurityTubeBase.java:421)
at
com.sun.xml.wss.jaxws.impl.SecurityClientTube.processClientRequestPacket(SecurityClientTube.java:304)
at
com.sun.xml.wss.jaxws.impl.SecurityClientTube.processRequest(SecurityClientTube.java:233)
at com.sun.xml.ws.api.pipe.Fiber.__doRun(Fiber.java:629)
at com.sun.xml.ws.api.pipe.Fiber._doRun(Fiber.java:588)
at com.sun.xml.ws.api.pipe.Fiber.doRun(Fiber.java:573)
at com.sun.xml.ws.api.pipe.Fiber.runSync(Fiber.java:470)
at com.sun.xml.ws.client.Stub.process(Stub.java:319)
at com.sun.xml.ws.client.dispatch.DispatchImpl.doInvoke(DispatchImpl.java:189)
at com.sun.xml.ws.client.dispatch.DispatchImpl.invoke(DispatchImpl.java:215)
at
com.sun.xml.ws.security.trust.impl.TrustPluginImpl.invokeRST(TrustPluginImpl.java:624)
at
com.sun.xml.ws.security.trust.impl.TrustPluginImpl.process(TrustPluginImpl.java:170)
at com.sun.xml.ws.security.trust.impl.client.STSIssuedTokenProv
Server log
==========
[#|2010-05-10T18:51:54.862+0530|WARNING|glassfish3.0|javax.enterprise.webservices.org.glassfish.webservices|_ThreadID=28;_ThreadName=Thread-1;|Servlet
web service endpoint 'simple.sts.STSImpl' failure
javax.xml.ws.WebServiceException: WSDL
jndi:/server/jaxws-s1-sts/WEB-INF/wsdl/sts.wsdl has the following services
[
{http://tempuri.org/}
SecurityTokenService] but not . Maybe you forgot to
specify a serviceName and/or targetNamespace in @WebService/@WebServiceProvider?
at
com.sun.xml.ws.server.EndpointFactory.verifyPrimaryWSDL(EndpointFactory.java:476)
at com.sun.xml.ws.server.EndpointFactory.createEndpoint(EndpointFactory.java:155)
at com.sun.xml.ws.api.server.WSEndpoint.create(WSEndpoint.java:505)
at com.sun.xml.ws.api.server.WSEndpoint.create(WSEndpoint.java:560)
at org.glassfish.webservices.JAXWSServlet.registerEndpoint(JAXWSServlet.java:405)
at org.glassfish.webservices.JAXWSServlet.doInit(JAXWSServlet.java:264)
at org.glassfish.webservices.JAXWSServlet.init(JAXWSServlet.java:99)
at org.apache.catalina.core.StandardWrapper.initServlet(StandardWrapper.java:1428)
at org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:1230)
at
org.apache.catalina.core.StandardContext.loadOnStartup(StandardContext.java:5007)
at org.apache.catalina.core.StandardContext.start(StandardContext.java:5280)
at com.sun.enterprise.web.WebModule.start(WebModule.java:499)
at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:928)
at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:912)
at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:694)
at com.sun.enterprise.web.WebContainer.loadWebModule(WebContainer.java:1947)
at com.sun.enterprise.web.WebContainer.loadWebModule(WebContainer.java:1619)
at com.sun.enterprise.web.WebApplication.start(WebApplication.java:90)
at org.glassfish.internal.data.EngineRef.start(EngineRef.java:126)
at org.glassfish.internal.data.ModuleInfo.start(ModuleInfo.java:241)
at org.glassfish.internal.data.ApplicationInfo.start(ApplicationInfo.java:236)
at
com.sun.enterprise.v3.server.ApplicationLifecycle.deploy(ApplicationLifecycle.java:339)
at
com.sun.enterprise.v3.server.ApplicationLifecycle.deploy(ApplicationLifecycle.java:183)
at org.glassfish.deployment.admin.DeployCommand.execute(DeployCommand.java:272)
at
com.sun.enterprise.v3.admin.CommandRunnerImpl$1.execute(CommandRunnerImpl.java:310)
at
com.sun.enterprise.v3.admin.CommandRunnerImpl.doCommand(CommandRunnerImpl.java:320)
at
com.sun.enterprise.v3.admin.CommandRunnerImpl.doCommand(CommandRunnerImpl.java:1176)
at
com.sun.enterprise.v3.admin.CommandRunnerImpl.access$900(CommandRunnerImpl.java:83)
at
com.sun.enterprise.v3.admin.CommandRunnerImpl$ExecutionContext.execute(CommandRunnerImpl.java:12
#### Environment
Operating System: All
Platform: All
#### Affected Versions
[2.0]
Source: [https://github.com/javaee/metro-wsit/issues/1430](https://github.com/javaee/metro-wsit/issues/1430)
Author: glassfishrobot
Contributor guide
Research direction
Start with the Scenario 1 test configuration and compare it with the earlier passing setup. Trace the reported failures through DefaultCallbackHandler.java and EndpointFactory.java, along with the referenced sts.wsdl and STSImpl endpoint. Done means the scenario deploys and runs without the username-handler or WSDL service errors.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- api, backend, testing-qa
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100