The problem is that instead of the plain-text password in the query params, we require a string representation of the binary-encoded encrypted password.  Our DB guru has provided this query to easily figure out what that is.  If you run this query against your WhatsUp DB, you'll get the info you need.

DECLARE @StartVarBin VARBINARY(MAX)
SET @StartVarBin = (SELECT sPassword FROM dbo.WebUser WHERE sUserName = 'guest')


-- Parsing Variables
DECLARE @StartVarBinText VARCHAR(MAX)
DECLARE @CurrentLocation INT
DECLARE @List VARCHAR(MAX)
DECLARE @CurrentText VARCHAR(2)
DECLARE @CurrentHex VARBINARY(2)

-- Declare starting points
SET @StartVarBinText = (SELECT '0x' + CAST('' AS XML).value('xs:hexBinary(sql:variable("@StartVarBin") )', 'VARCHAR(MAX)'))
SET @CurrentLocation = 3
SET @List = ''

-- Cycle though digits
WHILE @CurrentLocation < LEN(@StartVarBinText)
BEGIN
      SET @CurrentText = SUBSTRING(@StartVarBinText, @CurrentLocation, 2)
      SET @CurrentHex = (SELECT CAST('' AS XML).value('xs:hexBinary( substring(sql:variable("@CurrentText"), 0) )', 'VARBINARY(MAX)'))
      SET @List = @List + (CAST(CONVERT(INT, @CurrentHex) AS VARCHAR(10))) + ','
      SET @CurrentLocation = @CurrentLocation + 2
END

-- Remove last comma
SET @List  = LEFT(@List, LEN(@List) - 1)

-- Return results
SELECT @StartVarBin, @List

This will return a field that's a comma-separated string value of the password field. It will look something like 2,0,0,16,0,5,240,112,24,...,212 (none of those numbers will necessarily be there, it will just be a similar format).
You can then use that as the value for "sPassword" in your query and have auto-login work.

Your URL will then be something like http://nms:82/NmConsole/DeviceManagement/DeviceList/DeviceList.asp?DeviceList.nDeviceGroupID=71?sUsername=guest&sPassword=2,0,0,16,0,5,240,112,24,...,212

Be careful who you give those URLs out to, because they can just use that same sUserName and sPassword information to reach any page that user has access to.

The line breaks in this forum make that fairly unreadable, but if you copy and paste the query into a text editor it should restore the proper line breaks.

Thanks for your response Jeremy. I followed these instructions, but still get challenged for login when I use that link. I tried IE and Firefox, same results.

i can say, that the old autologin does work in 15.0.1. we have never changed the url since release 11 and it does still work with cleartext username and password.

Georg thanks for your post.

After you pointed this out, I did some testing and realized plain text autologin works when the landing page is one of the 'home' pages. I have been trying to use one of the 'devices' pages as a landing. I am not sure if this is a bug or by design.

I woudl still prefer this user to land in a devices group, but I can live with this; I created a custom 'home' page for him to land on.

Does the user have rights to that group?  If the user doesn't have explicit group access rights (assuming group access rights are enabled) he'll be sent to the login screen anyway.  I know for sure that the autologin works as I described, as its usage is central to our PDF export functionality.