search

smart-classic / smart_server

SMArt Bootstrap Server
Apache License 2.0
22 stars 10 forks source link

oauth: can't login with demouser after auto install #7

Closed arjunsanyal closed 12 years ago

arjunsanyal commented 12 years ago 
setting path /accounts/{user_id}/apps/{smart_app_id}/preferences <smart.client.common.rdf_ontology.SMART_API_Call object at 0x1039a7650>
setting path /records/{record_id}/allergies/ <smart.client.common.rdf_ontology.SMART_API_Call object at 0x1039c5bd0>
setting path /records/{record_id}/problems/ <smart.client.common.rdf_ontology.SMART_API_Call object at 0x1039bedd0>
Permission denied for  session_create None
[11/Apr/2012 15:02:56] "POST /oauth/internal/session_create HTTP/1.1" 403 26
2012-04-11 19:02:56,408 DEBUG 

>>> error: likely a bad username/password, or incorrect tokens from UI server to backend server.

[11/Apr/2012 19:02:56] "POST /login HTTP/1.1" 200 3637
jmandel commented 12 years ago

...pretty hard to debug this from that error message. Can you confirm the demo user for created by running a django shell on smart_server? Ditto for the chrome user... On Apr 11, 2012 3:03 PM, "Arjun Sanyal" < reply@reply.github.com> wrote:

setting path /accounts/{user_id}/apps/{smart_app_id}/preferences <smart.client.common.rdf_ontology.SMART_API_Call object at 0x1039a7650> setting path /records/{record_id}/allergies/ <smart.client.common.rdf_ontology.SMART_API_Call object at 0x1039c5bd0> setting path /records/{record_id}/problems/ <smart.client.common.rdf_ontology.SMART_API_Call object at 0x1039bedd0> Permission denied for session_create None [11/Apr/2012 15:02:56] "POST /oauth/internal/session_create HTTP/1.1" 403 26 2012-04-11 19:02:56,408 DEBUG

error: likely a bad username/password, or incorrect tokens from UI server to backend server.

[11/Apr/2012 19:02:56] "POST /login HTTP/1.1" 200 3637

Reply to this email directly or view it on GitHub: https://github.com/chb/smart_server/issues/7

arjunsanyal commented 12 years ago

Ok, it's working now. It looks like the create_user script failed (but I thought it was successful) due to another error upstream (the case of the missing libxslt). Once that was fixed and the script re-run, hello demouser. I'm all installed now and am looking at apps.

I'm thinking of doing a branch and pull request removing the libxslt refs. What do you think?

jmandel commented 12 years ago

Go ahead with the pull request (against dev please) if you can hack out the dependency (which I believe is only vestigial at this point).

(Not sure if we even need a pure python alternative -- if so there is elementtree.) On Apr 11, 2012 4:41 PM, "Arjun Sanyal" < reply@reply.github.com> wrote:

Ok, it's working now. It looks like the create_user script failed (but I thought it was successful) due to another error upstream (the case of the missing libxslt). Once that was fixed and the script re-run, hello demouser. I'm all installed now and am looking at apps.

I'm thinking of doing a branch and pull request removing the libxslt refs. What do you think?

Reply to this email directly or view it on GitHub: https://github.com/chb/smart_server/issues/7#issuecomment-5078453

arjunsanyal commented 12 years ago

Will do. I agree, we won't need to replace libxslt right now, but it we do need XSLT, XPath, etc support, I'd recommend lxml.