Comment 1 for bug 1950464

I noticed this using a deployment with an application credential and access rules and I kept getting a 401 when I didn't expect it (I added the API to the access rules.)

It wasn't until I dug through the keystonemiddleware code that I realized I needed to set that configuration option in keystonemiddleware. After I updated the configuration for all the services, access rules and keystonemiddleware filtered properly.

I feel like this might be an important part of the feature that should be called out, since it's not straightforward from the error what needs to happen.