First time here? Check out the FAQ!
0

Credentials not being passed out of the blue - 401 error

Nothing changed on our end. We use vielerets to pull data. Here is a batch log file:

Debug Output for VieleRETS


[December 13, 2018 16:07:01 UTC] CREATE new Request for INITIAL_LOGIN

[December 13, 2018 16:07:01 UTC] SET socket - failed

[December 13, 2018 16:07:01 UTC] SET cookies - failed

[December 13, 2018 16:07:01 UTC] SET credential failed because no credential is present

[December 13, 2018 16:07:01 UTC] READ as an XML formatted stream

[December 13, 2018 16:07:01 UTC] OPENING socket for Request on cwbr.rets.fnismls.com 80

[December 13, 2018 16:07:02 UTC] SUCCESS on open

[December 13, 2018 16:07:02 UTC] SENDING ...

POST /rets/fnisrets.aspx/CWBR/login HTTP/1.1

Host: cwbr.rets.fnismls.com:80

Accept: /

User-Agent: Paragon/1.1.8

Date: Thu, 13 Dec 2018 16:07:01 GMT

RETS-Request-ID: U571

RETS-Version: RETS/1.7.2

Pragma: no-cache

Content-Type: application/x-www-form-urlencoded

Content-Length: 21

rets-version=rets/1.5

[December 13, 2018 16:07:03 UTC] RESPONSE ...

HTTP/1.1 401 Invalid Username/Password combination

Cache-Control: private

Content-Type: text/html

Expires: Mon, 01 Jan 0001 00:00:00 GMT

RETS-Server: RETS-Paragon/1.0

RETS-Request-ID: U571

RETS-Version: RETS/1.7.2

WWW-Authenticate: Digest qop="auth",realm="CWBR",nonce="2018-12-13T16:17:02",opaque="",stale="false",domain="\rets\fnisrets.aspx\CWBR"

Set-Cookie: RMLS%5FSESSION%5FGUID=; path=/RETS/

Set-Cookie: RMLS%5FSESSION%5FLAST%5FDBUPDATE=; path=/RETS/

Set-Cookie: RMLS%5FSESSION%5FLAST%5FUPDATE=; path=/RETS/

Set-Cookie: RMLS%5FSESSION%5FTIMEOUT=; path=/RETS/

X-SERVER: A52

Date: Thu, 13 Dec 2018 16:07:02 GMT

Content-Length: 1293

Vary: Accept-Encoding

[December 13, 2018 16:07:03 UTC] READING the PAYLOAD with Content-Length

[December 13, 2018 16:07:03 UTC] PAYLOAD ...

<html xmlns="http://www.w3.org/1999/xhtml">

<head>

<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1"/>

<title>401 - Unauthorized: Access is denied due to invalid credentials.</title>

<style type="text/css">

</style>

</head>

<body>

Server Error

<fieldset>

401 - Unauthorized: Access is denied due to invalid credentials.

You do not have permission to view this directory or page using the credentials that you supplied.

</fieldset>

</body>

</html>

[December 13, 2018 16:07:03 UTC] GENERATE a credential

[December 13, 2018 16:07:03 UTC] OPENING socket for Request on cwbr.rets.fnismls.com 80

[December 13, 2018 16:07:03 UTC] Socket already open for Request on cwbr.rets.fnismls.com 80

[December 13, 2018 16:07:03 UTC] SENDING ...

POST /rets/fnisrets.aspx/CWBR/login HTTP/1.1

Authorization: Digest username="taagteam", realm="CWBR", nonce="2018-12-13T16:17:02", uri="/rets/fnisrets.aspx/CWBR/login", qop="auth", nc=00000001, cnonce="0a4f113b", response="83002e0dee5d656b3f572d5f157995fa", opaque=""

Host: cwbr.rets.fnismls.com:80

Accept: /

User-Agent: Paragon/1.1.8

Date: Thu, 13 Dec 2018 16:07:03 GMT

RETS-Request-ID: U571

RETS-Version: RETS/1.7.2

Cookie: RMLS%5FSESSION%5FGUID=; path=/RETS/

Cookie: RMLS%5FSESSION%5FLAST%5FDBUPDATE=; path=/RETS/

Cookie: RMLS%5FSESSION%5FLAST%5FUPDATE=; path=/RETS/

Cookie: RMLS%5FSESSION%5FTIMEOUT=; path=/RETS/

Pragma: no-cache

Content-Type: application/x-www-form-urlencoded

Content-Length: 21

rets-version ... (more)

cwbrmls's avatar
cwbrmls
asked 2018-12-13 13:37:56 -0500
edit flag offensive 0 remove flag close merge delete

Comments

add a comment see more comments

1 Answer

0

Please Change Domain in RETS URL From: "fnismls.com" To: "paragonrels.com".
This should be working now.
Please verify it is working and comment this answer.

bwolven's avatar
bwolven
answered 2018-12-13 13:43:56 -0500, updated 2018-12-13 14:36:08 -0500
edit flag offensive 0 remove flag delete link

Comments

SUCCESS!!!!!!!!!!!!!!!!!!! Yahoooooooooo! Thank you so much!

cwbrmls's avatar cwbrmls (2018-12-13 15:18:40 -0500) edit

Glad to hear that.
Please be sure to change the domain in your URL if you haven't already.
The fnismls.com domain is legacy and will probably go away sometime in the future.

bwolven's avatar bwolven (2018-12-13 15:30:55 -0500) edit
add a comment see more comments

Your Answer

Login/Signup to Answer