Fix issues with saving custom API token policies.

Review Request #9823 — Created March 22, 2018 and submitted — Latest diff uploaded

Information

Review Board
release-3.0.x
4c09645...

Reviewers

Even after saving an API token policy, the action would still show that
it's set to "Full access," making it seem like the custom policy didn't
save. If clicked again, this could override the custom policy. This was
happening because we never actually set the policy type to "custom."

This change does that, setting the type when saving the custom policy.

Selected Custom and edited the policy. Clicked Save. Saw that it was set
to Custom, and that reloading or editing it again showed my proper policy.