Comment 8 for bug 1743603

@Lance @Colleen it sounds to me like this is a valid issue with a couple potential solutions:

1) somehow the middleware needs to distinguish if it is being run by keystoner (in which case it should not log this warning) or something else (in which case it should).

or...

2) we have to require that the same service_token_roles and service_token_roles_required conf options are set in keystone's conf as in the other services, and then need to make sure they are passed to the middleware when it is used in the keystone pipeline.

I don't know if #2 is either possible or advisable, so I would lean toward #1. Either way this needs to be resolved before "This will be removed in future releases" becomes a reality.