As long as the role-name in the manager app web.xml matches the role assigned to a user in tomcat-users.xml, it works.
----- Original Message ----- From: "Cox, Charlie" <[EMAIL PROTECTED]> To: "'Tomcat Users List'" <[EMAIL PROTECTED]> Sent: Monday, April 01, 2002 10:15 AM Subject: RE: Reloading Web Applications without manager and without reloadable=true > I stand corrected. I didn't think you could override the default manager > role since it is not defined in the web.xml. > > So you have manager working with a user without the 'manager' role? Or are > you adding another role requirement to to the manager path? This is what it > appears that you are doing in the example as opposed to replacing 'manager' > with 'myappmanager'. > > Certainly you could add another role requirement on top of manager - you > would just have to make sure that each webapp's manager does the same if you > want users to only have access to their own app. > > Charlie > > > -----Original Message----- > > From: Jeff Larsen [mailto:[EMAIL PROTECTED]] > > Sent: Monday, April 01, 2002 10:34 AM > > To: Tomcat Users List > > Subject: Re: Reloading Web Applications without manager and without > > reloadable=true > > > > > > Not true. I've tested with a role-name other than manager. It > > is configurable in the web.xml for the manager app. See excerpt > > below. (TC 4.0.3) > > > > <security-constraint> > > <web-resource-collection> > > <web-resource-name>Entire Application</web-resource-name> > > <url-pattern>/*</url-patter> > > </web-resource-collection> > > <auth-constraint> > > <role-name>myappmanager</role-name> > > </auth-constraint> > > </security-constraint> > > > > > > > > > > ----- Original Message ----- > > From: "Cox, Charlie" <[EMAIL PROTECTED]> > > To: "'Tomcat Users List'" <[EMAIL PROTECTED]> > > Sent: Monday, April 01, 2002 6:02 AM > > Subject: RE: Reloading Web Applications without manager and > > without reloadable=true > > > > > > > The role must be 'manager'. The manager app currently does > > not let you > > > specify the role to use. > > > > > > Charlie > > > > > > > -----Original Message----- > > > > From: Jeff Larsen [mailto:[EMAIL PROTECTED]] > > > > Sent: Thursday, March 28, 2002 2:14 PM > > > > To: Tomcat Users List > > > > Subject: Re: Reloading Web Applications without manager > > and without > > > > reloadable=true > > > > > > > > > > > > I'm not 100% sure about this, but I'm sure someone will > > > > correct me if I'm wrong.... > > > > > > > > Isn't the manager app limited to apps within the same > > > > virtual host? So have your sysadmin create a tomcat > > > > virtual host just for your web app. Install the manager > > > > app in your virtual host under a unique context name so > > > > as not to conflict with the manager app for other virtual > > > > hosts. Then configure the role in the web.xml for YOUR manager > > > > app to a custom role and create a unique username and password > > > > for that role in tomcat-users.xml. > > > > > > > > Now you have access to a manager app just for your webapp. And > > > > your sysadmin rests easy knowing that you can't mess with anyone > > > > elses webapps. > > > > > > > > Jeff > > > > > > > > ----- Original Message ----- > > > > From: "Tarun Ramakrishna Elankath" <[EMAIL PROTECTED]> > > > > To: <[EMAIL PROTECTED]> > > > > Sent: Wednesday, March 27, 2002 10:28 AM > > > > Subject: Reloading Web Applications without manager and > > > > without reloadable=true > > > > > > > > > > > > > Hello all, > > > > > I had asked this question previously without anybody > > > > understanding. I > > > > > need to be able to reload my web-application *without* > > setting the > > > > > reloadable=true parameter in the context tag, when I *dont* > > > > have access > > > > > to the manager web-application. > > > > > Why? This is because my web-application will be on a > > > > *production* server > > > > > where reloadable *should* be set equal to false (as the > > > > documentation > > > > > recommends). And I will not be given access to the manager > > > > application > > > > > because my web-application resides with web-apps of other > > > > independent > > > > > developers. I do not want to bother my system administrator > > > > for every > > > > > modification that I commit to the site. (Even production > > > > environments > > > > > suffer from modification) > > > > > Is there another way of forcing Tomcat to reload classes of > > > > *only* my web > > > > > application? If no such program exists then I would be > > grateful if > > > > > someone could point me towards how to write one. > > > > > > > > > > Any help appreciated, > > > > > Tarun > > > > > > > > > > > > > > > > > > > > -- > > > > > To unsubscribe: > > > > <mailto:[EMAIL PROTECTED]> > > > > > For additional commands: > > > > <mailto:[EMAIL PROTECTED]> > > > > > Troubles with the list: > > > > <mailto:[EMAIL PROTECTED]> > > > > > > > > -- > > > > To unsubscribe: > <mailto:[EMAIL PROTECTED]> > > > For additional commands: <mailto:[EMAIL PROTECTED]> > > > Troubles with the list: <mailto:[EMAIL PROTECTED]> > > > > > > > -- > > To unsubscribe: <mailto:[EMAIL PROTECTED]> > > For additional commands: <mailto:[EMAIL PROTECTED]> > > Troubles with the list: <mailto:[EMAIL PROTECTED]> > > -- > To unsubscribe: <mailto:[EMAIL PROTECTED]> > For additional commands: <mailto:[EMAIL PROTECTED]> > Troubles with the list: <mailto:[EMAIL PROTECTED]> > > -- > To unsubscribe: <mailto:[EMAIL PROTECTED]> > For additional commands: <mailto:[EMAIL PROTECTED]> > Troubles with the list: <mailto:[EMAIL PROTECTED]> -- To unsubscribe: <mailto:[EMAIL PROTECTED]> For additional commands: <mailto:[EMAIL PROTECTED]> Troubles with the list: <mailto:[EMAIL PROTECTED]>
