tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "AJ (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (MTOMCAT-202) Cannot enable SSO for multiple contexts in embedded tomcat
Date Mon, 21 Jan 2013 13:56:13 GMT

     [ https://issues.apache.org/jira/browse/MTOMCAT-202?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

AJ updated MTOMCAT-202:
-----------------------

    Description: 
I am trying to enable SSO between two webapps being deployed in an embedded tomcat instance
created using the tomcat7-maven-plugin.

### Github Repo/Zip and instructions to reproduce the problem

Please take a look at the pom.xml (http://bit.ly/XQPCYV) and the server.xml (http://bit.ly/UenijR).
If you wish, you could also clone the github repo (https://github.com/ajorpheus/sso-embedded-tomcat)
or download the zip (https://github.com/ajorpheus/sso-embedded-tomcat/archive/master.zip)
(718kb). If you do so the instructions to reproduce the problem are in the Readme.


### The problem

The embedded tomcat runs fine and the two webapps are deployed to the appropriate contexts
as expected. However, SSO is never enabled even though the server.xml has the correct configuration.
Well, I assume it is correct since the exact same server.xml works fine in a standalone Tomcat
7 instance.

My tinkering has indicated that the problem is related to how the server.xml ends up in the
embedded tomcat instance. Initially, I was under the wrong impression that simply having the
server.xml in src/main/tomcatconf was enough since it did get copied over the embedded tomcat
( in target/tomcat/conf). But it seems, unless you refer to the server.xml in the plugin configuration
like so : 
{code}<serverXml>src/main/tomcatconf/server.xml</serverXml>{code}, it does not
get honored and the config contained does not have any affect.

However, as soon as I uncomment that above, the <webapps> portion of the configuration
is completely ignored and the webapps are never deployed.

There seem to no existing bugs (http://bit.ly/XQPWaf) and I am out of ideas at the moment.
It would be great if you could share your experience and point me to what I might be missing.

  was:
I am trying to enable SSO between two webapps being deployed in an embedded tomcat instance
created using the tomcat7-maven-plugin.

### Github Repo/Zip and instructions to reproduce the problem

Please take a look at the pom.xml (http://bit.ly/XQPCYV) and the server.xml (http://bit.ly/UenijR).
If you wish, you could also clone the github repo (https://github.com/ajorpheus/sso-embedded-tomcat)
or download the zip (https://github.com/ajorpheus/sso-embedded-tomcat/archive/master.zip)
(718kb). If you do so the instructions to reproduce the problem are in the Readme.


### The problem

The embedded tomcat runs fine and the two webapps are deployed to the appropriate contexts
as expected. However, SSO is never enabled even though the server.xml has the correct configuration.
Well, I assume it is correct since the exact same server.xml works fine in a standalone Tomcat
7 instance.

My tinkering has indicated that the problem is related to how the server.xml ends up in the
embedded tomcat instance. Initially, I was under the wrong impression that simply having the
server.xml in src/main/tomcatconf was enough since it did get copied over the embedded tomcat
( in target/tomcat/conf). But it seems, unless you refer to the server.xml in the plugin configuration
like so : 
{code}<serverXml>src/main/tomcatconf/server.xml</serverXml>{code}, it does not
get honored and the config contained does not have any affect.

However, as soon as I uncomment that above, the <webapps> portion of the configuration
is completely ignored and the webapps are never deployed.

There seem to no existing [bugs|https://issues.apache.org/jira/issues/?jql=%28text%20~%20sso%20OR%20text%20~%20%22single%20sign%20on%22%20OR%20text%20~%20%22server.xml%22%20OR%20text%20~%20serverXml%29%20AND%20project%20=%20MTOMCAT%20ORDER%20BY%20resolution%20ASC]
and I am out of ideas. It would be great if you could share your experience and point me to
what I might be missing.

    
> Cannot enable SSO for multiple contexts in embedded tomcat
> ----------------------------------------------------------
>
>                 Key: MTOMCAT-202
>                 URL: https://issues.apache.org/jira/browse/MTOMCAT-202
>             Project: Apache Tomcat Maven Plugin
>          Issue Type: Bug
>          Components: tomcat7
>    Affects Versions: 2.0
>            Reporter: AJ
>            Assignee: Olivier Lamy (*$^¨%`£)
>              Labels: sso, tomcat
>
> I am trying to enable SSO between two webapps being deployed in an embedded tomcat instance
created using the tomcat7-maven-plugin.
> ### Github Repo/Zip and instructions to reproduce the problem
> Please take a look at the pom.xml (http://bit.ly/XQPCYV) and the server.xml (http://bit.ly/UenijR).
If you wish, you could also clone the github repo (https://github.com/ajorpheus/sso-embedded-tomcat)
or download the zip (https://github.com/ajorpheus/sso-embedded-tomcat/archive/master.zip)
(718kb). If you do so the instructions to reproduce the problem are in the Readme.
> ### The problem
> The embedded tomcat runs fine and the two webapps are deployed to the appropriate contexts
as expected. However, SSO is never enabled even though the server.xml has the correct configuration.
Well, I assume it is correct since the exact same server.xml works fine in a standalone Tomcat
7 instance.
> My tinkering has indicated that the problem is related to how the server.xml ends up
in the embedded tomcat instance. Initially, I was under the wrong impression that simply having
the server.xml in src/main/tomcatconf was enough since it did get copied over the embedded
tomcat ( in target/tomcat/conf). But it seems, unless you refer to the server.xml in the plugin
configuration like so : 
> {code}<serverXml>src/main/tomcatconf/server.xml</serverXml>{code}, it does
not get honored and the config contained does not have any affect.
> However, as soon as I uncomment that above, the <webapps> portion of the configuration
is completely ignored and the webapps are never deployed.
> There seem to no existing bugs (http://bit.ly/XQPWaf) and I am out of ideas at the moment.
It would be great if you could share your experience and point me to what I might be missing.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org


Mime
View raw message