Migrating privacyIDEA

Hi,

at the moment I am not producing so much code as you might have realized
on github.

privacyIDEA is still based on pylons, which is a rather old python
framework and which is not actively developed anymore. Therefor, at the
moment I am investigating new possibilities where to migrate privacyIDEA
to come up with a new shiny 2.0.

This will be with the beginning of next year.

I am investigating things like flask, knockout.js, bootstrap, angularJS…
to build a lightweight, modern system with an attractive UI. I like it a
lot. Started to adapt many things in flask. But as it turns out, this is
also some kind of (major) rewrite. I realize there might be a better
data model :wink:

If you have any comments, suggestions and ideas, please drop me a note.

Kind regards

Cornelius

Hello,

in the process of the migration I also started to wonder how to deal
with the policies.

I realize, there are different kind of policies:
A) Some that restrict the access to certain functions and
B) some that work as a configuration setting, to define how privacyidea
is supposed to behave in certain conditions.

I’d like to keep things simple, keep the function-code clean and thus
not weave the policies to much into the code.
So I like the idea to handle policies with decorators. At least I can
think of it in case A).

I added a wiki page on this:

Feel free to drop your comments and thoughts.

Kind regards
CorneliusAm 17.11.2014 um 16:56 schrieb Cornelius Kölbel:

Hi,

at the moment I am not producing so much code as you might have realized
on github.

privacyIDEA is still based on pylons, which is a rather old python
framework and which is not actively developed anymore. Therefor, at the
moment I am investigating new possibilities where to migrate privacyIDEA
to come up with a new shiny 2.0.

This will be with the beginning of next year.

I am investigating things like flask, knockout.js, bootstrap, angularJS…
to build a lightweight, modern system with an attractive UI. I like it a
lot. Started to adapt many things in flask. But as it turns out, this is
also some kind of (major) rewrite. I realize there might be a better
data model :wink:

If you have any comments, suggestions and ideas, please drop me a note.

Kind regards

Cornelius