On 9 Sep 2015 17:59, "Christopher Schultz" <ch...@christopherschultz.net>
wrote:
>
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA256
>
> Andrew,
>
> On 9/8/15 9:21 AM, Andrew M wrote:
> > Any idea why it is saying "401 Unauthorized"
>
> > I execute the following command: curl -1 --max-time 10 -s -k -u
> > tomcat_jmx:'eyFW$&$FvSIp#FUk' --url
> > https://pentagon505:8443/deploy/jmxproxy?
>
> Your shell may do something odd with a partially-quoted
> username/password argument. Try this:
>
> $ curl -1 --max-time 10 -s -k \
>     -u 'tomcat_jmx:eyFW$&$FvSIp#FUk' \
>  --url https://pentagon505:8443/deploy/jmxproxy?
>

Can you post your <Realm> information? Your password does not match. You
did not provide proper user/pass combination, i.e. did not properly
authenticate, hence 401 error.

> > I have added the user to tomcat-users.xml configuration file as
> > well <role rolename="manager-gui"/>  <user username="tomcat"
> > password="pass1!" roles="manager-gui"/>   <role
> > rolename="manager-jmx"/>  <user username="tomcat_jmx"
> > password="passwords!@#" roles="manager-jmx"/></tomcat-users>
>

> The #1 error with tomcat-users.xml is forgetting to un-comment the
> block of XML.
>
> > Please note that I am executing the command from a remote server:
>
> > Complete output is as follows:<!DOCTYPE html PUBLIC "-//W3C//DTD
> > HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd";><html>
> > <head> <title>401 Unauthorized</title>  <style type="text/css">
> > <!-- BODY
> > {font-family:Tahoma,Arial,sans-serif;color:black;background-color:whit
> e;font-size:12px;}
> >
> >
> H1
> > {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525
> D76;font-size:22px;}
> >
> >
> PRE, TT {border: 1px dotted #525D76}    A {color : black;}A.name
> > {color : black;}    -->  </style> </head> <body>   <h1>401
> > Unauthorized</h1>   <p>    You are not authorized to view this
> > page. If you have not changed    any configuration files, please
> > examine the file    <tt>conf/tomcat-users.xml</tt> in your
> > installation.
>
> That sure looks like a failure to authenticate, coming from Tomcat.
>

+1

Reply via email to