MMConnect is not working in EU due to EU CareLink service changes (28.06.2020)

[benceszasz]

Hi!

There was a major upgrade in EU CareLink services (28.06.2020) and since then MMConnect module is not working anymore in EU.

Login changed
https://carelink.minimed.eu/patient/j_security_check?j_username=&j_password= throws HTTP 400
EU CareLink seems to using now the following service for logins:
https://mdtlogin.medtronic.com/mmcl/auth/oauth/v2/authorize/login

Dataservice changed
https://carelink.minimed.eu/patient/connect/ConnectViewerServlet?cpSerialNumber=NONE&msgType=last24hours&requestTime= throws HTTP 404
EU CareLink connect webapplication seems to be using the following service to fetch SGV values:
https://carelink.minimed.eu/patient/connect/data?cpSerialNumber=NONE&msgType=last24hours&requestTime=

The returned SGV data seems to be the very same JSON as earlier
lastSensorTSAsString
bgunits
lastSensorTS
...
lastSGTrend
lastSG{}
lastAlarm{}
activeInsulin{}
sgs[]
limits[]
markers[]

Could you please change the MMConnect module to support the new EU CareLink Connect services?

Thank you!

[bewest]

Yes, let's see what we can do.

[bewest]

Were you able to see if the cookie name is the same, or if there is possibly a different token used? If I post to a branch/fork somewhere are you able to test? @benceszasz, are you available for chat/test on some platform? Email me at bewest at gmail.

[raferg]

FWIW I'm potentially available to help with any final end-end testing - I'm running a herokuapp for my data through the eu minimed site.

[idowolf]

FWIW I'm potentially available to help with any final end-end testing - I'm running a herokuapp for my data through the eu minimed site.

Hi @raferg, I tried deploying your solution to my Nightscout installation but I get the following error when attempting to get data from Carelink:

2020-07-02T09:58:08.422869+00:00 app[web.1]: Thu Jul 02 2020 09:58:08 GMT+0000 (Coordinated Universal Time) Logging in to CareLink
2020-07-02T09:58:08.423034+00:00 app[web.1]: Thu Jul 02 2020 09:58:08 GMT+0000 (Coordinated Universal Time) POST https://mdtlogin.medtronic.com/mmcl/auth/oauth/v2/authorize/login
2020-07-02T09:58:08.774776+00:00 app[web.1]: MiniMed Connect error: Error [ERR_TLS_CERT_ALTNAME_INVALID]: Hostname/IP does not match certificate's altnames: Host: carelink.minimed.eu. is not in the cert's altnames: DNS:mdtlogin.medtronic.com, DNS:mdtsts.medtronic.com

Is there anything that can be done about this?

[raferg]

@idowolf follow the nightscout/minimed-connect-to-nightscout#1 link those solutions do work

[bewest]

Please see nightscout/cgm-remote-monitor#5725 for getting hotfix for cgm-remote-monitor.