Backend system auth

[Sandip Gupta]

We are developing a system to system integration between our backend and Dr Chrono and other EMRs. We need our backend process to authenticate to Dr Chrono. The documentation discusses redirecting to an online login screen for user to sign-in. 

Has anyone established a mechanism for backend to authenticate - like a client token and secret?

CONFIDENTIALITY NOTICE: This electronic mail transmission and any accompanying documents contain information belonging to the sender which may be confidential and legally privileged. This information is only for the use of the individual or entity to whom this electronic mail transmission was intended. If you are not the intended recipient, any disclosure, copying, distribution, or action taken in reliance on the contents of the information contained in this transmission is strictly prohibited. If you have received this transmission in error, please immediately contact the sender and delete the message. Thank you.

[Briggs McKnight]

Hey Sandip,

Currently we do not have a way to connect to the DrChrono API that doesn't involve the redirect to our login UI. You will have to initially connect via this authorization process to obtain access tokens to make requests to the API. Once you have acquired tokens, you can make use of refresh tokens to keep a continuous connection to the API active, without the use of any UI. The authorization process, as well as refresh tokens, is documented here: https://app.drchrono.com/api-docs/v4/documentation#.

Let me know if you any further questions,

Briggs

--
You received this message because you are subscribed to the Google Groups "DrChrono API Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to drchrono-api...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/drchrono-api/7b070183-2ed8-4f7c-99f8-2eeadf59c2da%40googlegroups.com.

--

Briggs McKnight / API Support Specialist 

904-206-3978 / bri...@drchrono.com

[g krum]

Hi Briggs,

I'm new to Dr. Chrono and working on a backend service integration as Sandip was.  Working through documentation and tutorials and am concluding that your response to Sandip still stands 10 months later?  I don't see any updates to this thread and it appears there is still no way to simply call for an access token and refresh with client ID and secret without first going through a manual auth/login step.

thanks,

Gregg

[bri...@drchrono.com]

That is correct, we still only provide the OAuth process that requires UI login. We don't have any plans to change this in the near future.

[Blake Hull]

Hey folks, just wanted to follow up here 4 years later to ask the same question:

any plans to provide client credentials flow or MTLS so we can develop M2M apps? Even having this locked down to only `get` calls could be helpful.

Thanks!
Blake

[Edmilson100%]

ok.

To view this discussion visit https://groups.google.com/d/msgid/drchrono-api/e8c98ee7-c391-43ef-aeb0-4957fb269fd6n%40googlegroups.com.

[DrChrono API Developers]

Hi,

DrChrono does not have current plans for M2M or similar. I am happy to provide feedback for the team.

Best,

Assaad