Lukasz, HTTPS is fine and MUST be implemented ASAP, but it doesn't solve the issue. When I click "Logout" I'm expecting that a token will be revoked, so nobody can use it to sign requests if it was stolen. It's about security. It's a behaviour that I expect as user. I don't want make manual requests to Keystone in order to revoke token - I want it out of box.
So what's the problem to implement it within mentioned blueprint? Thanks, Igor -- Mailing list: https://launchpad.net/~fuel-dev Post to : fuel-dev@lists.launchpad.net Unsubscribe : https://launchpad.net/~fuel-dev More help : https://help.launchpad.net/ListHelp
