zopefoundation / Products.PluggableAuthService

Pluggable Zope authentication / authorization framework
Other
9 stars 18 forks source link

Cannot update challenge_protocol #63

Closed tech-kio closed 4 years ago

tech-kio commented 4 years ago

Hello, I am trying to change the mapping for xml-rpc to map to http and it seems it doesn't work in : /acl_users/challenge_protocol

Using Zope 4.1.3. It doesn't save changes after pressing update mapping.

Thank you!

jugmac00 commented 4 years ago

I am not 100% sure whether I understand your problem.

I only setup Products.PluggableAuthService once, and then I have not touched it ever since.

I am not sure what "challenge_protocol" is... I installed the "challenge_chooser" - did you mean that?

My setup is cookie_auth for browser and http(basic_auth) for XML-RPC - this currently works, and I also changed them, saved them successfully, reversed them, saved them.. .and it all works.

I also run Zope 4.1.3.

What exactly happens when you hit the "Update Mapping" button? Does the page get reloaded? Maybe open the dev-console in your browser and make sure, that the reload happens and also that no errors show off in the console.

tech-kio commented 4 years ago

Yes, the page refreshes and there is nothing on console logs. I simply select http and press update mapping, but it doesn't keep the setting :

zopeprob20200127

d-maurer commented 4 years ago

Jürgen Gmach wrote at 2020-1-26 23:39 -0800:

... I am not sure what "challenge_protocol" is... I installed the "challenge_chooser" - did you mean that?

The "challenge_protocol" is the way, the challenge is implemented: e.g. via HTTP Basic Authentication (browser login dialog) or via an application login dialog (together with cookie authentication).

It is what the "challenge_chooser" selects.

dataflake commented 4 years ago

The fix is in version 2.3, which I just released.

jugmac00 commented 4 years ago

So, obviously this was only a problem on Python 3, and I must have tried to reproduce the problem in my Python 2 dev setup.

dataflake commented 4 years ago

That is correct