oada-ref-auth-js problem

31 views
Skip to first unread message

Weipeng Chen

unread,
Mar 7, 2016, 2:01:00 AM3/7/16
to OADA Developers Group
Hi All,
I am one of Oregon State University Computer Science Capstone Team members. Our team need to understand the OADA in order to finish our senior project.
When I try to test the "oada-ref-auth-js" in my local pc, I followed the instructions in the github showed. When I run "node index.js", and then I go to the URL "https://localhost:3000/login" and other endpoints by Chrome, it just showed "No data Received" like the following image. Is anyone can tell me what happen here?


Thank You,
Weipeng Chen

Andrew Balmos

unread,
Mar 7, 2016, 8:45:58 AM3/7/16
to Weipeng Chen, OADA Developers Group
Weipeng,

`oada-ref-auth-js` is just the server side of the OADA OAuth 2.0 stack, it has no client. The `oada-id-client-js` library implements the client side of OADA's OAuth 2.0 stack. The repo has examples can easily be pointed to your local server. We also host a version of that client at: https://client.oada-dev.com. You can enter "localhost:3000" in any of the "Domain" fields to start the associated OAuth 2.0 flows with your local server. 

Note: Are you using a self-signed SSL certificate? If so, you need to to approve it in the browser before the client will work. One way of doing that is: navigate to "https://localhost:3000" (the https part is important) and approve the self-signed certificate using the warnings that come up. 

Andrew

--
You received this message because you are subscribed to the Google Groups "OADA Developers Group" group.
To unsubscribe from this group and stop receiving emails from it, send an email to oada-dev+u...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Aaron Ault

unread,
Mar 7, 2016, 8:48:31 AM3/7/16
to Andrew Balmos, Weipeng Chen, OADA Developers Group
I'll also add that I spent a couple of hours one day banging my head against the wall trying to figure out why the client wouldn't connect to my local server, and finally figured out that if, in the client's "Domain" textbox, you enter "https://localhost:3000" instead of "localhost:3000", it won't work.  You have to leave off the https:// because it currently prepends that to whatever you type in the box.

Aaron

Weipeng Chen

unread,
Mar 11, 2016, 8:23:54 PM3/11/16
to OADA Developers Group, che...@oregonstate.edu

Thank you for answer me the previous question. Now I have a new question. When I tried to start an express server by use the command "grunt demo" in the 'oada-id-client-js' repo, it works successfully and showed two text-box in localhost:3007, but when I click one of them, it just showed "invalid_client_metadata:Client metadata must include a valid trusted OADA", such as the photo showed above. Can you tell me how to fix this? 

Andrew Balmos

unread,
Mar 14, 2016, 2:10:46 PM3/14/16
to Weipeng Chen, OADA Developers Group
Weipeng,

I just pushed some commits to `oada-id-client-js`. If you pull and rebuild the project the demo should now work.

Andrew
Reply all
Reply to author
Forward
0 new messages