[AAA-87] AAA sometimes falsely authorizes user to restricted endpoint Created: 20/Jan/16 Updated: 21/Mar/19 Resolved: 26/Jan/16 |
|
| Status: | Resolved |
| Project: | aaa |
| Component/s: | General |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | ||
| Reporter: | Ryan Goulding | Assignee: | Ryan Goulding |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Operating System: All |
||
| External issue ID: | 5033 |
| Description |
|
AAA Authorization may falsely authorize user to a Shiro-restricted endpoint. In the current design, there is a cached User since it was incorrectly assumed that "doGetAuthorizationInfo()" was called directly after "doGetAuthenticationInfo()" for a given request. However, since multiple threads may access the TokenAuthRealm, there is a case for interleaving. This should be fixed by modifying the Principal object returned by "doGetAuthenticationInfo()" to return appropriate information. This is an unpolished script that shows this behavior: [ryan@awesomeo ~]$ cat test.py url = 'http://localhost:8181/restconf/modules/' if _name=='main_': In the future, this script should be added to CSIT, but due to time constraints was tested manually. |
| Comments |
| Comment by Ryan Goulding [ 20/Jan/16 ] |