HTTPS + Basic fails but HTTP + Digest Works for TEXARKMLS
User: retsbintz http://texarkmls-rets.paragonrels.com... with Digest auth connects successfully.
https://texarkmls-rets.paragonrels.co... with Basic auth returns a: 401 - Unauthorized: Access is denied due to invalid credentials.
We are trying to cutover to https for all of our Paragon RETS feeds but this is 1 of 2 that still give us problems.
Thanks.
Comments
Are the two that aren't working on the same servers as the ones that are working?
Only TEXARKMLS has this noted behavior for the account above. We see the same whether running in our AWS infrastructure or directly in Postman.
You said one of two above.
I assume that you have other's that are working correctly running from the same place?
What is the other one that isn't working?
Also what User-Agent value are you sending?
I should not have mentioned the other one--it was a deprecated feed due to merger. I was trying to steer back to the one having the issue. We have 15 other Paragon RETS feeds that are working over https on the same infra. TEXARKMLS is the only one exhibiting this behavior. "Python RETS" or whatever postman throws in there ("PostmanRuntime/7.29.2").
Do your other URLs all use rets-version=rets/1.8 too or can you try rets-version=rets/1.7.2?
No, it's a mix in the others: some 1.8, some 1.7.2, some 1.5.
Testing
rets/1.7.2(https://texarkmls-rets.paragonrels.co...) also failed with the credential issue.Is the case of the password exact?
Our Digest is a little more forgiving on case.
Yes, password was shared originally as all lower so as far as I am aware it is right.