dynamic provider error

[calh]

I'm not sure if I'm doing something wrong, but whenever I provide a dynamic provider URL in the configuration, I get this error.

$ oic_flow_tests.py ryo
X (oic-verify)Special flow used to find necessary user interactions - 
CRITICAL ([u'Traceback (most recent call last):\n', u'  
File "/usr/local/lib/python2.7/dist-packages/oictest-0.2.1-py2.7.egg/oictest/base.py", 
line 217, in send\n    self.last_content, self.features, **extra_args)\n', 
u'TypeError: __call__() takes exactly 1 argument (6 given)\n'])

The same error happens with the provided ryo.py file too.

[rohe]

10 nov 2014 kl. 21:53 skrev Cal Heldenbrand [email protected]:

I'm not sure if I'm doing something wrong, but whenever I provide a dynamic provider URL in the configuration, I get this error.

$ oic_flow_tests.py ryo
X (oic-verify)Special flow used to find necessary user interactions -
CRITICAL ([u'Traceback (most recent call last):\n', u'
File "/usr/local/lib/python2.7/dist-packages/oictest-0.2.1-py2.7.egg/oictest/base.py",
line 217, in send\n self.last_content, self.features, **extra_args)\n',
u'TypeError: call() takes exactly 1 argument (6 given)\n'])

The same error happens with the provided ryo.py file too.

It’s probably not you :-)
The code is in heavy flux right now.
By the end of the week I should have it in order again.

— Roland

”Being able to think like a child is an important attribute of being an adult” - Eddie Izzard

[calh]

Okay thanks. Is there a specific commit I can roll back to in order to play around with my tests until then?

[rohe]

10 nov 2014 kl. 22:05 skrev Cal Heldenbrand [email protected]:

Okay thanks. Is there a specific commit I can roll back to in order to play around with my tests until then?

Hm, don’t know off the top of my head.
I’ll look at it tomorrow.

— Roland

”Being able to think like a child is an important attribute of being an adult” - Eddie Izzard

[calh]

Also, follow up question, if I manually enter in the endpoints for my OP (issuer, authorization_endpoint, token_endpoint, etc) and run the tests, everything returns OK, but I don't see any hits server-side on my app. Is this also related to your current work?

[rohe]

Sort of :-(

• Roland (@ my iphone)

On 10 nov 2014, at 22:20, Cal Heldenbrand <[email protected]mailto:[email protected]> wrote:

Also, follow up question, if I manually enter in the endpoints for my OP (issuer, authorization_endpoint, token_endpoint, etc) and run the tests, everything returns OK, but I don't see any hits server-side on my app. Is this also related to your current work?

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/22#issuecomment-62457229.

[rohe]

Checked in a fix that should enable you to run the oicc.py script again.

10 nov 2014 kl. 22:05 skrev Cal Heldenbrand [email protected]:

Okay thanks. Is there a specific commit I can roll back to in order to play around with my tests until then?

— Roland

”Being able to think like a child is an important attribute of being an adult” - Eddie Izzard

[calh]

Yes, I think it's working! I managed to make it through a few tests before a failure. One follow up question, is there a way to provide cookies in the interaction section? (Or headers would suffice)

Thank you!

[rohe]

12 nov 2014 kl. 18:34 skrev Cal Heldenbrand [email protected]:

Yes, I think it's working! I managed to make it through a few tests before a failure. One follow up question, is there a way to provide cookies in the interaction section? (Or headers would suffice)

Well, sort of.

When you start oicc.py you can give the argument -Ki <file_name>.
The script will then import cookies from the file named and use them in the communication with the server.
The format of the file is the Netscape format.

The think behind this was that you used your normal browser, authenticated at the server and then
dumped the cookies returned by the server to the above mentioned file.

— Roland

”Being able to think like a child is an important attribute of being an adult” - Eddie Izzard