Document how user permission caching works
|Reported by:||Giggaflop||Owned by:||Jennifer|
|Cc:||Daniele Procida||Triage Stage:||Accepted|
|Has patch:||yes||Needs documentation:||no|
|Needs tests:||no||Patch needs improvement:||no|
Could it be mentioned on the API Methods for Django authentication that it may be required that the User object is reobtained if dynamically adding permissions. This is due to them being cached by Django.
This was not made clear by the documentation and has wasted considerable amount of time tracking down until i hit upon this Stack Overflow.
Change History (12)
comment:2 Changed 3 years ago by
|Summary:||User objects Cache permissions data → Document how user permission caching works|
|Triage Stage:||Unreviewed → Accepted|