James, > Am 07.01.2020 um 03:11 schrieb James H. H. Lampert <jam...@touchtonecorp.com>: > > Dear Mr. Schultz, et al.: > > The manager password on this Tomcat server has an embedded curly brace, and > an embedded question mark. > > If I do this (the names have been changed to protect the innocent, and the > -k!) > >> curl -k >> "https://foo:b?a{r@localhost:8443/manager/jmxproxy?invoke=Catalina%3Atype%3DProtocolHandler%2Cport%3D8443%2Caddress%3D%22127.0.0.1%22&op=reloadSslHostConfigs" > > I get curl: (3) [globbing] unmatched brace in column xx > > If I change the curly brace to "%7B," I get: > >> curl -k >> "https://foo:b?a%7Br@localhost:8443/manager/jmxproxy?invoke=Catalina%3Atype%3DProtocolHandler%2Cport%3D8443%2Caddress%3D%22127.0.0.1%22&op=reloadSslHostConfigs" > > I get curl: (3) Port number ended with 'n' > > And if I put the user-ID and password in with a -u clause on curl, rather > than in the URL itself, I get "Unauthorized." > > What is wrong here? Are there characters it simply can't tolerate in > passwords, even if URL-escaped?
I‘d prefer them in -u. for separation of concerns, add a separate user with a longer one and shell friendly password only with the role below... > Or do I need to give the manager user an additional role? Currently, I have: > <user username="foo" password="b?a{r" roles="manager-gui"/> manager-jmx (and maybe for other script-actions manager-script) Peter > -- > JHHL > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org > For additional commands, e-mail: users-h...@tomcat.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org