Use shared secret auth in tests instead of oauth

RESOLVED WONTFIX

Status

Marketplace
Code Quality
P3
normal
RESOLVED WONTFIX
5 years ago
2 years ago

People

(Reporter: mat, Unassigned)

Tracking

x86_64
Linux
Points:
---

Details

(Whiteboard: [marketplace-transition])

(Reporter)

Description

5 years ago
Pretty much all of our API tests that test views/resources rely on OAuthClient, but the main authentication scheme is what fireplace, rocketfuel etc use, and that's SharedSecret. In fact, we even had a bug recently (bug 943471) that was due to an edge case in RestSharedSecretAuthentication code; view tests would have caught that if they had used Shared Secret.

I propose we introduce a new test client class, SharedSecretClient, and use that in our API tests. (It might even be faster, who knows)
(Reporter)

Updated

4 years ago
Priority: -- → P3

Updated

4 years ago
Component: API → Code Quality

Updated

2 years ago
Status: NEW → RESOLVED
Last Resolved: 2 years ago
Resolution: --- → WONTFIX
Whiteboard: [marketplace-transition]
You need to log in before you can comment on or make changes to this bug.