This Bug Report affects these Traffic Control components:

• Traffic Ops

Current behavior:

You can submit a POST or PUT to /acme_accounts with an email that isn't an email address, and/or a uri that isn't a valid uri.

Expected behavior:

I think the API should verify those fields, but it's possible I just don't understand some use-case for them being invalid.

Steps to reproduce:

topost -kpa 3.1 acme_accounts '{"email": "not an email", "uri": "not a URI", "provider": "some provider", "privateKey": "some private key"}'