<response>Bad username or password</response> during recon

golbiga
Contributor III
Contributor III

I've been seeing <response>Bad username or password</response> lately on a few machines when running recon and I was wondering what usually causes it? To fix it, I've had to run jamf removeFramwork and then recon on it, but I'm just wondering if there are any other fixes for this?

Thanks
allen

13 REPLIES 13

jarednichols
Honored Contributor

This error is thrown if the local admin account password is different from what the JSS expects it to be. We spin our passwords daily and run into this somewhat. Reset your admin account password on the local box to what it should be and you should be good to go.

j
---
Jared F. Nichols
Desktop Engineer, Client Services
Information Services Department
MIT Lincoln Laboratory
244 Wood Street
Lexington, Massachusetts 02420
781.981.5436

Matt
Valued Contributor

I had this same issue with a few machines. Never got an answer as to why this was happening.
--
Matt Lee
FNG Sr. IT Analyst / Desktop Architecture Team / Apple S.M.E / JAMF Casper Administrator
Fox Networks Group
matthew.lee at fox.com<mailto:matthew.lee at fox.com>

Need Help? Call the Help Desk at (310) 969-HELP (ext 24357) or online at http://itteam<http://itteam/>
Help Desk Hours: Mon-Fri, 6AM-6PM PST

golbiga
Contributor III
Contributor III

I've verified that the username and password on the machine were the same as the JSS. Only a removeFramework/quickadd ever seems to fix the issue.

Thanks
Allen

Not applicable

I've seen this a few times now with version 8 of Recon. This has never come up with previous versions of Recon. My fix (if you want to call it that) has been to just re-insert the credentials (I did notice for some reason the number of dots in the password were always one more than they should have been) and proceed to run recon. No issues thereafter.
This is spotty as the image is the same for all the units that get this issue and for those units that the issue has not come up for.

Jesus Ward Macintosh Desktop Support Administrator

Phone +1 212.631.3928 Fax 212-946-4010 Jesus.ward at rga.com

talkingmoose
Moderator
Moderator

We're still running 7.31 and see this every once in a while, usually where
On 6/8/11 9:52 AM, "Jesus Ward" <Jesus.Ward at rga.com> wrote:
multiple machines are receiving the same policy. The password is correct
in the JSS or else other things would have failed long ago and continued
failing.

It's an intermittent problem that I've attributed to something local to
the machine or maybe the communication between the machine and the JSS. We
don't spin passwords.

--

William Smith
Technical Analyst
Merrill Communications LLC
(651) 632-1492

donmontalvo
Esteemed Contributor II

We're seeing this error on some MacBook Air laptops we are imaging. We are running 8.43 and the hidden admin account password is fine on the workstation and server.

sudo jamf checkJSSConnection works fine but sudo jamf recon results in the below error. Was there every a fix for this?

$ sudo jamf recon

WARNING: Improper use of the sudo command could lead to data loss
or the deletion of important system files. Please double-check your
typing when using sudo. Type "man sudo" for more information.

To proceed, enter your password, or type Ctrl-C to abort.

Password:
Retrieving Inventory Preferences from https://servername:8443//...
Locating Hard Drive Information...
Locating Hardware Information (Mac OS X 10.7.3)...
Locating Applications...
Executing Unix Applications...
Locating Receipts...
Gathering Application Usage Information...
Finding Extension Attributes...
Submitting data to https://servername:8443//...
There was an error submitting the computer to the JSS. Here is what the JSS reported back:



<?xml version="1.0" encoding="UTF-8"?>
<jamfServlet version="8.43" server="Apache Tomcat/6.0.33">
<institution>MyCompany</institution>
<epoch>1335378415</epoch>

        <response>Bad username or password</response>

<sessionLastError></sessionLastError>
</jamfServlet>




$
--
https://donmontalvo.com

jarednichols
Honored Contributor

What happens if you disable certificate-based verification?

donmontalvo
Esteemed Contributor II

@jarednichols I'm fairly sure you don't mean disabling the certificate on the server? Right now we have a signed certificate on the server and imaging MacBook Pro laptops hasn't been a problem, just the MacBook Air laptops. The USB/Ethernet adapter isn't (yet) set up as a Removable MAC Address.

As a test I ran our QuickAdd (created using the 8.43 Recon application to match the server) and got the same error when trying to run Recon.

Don

--
https://donmontalvo.com

stevewood
Honored Contributor II
Honored Contributor II

In the past, anytime I've seen this the only resolution I've found is to push a QuickAdd against the machine. If that doesn't work, try removing the framework first (jamf removeFramework) and then push the QuickAdd.

Steve

donmontalvo
Esteemed Contributor II

@stevewood That did the trick. I ran sudo jamf removeFramework and then ran the QuickAdd and it's fine now.

--
https://donmontalvo.com

bentoms
Release Candidate Programs Tester

Don, check the 8.51 release notes.. I think that fixed it.

donmontalvo
Esteemed Contributor II

@bentoms Man you guys are friggin awesome...we are at 8.43 and having thought of moving up since nothing was broken...well...that changes now. :D:D:D

--
https://donmontalvo.com

bentoms
Release Candidate Programs Tester

Ha ha. Thank JAMF!!