Hi @speedy, @quynh,
we removed this from our 3.0 milestone, since 3.0 is basically a release, where underlying concepts change.
- Python 3 support => a lot of code changes (roughly all the code)
- cryptographic lib changes
- immense DB changes: The user assignment will be removed from the token table and stored in its own, new database table.
It is important for use to get this shipped. Lately we sat togeather and moved some features to the next release 3.1 (otherwise we would not be able to finish the 3.0)
In addition we realized, that we also need a redesign of the policies and make them more harmonic with the event handlers.
Currently the policy table contains a lot of information - some of the columns are like conditions for the policy and others are the action. Why are conditions static in the policy table? This makes it difficult for us to add a new condition like the arbitrary user attribute. Why do the action only have one column?
This makes it difficult to parse the action…
So you see, as we want to make this right we had to move this to 3.1.
Then we can add the user attributes and use them in arbitrary conditions in policies and event handlers.