FHIR Chat · invalid scope · smart

Stream: smart

Topic: invalid scope


view this post on Zulip David Hay (Dec 18 2017 at 21:17):

I'm accessing the sandbox at: https://sb-fhir-stu3.smarthealthit.org/smartstu3/data as a confidential client in standalone launch sequence.

It's all working fine, but when I request a scope of patient/*.read I get an 'invalid scope' error. A scope of patient/*.* is fine. I appreciate that this is legal - the server is saying that it won't grant read-only access - but is it deliberate?

view this post on Zulip Josh Mandel (Dec 18 2017 at 21:46):

Some funny formatting here @David Hay (you can use back-quotes to avoid having zulip clobber by interpreting your * as formatting). @Dan Gottlieb can you comment on this sandbox behavior?

view this post on Zulip David Hay (Dec 18 2017 at 21:47):

oops - sorry about that :) fixed...

view this post on Zulip David Hay (Dec 18 2017 at 21:55):

btw - not infrequently getting an error: Request method 'POST' not supported plus stack trace - after I "authorize an app until revoked"...

view this post on Zulip David Hay (Dec 18 2017 at 21:58):

actually, it's consistently with this scope: openid profile patient/*.*

view this post on Zulip Dan Gottlieb (Dec 18 2017 at 22:51):

I'm not getting the scope error, but am hitting the stack trace after authorizing on every request - not sure if these are related. @Travis Cummings is following up on the errors now. @David Hay- can you use https://launch.smarthealthit.org to test your app?

view this post on Zulip David Hay (Dec 18 2017 at 22:55):

Hi Dan - about to go into a meeting, but will do so in an hour. Actually - right now it's still working (if I avoid that scope)...

view this post on Zulip Dan Gottlieb (Dec 18 2017 at 23:04):

Interesting, I'm still getting the stack trace. In any case, patient/*.read should be a valid scope, so it's odd that it's erroring...

view this post on Zulip Dan Gottlieb (Dec 18 2017 at 23:16):

One other thought - in the sandbox, I think the scopes the app was registered with have to match the scopes the client is requesting. Any chance that's the issue?


Last updated: Apr 12 2022 at 19:14 UTC