Stream: crucible
Topic: No padlock icon seen
harini jagannathan (Mar 16 2017 at 16:17):
@Jason Walonoski - I checked out the DSTU2 branch and ran crucible using that against our DSTU2 FHIR server locally. I do not see a padlock icon to enter oauth information. Am I missing something? I see this error in my terminal where I run crucible:
harini jagannathan (Mar 16 2017 at 16:18):
Started GET "/servers/58c72a1268617236ba000000/conformance" for 127.0.0.1 at 2017-03-16 09:10:02 -0700
Processing by ServersController#conformance as JSON
Parameters: {"server_id"=>"58c72a1268617236ba000000"}
MOPED: 127.0.0.1:27017 QUERY database=crucible_development collection=servers selector={"_id"=>BSON::ObjectId('58c72a1268617236ba000000')} flags=[] limit=0 skip=0 batch_size=nil fields=nil runtime: 0.3900ms
GETTING: https://localhost:9443/fhir-server/api/v1/metadata
GETTING: https://localhost:9443/fhir-server/api/v1/metadata
GETTING: https://localhost:9443/fhir-server/api/v1/metadata
GETTING: https://localhost:9443/fhir-server/api/v1/metadata
GETTING: https://localhost:9443/fhir-server/api/v1/metadata
Completed 500 Internal Server Error in 113ms
JSON::ParserError (757: unexpected token at 'null'):
app/models/server.rb:196:in collect_supported_tests'
app/models/server.rb:64:inload_conformance'
app/controllers/servers_controller.rb:85:in `conformance'
Jason Walonoski (Mar 20 2017 at 17:34):
@harini jagannathan Have you looked at the README which explains how the authorization works? See https://github.com/fhir-crucible/crucible#authentication-with-scopes Let me know if that helps or not.
harini jagannathan (Mar 20 2017 at 17:36):
Hi Jason...yes, I have. We do support the SMART on FHIR authorization flows and have published those URLs in the conformance statement. But, as mentioned in the README, I do not see a padlock icon anywhere after I click "BEGIN".
harini jagannathan (Mar 20 2017 at 17:41):
Screen-Shot-2017-03-20-at-10.41.32-AM.png
Jason Walonoski (Mar 20 2017 at 17:54):
Our production instance of Crucible is prohibited from accessing localhost. I can't remember if that is the default behavior or not. Have you tried running on separate servers?
harini jagannathan (Mar 20 2017 at 17:57):
Ah ok! Haven't tried that yet...will do and get back on this. Thanks!
Brian Postlethwaite (Mar 20 2017 at 23:25):
Yes, that's because the tests are run from the server, and not the browser. So localhost isn't appropriate there.
harini jagannathan (Mar 21 2017 at 15:34):
Thanks for confirming, Brian! I will set up a remote server for this.
harini jagannathan (Mar 22 2017 at 17:21):
I set up a remote FHIR server instance and tried connecting to it with a Crucible server running on localhost. It's still failing with the same error.
Brian Postlethwaite (Mar 22 2017 at 21:06):
localhost is not an externally accessible address. You need to use a publicly accesible address for crucible to be able to connect to.
harini jagannathan (Mar 23 2017 at 18:45):
I am not using localhost anymore.
harini jagannathan (Mar 23 2017 at 20:19):
@Brian Postlethwaite - I tried connecting to a public FHIR server like the HAPI-FHIR. It seems to be working fine. Let me check what's blocking the connection to our FHIR server.
Last updated: Apr 12 2022 at 19:14 UTC
