Bug 779957 (SOA-2317) - ESB: security_cert quickstart causes server stack trace
Summary: ESB: security_cert quickstart causes server stack trace
Keywords:
Status: CLOSED WONTFIX
Alias: SOA-2317
Product: JBoss Enterprise SOA Platform 5
Classification: JBoss
Component: JBossESB, Examples
Version: 5.1.0.ER1
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: FUTURE
Assignee: tcunning
QA Contact:
URL: http://jira.jboss.org/jira/browse/SOA...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-09-14 09:04 UTC by Julian Coleman
Modified: 2011-12-06 22:01 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-12-06 22:01:25 UTC
Type: Bug


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker SOA-2317 0 Major Closed ESB: security_cert quickstart causes server stack trace 2014-07-25 07:33:10 UTC

Description Julian Coleman 2010-09-14 09:04:51 UTC
project_key: SOA

When the security_cert quickstart runs, it tries to login with valid credentials, and then
with invalid credentials.  When the login with invalid credentials is tried, the server logs:

  2010-09-14 09:58:56,295 ERROR [org.jboss.soa.esb.listeners.message.ActionProcessingPipeline] (pool-24-thread-1) SecurityService exception : 
  org.jboss.soa.esb.services.security.SecurityServiceException: Exception while trying to login:
        at org.jboss.internal.soa.esb.services.security.JaasSecurityService.authenticate(JaasSecurityService.java:102)
        at org.jboss.soa.esb.listeners.message.ActionProcessingPipeline.processPipeline(ActionProcessingPipeline.java:549)
        at org.jboss.soa.esb.listeners.message.ActionProcessingPipeline.process(ActionProcessingPipeline.java:433)
        at org.jboss.soa.esb.listeners.message.MessageAwareListener$TransactionalRunner.run(MessageAwareListener.java:540)
        at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
        at java.lang.Thread.run(Thread.java:619)
  Caused by: javax.security.auth.login.LoginException: SignatureException : Signature does not match.
        at org.jboss.soa.esb.services.security.auth.login.CertificateLoginModule.login(CertificateLoginModule.java:181)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
        at java.lang.reflect.Method.invoke(Method.java:597)
        at javax.security.auth.login.LoginContext.invoke(LoginContext.java:769)
        at javax.security.auth.login.LoginContext.access$000(LoginContext.java:186)
        at javax.security.auth.login.LoginContext$4.run(LoginContext.java:683)
        at java.security.AccessController.doPrivileged(Native Method)
        at javax.security.auth.login.LoginContext.invokePriv(LoginContext.java:680)
        at javax.security.auth.login.LoginContext.login(LoginContext.java:579)
        at org.jboss.internal.soa.esb.services.security.JaasSecurityService.authenticate(JaasSecurityService.java:94)
        ... 6 more


Note You need to log in before you can comment on or make changes to this bug.