These warnings happen every time the policies are reloaded which apparently happens dynamically, we should make sure to only emit these warnings when keystone starts.
The reason we emit these warnings is that while the policies are deprecated, the old rules and the new rules are OR'd together, making them more open by default, so we want people to opt into the new more secure policies by changing them in your policy config.
These warnings happen every time the policies are reloaded which apparently happens dynamically, we should make sure to only emit these warnings when keystone starts.
The reason we emit these warnings is that while the policies are deprecated, the old rules and the new rules are OR'd together, making them more open by default, so we want people to opt into the new more secure policies by changing them in your policy config.