Let me add another use case: in our dev environments the keystone service only provides an https endpoint, however configuring keys on multiple (sometimes transient) local boxes is a pain. Enabling an insecure option would allow us to do development against the https endpoints, then roll to a "production" configuration on release.
Let me add another use case: in our dev environments the keystone service only provides an https endpoint, however configuring keys on multiple (sometimes transient) local boxes is a pain. Enabling an insecure option would allow us to do development against the https endpoints, then roll to a "production" configuration on release.