Created attachment 1177517 [details]
filtering from satellite for one role.

Description of problem:

When creating a filter allowing a user only to see things named  ~ oss* , 
he is then only able to see things named oss* troughout the menus.  

However if he press a activation key, and then in the url (as they are in sequence) select a number,he would not normally be able to see ie he has access to AK 1 normally and then he types 2 for the fun of it then he will see the number 2 AK even tough he should not be able to, and from that he can click host collections, and from that he can clone a host collection he would normally not have access to, and that way get access to all hosts under that collection and be able to change settings install packages and more on them. 

Activation keys are of cause public if you have the right ORG id, and it will let you register a server, however it should not let you access other parts of the org that would normally be filtered out for you. 

This way you effectively sets all filters out of action, 



Version-Release number of selected component (if applicable):
6.2.0 beta 2

How reproducible:
Always.

Steps to Reproduce:
1. Create restrective filter that only allows you to see AK and more starting with name oss* or others using the ~ in the filter. 
2. test what you can see. 
3.

Actual results:
You can see every thing in the ui like were intended, however by modifying the url under activation keys, you can get access to other persons activation keys  starting with something else than oss* that you normally would not be able to see nor edit due to the filtering. 

Expected results:
permission denied for the access key you should not have access to due to the filter. 

Additional info:

Filter attached.