Re: [Hypercontent-users] CASIFY Hypercontent - issue

[tom t. <j_l...@ya...>]

Hi Alex,

Thanks for the reply, I did further investigation,
still I am at the casifying task (not touched uPortal
yet). I have listed all the information below.

See my initial observations below ...........

I did edit the pipelines.xml as per the instructions
in  cas-support folder readme doc. Also I followed all
the instructions to casify the applications. 

It looks to me pipeline.xml works fine as when I click
my newly created project(myproject) it redirects to
the CAS login page.
but when I enter user name and password(student Id,
and password) it does not redirected to the HC. So far
I have not edited any of the permissions.xml or
groups.xml files those remains as it is. I am under
the impression even without that it should work and
can read contents.
(I have only edited or modified
jaas.properties,hypercontent.properties,pipelines.xml,project-definitions.xml
   files only.)


The browser shows the following error.

---------
The page isn't redirecting properly
Firefox has detected that the server is redirecting
the request for this address in a way that will never
complete.
    *   This problem can sometimes be caused by
disabling or refusing to accept
          cookies.

-------------

When I looked into the tomcat log file it shows the
following exception, I am getting such repeated such
exceptions.

my jaas.properties look as follows 

HyperContent
{
edu.yale.its.tp.cas.client.jaas.CASLoginModule
sufficient
cas_validate_url="https://localhost:8443/cas/serviceValidate";

};

let me know whats what is wrong in this setup


tomcat log

2006-10-30 12:22:06,416 INFO
[org.jasig.cas.CentralAuthenticationServiceImpl] -
<Granted service ticket [ST-2-AoGXke7hPRbj0SVbrMxn]
for service
[http://localhost:8080/hypercontent/my-project/?mode=login&passmode=&command=Login]
for user [3686288]>
2006-10-30 12:22:06,444 ERROR
[org.hypercontent.util.Logger] - <>
javax.security.auth.login.LoginException: No
LoginModules configured for HyperContent
        at
javax.security.auth.login.LoginContext.init(LoginContext.java:256)
        at
javax.security.auth.login.LoginContext.<init>(LoginContext.java:367)
        at
javax.security.auth.login.LoginContext.<init>(LoginContext.java:444)
        at
org.hypercontent.server.commands.Login.execute(Login.java:85)
        at
org.hypercontent.server.ContentServer.service(ContentServer.java:431)
        at
org.hypercontent.servlet.CompositionServlet.doGet(CompositionServlet.java:104)
        at
javax.servlet.http.HttpServlet.service(HttpServlet.java:689)
        at
javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
        at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252)
        at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
        at
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213)
        at
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:178)
        at
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126)
        at
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105)
        at
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107)
        at
org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148)
        at
org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:868)
        at
org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:663)
       at
org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:527)
        at
org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFollowerWorkerThread.java:80)
        at
org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:684)
        at java.lang.Thread.run(Thread.java:595)



More information....................

my pipeline.xml looks as follows

<pipelines>
        <!-- login and logout pipelines can use
RedirectStage to bounce to an external authentication
server
                a passthrough URL can be constructed,
such as

               
${abs-project-base}${request-path}?mode=interactive&amp;command=Logout

                see RedirectStage docs for a list of
all recognized variables
        -->
        <pipeline name="login-local"
mode="login-local" basedir="/"
content-type="text/html" binding="all">
                <exec
stage="org.hypercontent.project.engine.stage.XMLIncludeStage"/>
                <exec
stage="org.hypercontent.project.engine.stage.XSLTransformStage">
                        <with-param name="source"
value="/screens/login.xsl"/>
                        <with-param name="parms"
value="${request-parms}"/>
                </exec>
        </pipeline>

        <pipeline name="login" mode="login"
basedir="/" content-type="text/html" binding="all">
                <exec
stage="org.hypercontent.project.engine.stage.SessionAttributeStage">
                        <with-param name="name"
value="service"/>
                        <with-param name="value"
value="${abs-project-base}${request-path}%3f${request-parms-encoded}%26command%3DLogin"/>
                </exec>
                <exec
stage="org.hypercontent.project.engine.stage.RedirectStage">
                        <with-param name="location"
value="https://localhost:8443/cas/login?service=${service}"/>
                </exec>
        </pipeline>

        <pipeline name="logout" mode="logout"
basedir="/" content-type="text/html" binding="all">
                <exec
stage="org.hypercontent.project.engine.stage.RedirectStage">
                        <with-param name="location"
value="${abs-project-base}${request-path}?${request-parms}&amp;command=Logout"/>
                </exec>
        </pipeline>





Thanks










 
____________________________________________________________________________________
Want to start your own business? Learn how on Yahoo! Small Business 
(http://smallbusiness.yahoo.com)