Closed Bug 959476 Opened 11 years ago Closed 11 years ago

Remove X-Conditions-Accepted from tokenserver 1.0 spec

Categories

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

x86_64
Linux
defect
Not set
normal

Tracking

(Not tracked)

VERIFIED FIXED

People

(Reporter: rfkelly, Assigned: rfkelly)

References

Details

(Whiteboard: [qa-])

Attachments

(1 file)

We no longer need to enforce ToS acceptance at the server level, and have no plans to ship anything that needs this functionality from the tokenserver. Refactoring the backend to support this in conjunction with generation/fingerprint stuff is looking pretty yuck. Can we just yank this from the 1.0 spec and revisit if we need it down the road?
Attachment #8359603 - Flags: review?(telliott)
(IIRC it was a pretty last-minute addition to begin with, for the rush-rush-rush AitC deadline way back when)
Comment on attachment 8359603 [details] [diff] [review] tokenserver-no-conditions.diff Review of attachment 8359603 [details] [diff] [review]: ----------------------------------------------------------------- Yeah, if it's getting in the way, keeping it around is low priority for now.
Attachment #8359603 - Flags: review?(telliott) → review+
Blocks: 956217
Whiteboard: [qa-]
Depends on: 960009
it's done
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
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: