Zimbra offers Open Source email server software and shared calendar for Linux and the Mac
Go Back   Zimbra :: Forums > Zimbra Collaboration Suite > Administrators

Welcome to the Zimbra :: Forums!
Welcome, if you would like to post a comment please register. We also encourage you to explore all things Zimbra with our team and members of the community.

Reply
 
LinkBack Thread Tools Search this Thread Display Modes
  #1 (permalink)  
Old 07-19-2010, 12:54 PM
Senior Member
 
Posts: 57
Default [SOLVED] Preauth + CAS and port 7072

hello all,

we are currently evaluating zimbra and single sign on is a must have for our future solution. we do already have most of our applications shibbolized, zimbra cant use saml2/shibboleth. so we tried with cas integration.

we used the zimbra wiki for the zimbra / cas integration (CASifying Zimbra 6.0 - Zimbra :: Wiki) and on the other side we use casshib with authentication against a shibboleth idp. works like a charm. but after the final redirection to our zimbra installation on port 7072 we get the following message:

Code:
2010-07-19 21:36:29,098 INFO  [btpool0-13://vm00.webop.net:7072/zimbra/public/preauth.jsp?ticket=ST-8-SiYb0GeImgNpIw3eBZPb-cas] [] ProxyGrantingTicketStorageImpl - No Proxy Ticket found for 
2010-07-19 21:36:29,111 WARN  [btpool0-13://vm00.webop.net:7072/service/preauth/?account=asartori@vm00.webop.net&by=name&timestamp=1279568189109&expires=0&preauth=23a9c59a1b2b61d19c2c4e6f0d9442426c1e9902] [] soap - 
com.zimbra.common.service.ServiceException: system failure: Request not allowed on port 7072
ExceptionId:btpool0-13://vm00.webop.net:7072/service/preauth/?account=asartori@vm00.webop.net&by=name&timestamp=1279568189109&expires=0&preauth=23a9c59a1b2b61d19c2c4e6f0d9442426c1e9902:1279568189111:481c9cdb07fefe26
Code:service.FAILURE
	at com.zimbra.common.service.ServiceException.FAILURE(ServiceException.java:248)
	at com.zimbra.cs.servlet.ZimbraServlet.service(ZimbraServlet.java:169)
	at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
	at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:511)
	at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1166)
	at com.zimbra.cs.servlet.SetHeaderFilter.doFilter(SetHeaderFilter.java:79)
	at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1157)
	at org.mortbay.servlet.UserAgentFilter.doFilter(UserAgentFilter.java:81)
	at org.mortbay.servlet.GzipFilter.doFilter(GzipFilter.java:132)
	at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1157)
	at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:388)
	at org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:216)
	at org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:182)
	at org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:765)
	at org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:418)
	at org.mortbay.jetty.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:230)
	at org.mortbay.jetty.handler.HandlerCollection.handle(HandlerCollection.java:114)
	at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:152)
	at org.mortbay.jetty.handler.rewrite.RewriteHandler.handle(RewriteHandler.java:230)
	at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:152)
	at org.mortbay.jetty.handler.DebugHandler.handle(DebugHandler.java:77)
	at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:152)
	at org.mortbay.jetty.Server.handle(Server.java:326)
	at org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:543)
	at org.mortbay.jetty.HttpConnection$RequestHandler.headerComplete(HttpConnection.java:924)
	at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:547)
	at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:212)
	at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:405)
	at org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:409)
	at org.mortbay.thread.BoundedThreadPool$PoolThread.run(BoundedThreadPool.java:451)
the authentication worked, because when i do a browser request to our http://zimbra:7072 i am logged in and everything works.

any ideas out there? thanks in advance

-andy
Reply With Quote
  #2 (permalink)  
Old 07-22-2010, 11:01 AM
Senior Member
 
Posts: 57
Default

works when using port 80.

-andy
Reply With Quote
Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes


Similar Threads

Why Join?

Registering let's you ask questions, makes it easier to search, displays any files attached to posts, and notifies you about replies.

blog.zimbra.com




 

SEO by vBSEO ©2011, Crawlability, Inc.