Not knowing how it’s supposed to behave, here’s another clue. When I click on
the “Server Status” button, I never get prompted for credentials. Is it a
permissions problem on the server itself. Like the server doesn’t have rights
to the HTML pages?
Thanks in advance,
From: Garber, Frank
Sent: Wednesday, May 22, 2024 2:26 PM
To: Tomcat Users List <users@tomcat.apache.org>
Subject: RE: {EXTERNAL} Re: Tomcat Console - 401 Unauthorized
I’m not sure how the URLs got munged up.
What I have on my side is valid XML, so I’m not worried about that. I’m really
just concerned that the following isn’t working:
<role rolename="manager-gui"/>
<role rolename="manager-script"/>
<role rolename="admin-gui"/>
<user username="admin" password="admin"
roles="admin-gui,manager-gui,manager-script" />
Thanks in advance,
From: Chuck Caldarale <n82...@gmail.com<mailto:n82...@gmail.com>>
Sent: Wednesday, May 22, 2024 2:16 PM
To: Tomcat Users List <users@tomcat.apache.org<mailto:users@tomcat.apache.org>>
Subject: {EXTERNAL} Re: Tomcat Console - 401 Unauthorized
> On May 22, 2024, at 10: 51, Garber, Frank <Francis. Garber@ elevancehealth.
> com. INVALID> wrote: > > I've just installed Tomcat 9. 0. 89. <snip/> >
> Tomcat runs, and I can get to the console at https: //urldefense.
> com/v3/__http: //localhost:
> 8080/__;!!IZ3lH8c!yts7ZdG2lLWkLHZXnQFxUeyJeHbX_NxqieI-zv0Ui8nBlMzfnQ_mbT_M5evoEof6o-OZ5azA1nAyFvzyQAcQ$
> On May 22, 2024, at 10:51, Garber, Frank
> <francis.gar...@elevancehealth.com.INVALID<mailto:francis.gar...@elevancehealth.com.INVALID>>
> wrote:
>
> I've just installed Tomcat 9.0.89.
<snip/>
> Tomcat runs, and I can get to the console at
> https://urldefense.com/v3/__http://localhost:8080/__;!!IZ3lH8c!yts7ZdG2lLWkLHZXnQFxUeyJeHbX_NxqieI-zv0Ui8nBlMzfnQ_mbT_M5evoEof6o-OZ5azA1nAyFvzyQAcQ$<https://urldefense.com/v3/__http:/localhost:8080/__;!!IZ3lH8c!yts7ZdG2lLWkLHZXnQFxUeyJeHbX_NxqieI-zv0Ui8nBlMzfnQ_mbT_M5evoEof6o-OZ5azA1nAyFvzyQAcQ$>
> but, when I click on "Server Status" I get the 401 Unauthorized page.
<snip/>
> I've been editing the conf\tomcat-users.xml file and have tried MANY
> different combinations of entries but, can't get past the 401 problem.
<snip/>
> Here's my current file contents:
>
> <?xml version="1.0" encoding="UTF-8"?>
>
> <tomcat-users
> xmlns=https://urldefense.com/v3/__http://tomcat.apache.org/xml__;!!IZ3lH8c!yts7ZdG2lLWkLHZXnQFxUeyJeHbX_NxqieI-zv0Ui8nBlMzfnQ_mbT_M5evoEof6o-OZ5azA1nAyFqswncMY$<https://urldefense.com/v3/__http:/tomcat.apache.org/xml__;!!IZ3lH8c!yts7ZdG2lLWkLHZXnQFxUeyJeHbX_NxqieI-zv0Ui8nBlMzfnQ_mbT_M5evoEof6o-OZ5azA1nAyFqswncMY$>
> xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance
> xsi:schemaLocation=http://tomcat.apache.org/xml
> tomcat-users.xsd<https://urldefense.com/v3/__http://tomcat.apache.org/xml*20tomcat-users.xsd__;JQ!!IZ3lH8c!yts7ZdG2lLWkLHZXnQFxUeyJeHbX_NxqieI-zv0Ui8nBlMzfnQ_mbT_M5evoEof6o-OZ5azA1nAyFtPXhfv-$<https://urldefense.com/v3/__http:/tomcat.apache.org/xml*20tomcat-users.xsd__;JQ!!IZ3lH8c!yts7ZdG2lLWkLHZXnQFxUeyJeHbX_NxqieI-zv0Ui8nBlMzfnQ_mbT_M5evoEof6o-OZ5azA1nAyFtPXhfv-$>>
> version="1.0">
If the above is what you actually have in the .xml file, you should also be
seeing parsing errors in the catalina.out log file, since it’s not valid XML.
Once corrected to the following, access to the server status pages worked
properly.
<tomcat-users
xmlns="https://urldefense.com/v3/__http://tomcat.apache.org/xml__;!!IZ3lH8c!yts7ZdG2lLWkLHZXnQFxUeyJeHbX_NxqieI-zv0Ui8nBlMzfnQ_mbT_M5evoEof6o-OZ5azA1nAyFqswncMY$<https://urldefense.com/v3/__http:/tomcat.apache.org/xml__;!!IZ3lH8c!yts7ZdG2lLWkLHZXnQFxUeyJeHbX_NxqieI-zv0Ui8nBlMzfnQ_mbT_M5evoEof6o-OZ5azA1nAyFqswncMY$>"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
xsi:schemaLocation="http://tomcat.apache.org/xml
tomcat-users.xsd<http://tomcat.apache.org/xml%20tomcat-users.xsd>"
version="1.0">
Note the missing quotes and seriously munged-up xsi:schemaLocation attribute in
your posting.
If you’re using an editor that thinks it’s clever to convert http:// references
into HTML, get a better editor.
- Chuck
CONFIDENTIALITY NOTICE: This e-mail message, including any attachments, is
for the sole use of the intended recipient(s) and may contain confidential
and privileged information or may otherwise be protected by law. Any
unauthorized review, use, disclosure or distribution is prohibited. If you
are not the intended recipient, please contact the sender by reply e-mail
and destroy all copies of the original message and any attachment thereto.
