Inaccurate 401 errors are being generated (invalid login credentials)

Shannon_W
Employee

Inaccurate 401 errors are being generated (invalid login credentials)

We are currently experiencing issues on our server that are causing a 401 (invalid credentials) response to go out, incorrectly.  We are currently investigating the cause of the issue, and hope to have it resolved as soon as possible.  

 

As a workaround for the moment, this appears to be happening for basic authentication users who do not have pre-emptive authentication turned on.  If you turn pre-emptive authentication on, the error should not occur.

 

Thank you for your patience while we resolve this issue.

 

 

Shannon W.

API Support Specialist

11 REPLIES 11
KevinZ24
Regular Participant

By pre-emptive authentication you mean pre-authenticating the HttpRequest, right? I used the statement request.PreAuthenticate = true; but I still got the error. Do you think this could be resolved by Monday?

Yes, that is what I meant, and I'm not sure why that didn't work, but the issue should be resolved now if you want to check.

 

Thanks!

Shannon W.

API Support Specialist

mitschj
Regular Participant

This is certainly an interesting development.  I have 5 clients using a basic authentication interface, all of which stopped working on 9/21/2012.  At first I was getting back the 401, but now I just get back empty response objects.  I realized Basic Authentication is being deprecated, but I have seen no announcement to say it should no longer work.  While I work to build an OAUTH2 replacement, it would be good if these kept working.  Adding PreAuthenticate to the HTTP Request was no help. Advice would be appreciated.

Hi,

 

There was a system issue which caused this; we certainly didn't mean to abruptly stop basic authentication integrations from working suddenly.  The issue should now be resolved.  Let us know if you are still seeing issues.

 

 

Best Regards,

Shannon W.

API Support Specialist

mitschj
Regular Participant

Thanks for the reassurance.  I eventually found the problem in my own code introduced while trying to resolve the earlier rejections.  All is better.

we are still getting these errors, has this been fully resolved?

Yes, this error was resolved later the same day we reported it.  Were you making successful calls previously, and have suddenly started getting 401 responses back with the same calls?  When did this start happening?

 

Best Regards,

Shannon W.

API Support Specialist

it's a new implementation using basic HTTPS, and we keep getting 401 errors.  i saw this post and thought maybe this was why.  what do you need from me to debug?

Hey,

 

This means that there is a problem with the credentials (username, password, API key, and/or access token) provided to Constant Contact. Depending on the type of authentication you are using, you will want to make sure the places your credentials are being stored have the right information. For basic authentication, you will want to use apiKey%username when providing your username to us. 

 

Are you using OAuth 2 for authentication?  

 

Best Regards,

Shannon W.

API Support Specialist

oddly enough, sometime between when i posted here and now, it has started working even though there were no code changes.  we are using https basic.

Hmm, most interesting.  Let me know if you see this behavior again.  Thanks for the update!

 

Best Regards,

Shannon W.

API Support Specialist

Developer Portal

View API documentation, code samples, get your API key.

Visit Page