any restrictions on redirect_uri for oauth2?

44 views
Skip to first unread message

Gary Pinkham

unread,
Mar 23, 2017, 4:03:50 PM3/23/17
to SMART on FHIR
signed up to use the sandbox a few hours ago and have not had any luck getting the step one in the oauth2 chain to work..   I keep getting invalid_client..     I'm using a local nodejs server (so the redirect is http://localhost:9000/callback).     I've used quite a few oauth2 providers (even wrote one) so I'm mostly sure I have this right: "https://open-ic.epic.com/Argonaut/oauth2/authorize?redirect_uri=https%3A%2F%2Flocalhost%3A9000%2Fcallback&response_type=code&client_id=FOO"    I'm thinking that even though the client app sign up page allowed me to enter http://localhost that the actual authorization server is rejecting it (I have had issues with https and a few providers in the past)    Just trying to poke around the API so I'd really love to get passed step 1 :-)   So any feedback would be greatly appreciated!

thanks in advance
Gary

Travis Cummings

unread,
Mar 23, 2017, 6:06:56 PM3/23/17
to Gary Pinkham, SMART on FHIR
Hi Gary,

Did you intend to send this message to the Epic support forum?

Thanks,
Travis

--
You received this message because you are subscribed to the Google Groups "SMART on FHIR" group.
To unsubscribe from this group and stop receiving emails from it, send an email to smart-on-fhi...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Reply all
Reply to author
Forward
0 new messages