Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Does anyone know why the api LoginPublisherAccountByName always return a default session id #57

Open
stephanie-miao opened this issue Oct 8, 2022 · 5 comments

Comments

@stephanie-miao
Copy link

Does anyone know why the api "LoginPublisherAccountByName" always return a default session id --- like this "00000000-0000-0000-0000-000000000000", thx

@chrisgibson41
Copy link

I'm getting the same. I'm wondering if dexcom have moved this apps registered id back into a sandbox account?

@stephanie-miao
Copy link
Author

I'm getting the same. I'm wondering if dexcom have moved this apps registered id back into a sandbox account?

I figured out the reason, you should use ShareWebServices/Services/General/AuthenticatePublisherAccount with accountName as params to get the account_id first, then use LoginPublisherAccountById to with account_id as param to get the session id. Seems LoginPublisherAccountByNameis no longer avaiable

@chrisgibson41
Copy link

Ah nice!

So basically post request - /ShareWebServices/Services/General/AuthenticatePublisherAccount

with the body - {
"accountName": "dexcom-user",
"applicationId": "d89443d2-327c-4a6f-89e5-496bbb0317db",
"password": "dexcom-pass"
}

Weirdly getting an unhelpful 400 response. Is there something im missing?

@stephanie-miao
Copy link
Author

Seems your body and the url are the same as mine. However I am using the applicationId as d8665ade-9673-4e27-9ff6-92db4ce13d13, this point is different

@bewest
Copy link
Member

bewest commented Nov 18, 2022

@chrisgibson41, @stephanie-miao Thanks for adding notes here. Where are you located? There have been several changes to the Dexcom "cloud" ecosystem over the last 2 years with several more changes coming as G7 rolls out all over the world and eventually. While there are plans at Dexcom for G7 and G6 backwards compatibility as a unified system, the measures we have historically used to access data are unique to G6 and previous versions, including Dexcom Share authentication.

Where are you located, and is G7 active in your region?
Are you using "dependent" accounts for people under 21, 18, 13, or another age of designation in your region?
Have you tried switching to "the other" server?

Thanks for exchanging notes. I hope we can continue to establish consistent and reliable connectivity.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants