[thredds] Hashed password for tomcat-users.xml is not consistent so unable to login

  • To: "thredds@xxxxxxxxxxxxxxxx" <thredds@xxxxxxxxxxxxxxxx>
  • Subject: [thredds] Hashed password for tomcat-users.xml is not consistent so unable to login
  • From: "Vu , Long" <vu.long@xxxxxxxxxx>
  • Date: Fri, 20 Sep 2019 16:13:12 +0000
  • Arc-authentication-results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=ouranos.ca; dmarc=pass action=none header.from=ouranos.ca; dkim=pass header.d=ouranos.ca; arc=none
  • Arc-message-signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=SHjBhHzGe27TVIhVdpQzL7mr92CE2hskAYiXpQMfW50=; b=TkXX9FXhkWKmD6Ss/46OZkcm+URya1T1N6cAJzkv22JzwZLYjhhBiMewIyHWW9Kt1lv01gMRFhfaiuyE0rzV9/dji7HFNi22AJSC62SRfLIlJM0Ur0T9kzD1EA4x2xtMhqzcJPS9sQvzRV4aC8ktSx+mGIp7CxEwuTL5svvjTA3PHn9I2VetGkyMtyw7CemjmK+Ap8AbEg85i//gf9ZJ6e5nSdnuVfAttBXVr/+u/Jj7nfEd+yYuWesHqjjNJ6T8rAFSu6HXo3O2mb5mBilxVRj+B9NSF0+/P1XE0W3devY9DrlN1HF5NOYAU3oL7IZ8RoxG93wViSgXbGjLUifGMw==
  • Arc-seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=HA+Gjs8ltyxiazfSm3RUVbvM2sVCxofKLqYlI4ugSAxdoE10Knjks7Tx80TCxi3Ra6s1CyRSVnmAAHj7GL8WjeHOCqrcC3YaPx1QI7/XAsQbpFHZFeKF2JyoBj8lhJCbWGTdeavBOgsHaynZyV4t9iQ51llTcwUguesip/4b0oz8rQSA4Ln0qHOtXEGdIRoff4Vf4ouYpPupB2lLfL+CAc9xwo1kW2dgLDzsuKLU8i8cNiE/RUa1Ns55C96MdVufR1736Do+xn7XxwbzL9GtR/WgZy1HN6h6uVXxiJTkQI8JukNL9O0a45pL8mj+Ye2/aWEDf0owFvYXy5BMpwAaQA==
  • Authentication-results: spf=none (sender IP is ) smtp.mailfrom=vu.long@xxxxxxxxxx;
Hi,

I followed instructions here 
https://github.com/Unidata/thredds-docker#h20B33C74 which leads to here 
https://github.com/Unidata/tomcat-docker#digested-passwords.

As you can see below, I tried to hash "admin" 4 times and "super" 3 
times and I am getting completely different result each time.

Consequently I am unable to login to http://<my 
host>:8080/thedds/admin/debug with the password I have chosen because 
probably the hash calculated on server side is different so the 2 hashes 
did not match !

What did I do wrong so I should log a bug for this?

11:47 $ docker run unidata/thredds-docker:4.6.14 
/usr/local/tomcat/bin/digest.sh -a "SHA" admin
admin:7e7e81ea10686b0648bffa9edafd0b7f60eacc5145d97dd1d357cbc193060aed$1$ab2c3ddcb23f65a9b6e3f204958dd463336c283f

12:00 $ docker run unidata/thredds-docker:4.6.14 
/usr/local/tomcat/bin/digest.sh -a "SHA" admin
admin:8446588eec143b0decac02be49993bcc56e4b16a4187ce15a2727f267d7f1306$1$e771b647858a86ff580290077b5df357f5c20650

12:00 $ docker run unidata/thredds-docker:4.6.14 
/usr/local/tomcat/bin/digest.sh -a "SHA" admin
admin:ee16b99f11c0eeba71a6a821fba1e8b09f273ab032c13d2ce7ec5eeab2a1e7cc$1$bab5606e5cbb0ae1bca38c0f5bd15d656fe72085

12:00 $ docker run unidata/thredds-docker:4.6.14 
/usr/local/tomcat/bin/digest.sh -a "SHA" admin
admin:4ec71242066de4912869026a017f7ebeb59bdaec4de40ba8ac9ff694229c2084$1$a0c61f7703b080e3bcfcdb2579854df45d2abcdd

12:00 $ docker run unidata/thredds-docker:4.6.14 
/usr/local/tomcat/bin/digest.sh -a "SHA" super
super:f423f534302461b1829891a2e1fcdbf7ffa2c06721a51b3b12cd70695ce4cdec$1$cc6c5d231b0f522c20606139619052fba3f5a257

12:01 $ docker run unidata/thredds-docker:4.6.14 
/usr/local/tomcat/bin/digest.sh -a "SHA" super
super:eace3dbabc0275bd6f5a745eb55b3e3de729e8d835882e4469d066eae1a19f9d$1$7f3e8561201bdac50e328dbc89f9383b5d26d47a

12:01 $ docker run unidata/thredds-docker:4.6.14 
/usr/local/tomcat/bin/digest.sh -a "SHA" super
super:afc94d3d0885e8e81cc02ba26642085563a3edb3f375afe2c0f92068b43610b9$1$b6c57eae754e062469887ecc101df9adbe1a404d
  • 2019 messages navigation, sorted by:
    1. Thread
    2. Subject
    3. Author
    4. Date
    5. ↑ Table Of Contents
  • Search the thredds archives: