Out of curiosity, are you using caching in any of the following areas:
Horizon/Django
Keystonemiddleware (for any of the services)?
It could be possible the token response has been cached. If that is the case, even if the user is deleted, if a service does not check with keystone, it is impossible to know if the user/data/etc has been deleted.
In the past the behavior I just described was highlighted in the documentation but that information may have disappeared in a number of documentation/guide updates.
Let us know and we can work to further dig into the issue/duplicate/add documentation (depending on what is needed).
Out of curiosity, are you using caching in any of the following areas:
Horizon/Django
Keystonemiddleware (for any of the services)?
It could be possible the token response has been cached. If that is the case, even if the user is deleted, if a service does not check with keystone, it is impossible to know if the user/data/etc has been deleted.
In the past the behavior I just described was highlighted in the documentation but that information may have disappeared in a number of documentation/guide updates.
Let us know and we can work to further dig into the issue/duplicate/add documentation (depending on what is needed).
Thanks!