Lots of things might be happening, Any dumps or other useful info in
the log files?
A) Are you actually reaching the LoginServlet, DefaultLoginModule and
LoginRedirectorServlet ?
B) What is the LoginRedirectorServlet mapped to in the web.xml ?
C) It may simply be a page not found.
-What profiling rule does the user you're attempting to login have?
-Is your pages directory set up to actually provide a default page
(psml file) according to that profiling rule?
To the people who know more about apache (most of my direct experience
has been working simply within tomcat) is there something in the
httpd.conf that needs to be set to allow the portal to respond from
localhost? I know I've run into issues there with portlet webapps
running under jetspeed not being able to serve out images until it was
updated.
brunp wrote:
Equivalent to a "Page not found" error, or something to that affect. I was
going to try a couple things tomorrow to see if I can get around the error.
Paul
David Dyer wrote:
What actually happens when you redirect to
https://127.0.0.1:8080/portal/login/redirector ?
brunp wrote:
I figured as much, but if the ServletRequest returns 127.0.0.1:8080 as
the
servername when building the URL, then you are pooched unless you
override
and replace the HttpServletRequest class.
Again, I had thought the property mentioned above was to enable us to use
relative URL redirecting???
Paul
ronatartifact wrote:
I could be way off base here but I would think that your redirect has to
be something that your browser is going to have to be able to interpret.
That would mean that you have to specify your "front door"
https://10.35.5.99/portal/login/redirector in your custom code.
Not sure that I am telling you anything that you do not already know.
Ron
brunp wrote:
There are two systems involved. My notebook (i.e., used for browsing to
the
site) and the linux server that is running apache/linux.
So, I enter "https://10.35.5.199/portal";, where portal is the jetspeed
root
directory. The login page shows up and within the LoginProxyServlet,
which
is custom, I want to redirect to /portal/login/redirector,
and when that occurs, my browser is then attempting to connect to
https://127.0.0.1:8080/portal/login/redirector
IF proxyName and ProxyPort are defined in Server.xml for tomcat, and I
browse by FQDN, I get a redirect URL of: https://<FQDN name of
server>/portal/login/redirector, which is a valid site.
So.....that is the state of play.....trying to another locaiton on the
same
server.
ronatartifact wrote:
localhost is the name of 127.0.0.1.
Are you trying to redirect to localhost or some other site?
Ron
brunp wrote:
Thank you to all......so, I can get to my "login" page after making
some
macro adjustments, however, when I press login, my LoginServlet pipes
out
some logs, I redirect to another location, but it appears that the
redirect
replaces the IP address w/ 127.0.0.1
So something within the Apache configuration and/or the redirect
rules
is
replacing the x-forward-host
with localhost...
Paul
hemantmalik wrote:
You can use mod_jk module as well and then can connect to AJP
connector
of
tomcat as mentioned by Bhaskar.
On Thu, May 7, 2009 at 9:41 PM, Bhaskar Roy
<[email protected]>
wrote:
Use ajp protocol, much easier!
Thanks
Bhaskar
http://lims.chikpea.com
On Thu, May 7, 2009 at 6:32 PM, Ron Wheeler
<[email protected]>wrote:
brunp wrote:
I have this in profiler.xml:
158 <bean id='HostnameCriterionResolver'
class='org.apache.jetspeed.profiler.rules.impl.HostnameCriterionResolver'>
159 <!-- use the dot prefix, for ex: "accounting.xyz.com"
returns
"accounting" -->
160 <constructor-arg type="boolean" index="0">
161 <value>false</value>
162 </constructor-arg>
163 </bean>
Paul Brun Quotes: I have this in mine too.....
I will have to look into the mod_rewrite stuff tomorrow. No time
this
evening....
I am not sure if this is the same thing that you are trying to do
but
we
have Apache proxying Jetspeed 2.1.2 and 2.1.3 in exactly the same
way.
There are no modifications to the Tomcat application .
Since the Jetspeed portal is reachable as localhost:8080 from the
server
that Apache runs on, we just added a set of proxy statements to
the
httpd-vhost.conf to proxy www.mydomain.com/myportal to
localhost:8080/myportal and created a dummy index.html on the
apache
site
to
redirect www.mydomain.com to locahost:8080/myportal so the user
can
just
ask for http://www.mydomain.com
If the tomcat is on another server, adjust your proxy destinations
accordingly.
You need to enable Apache's mod_proxy but after that it is
trivial.
Ron
---------------------------------------------------------------------
To unsubscribe, e-mail:
[email protected]
For additional commands, e-mail:
[email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
