Automating a login/authentication issue for unit testing

[D C]

Hello,

I am having an issue with creating an automated login test using Selenium for test automation.  The error that I am receiving is "We can't process your request at this time.

Try logging into your account later.".  I have seen some other posts with this same process and error and the response has been to space out your logins to ensure that the security of Medicare.gov doesn't assume you are a bot to protect potential spamming.  However, I am only making this call once just to get a single authorization code and refresh token to ensure that my OAuth code is correct.  I am not running this multiple times.

I have also receive this error using Insomnia (a more lightweight version of Postman) when running through the authorization flow.

Is there a particular header that I need to include (or anything else in my request) to ensure that my logins don't get blocked (assuming that's what's happening)?

Thank you,

Dan

[Kirsten Hansen]

Hi Dan,

I sent you an email to follow up on this issue. Please check your inbox.

Thanks,

Kirsten Hansen

Product Manager

The Blue Button 2.0 API Team

[Fatih Cekic]

Hi Kristen,

I am having the same problem so if you can help me I will appreciate it.

" Hello,

I am having an issue with creating an automated login test using Selenium for test automation.  The error that I am receiving is "We can't process your request at this time.

Try logging into your account later.".  I have seen some other posts with this same process and error and the response has been to space out your logins to ensure that the security of Medicare.gov doesn't assume you are a bot to protect potential spamming.  However, I am only making this call once just to get a single authorization code and refresh token to ensure that my OAuth code is correct.  I am not running this multiple times.

Is there a particular header that I need to include (or anything else in my request) to ensure that my logins don't get blocked (assuming that's what's happening)?  "

Thanks 

Fatih

[Kirsten Hansen]

Hi Fatih,

Blue Button 2.0 relies on the Medicare.gov login system for authentication. Unfortunately, our team (Blue Button 2.0) does not manage the access or rules around automated testing on the Medicare.gov environments. We’ve had API users come to us in the past with this same issue and have determined it is due to automated bot-detection in place for Medicare logins. We don’t currently have a workaround for this, but we are discussing internally what might be done to allow our users to set up automated tests for their applications. We will reach out if there are any workarounds.

Thanks for your understanding and please reach out if you need additional support.

Kirsten Hansen

Product Manager

The Blue Button 2.0 API Team

[Fatih Cekic]

I truly appreciate your time and effort to help us. Thanks for your response!