Closed Bug 718725 Opened 12 years ago Closed 12 years ago

services.user doesn't accept "check_node" argument

Categories

(Cloud Services Graveyard :: Server: Sync, defect)

x86
macOS
defect
Not set
normal

Tracking

(Not tracked)

VERIFIED FIXED

People

(Reporter: Atoll, Unassigned)

Details

(Whiteboard: [qa-])

Attachments

(1 file)

Please port the check_node argument from services.auth to services.user, as it's mandatory for load testing (where we set it to false).
After further investigation, it looks like no special support in services.user should be necessary.  The code in wsgiauth.py checks for "auth.check_node" directly in the config rather than looking for it as an attribute of the services.user backend object.

What happens when you set auth.check_node in the config file for a services.user backend?  Does it give an error, or just not work?

I will attach a testcase for auth.check_node, which passes for me under both services.auth and services.user on current tip.
Whiteboard: [qa-]
Attachment #589328 - Flags: review?(tarek) → review?(telliott)
Attachment #589328 - Flags: review?(telliott) → review+
We don't plan to deploy anything of updated server-core, but still, there's a reviewed patch here so I might as well commit it.

http://hg.mozilla.org/services/server-core/rev/27768497bc68
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
Yea verified the test on sync 1.1:
./sync/server-full/deps/server-core/services/tests/test_wsgiauth.py

For completeness Verifying the ticket.
Status: RESOLVED → VERIFIED
Product: Cloud Services → Cloud Services Graveyard
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: