Thomas Krille
Thomas Krille
Hello @bng-okta, this is a known limitation of OSIAM. We are aware of it, but [it's not documented anywhere yet](https://github.com/osiam/osiam/issues/105). We also agree, that this is something that OSIAM really...
Thanks for your suggestion @bng-okta. This would be much easier, of course. It's still hard enough that I think, it won't make it in 3.0. But for now we can...
Oh my god, are we really scoring so badly? That's embarrassing. But thank you very, very much, @bluestoat, for running these compliance checks against OSIAM. We really appreciate this and...
> Update User with PATCH: add and delete same email address depends on the order Actually, I thought that we remove the PATCH functionality: #21
I've added https://github.com/osiam/osiam/issues/309 to the list of compliance issues.
@wallner @dacrome @sputnik27 Ping
> Why do we omit a .0 PATCH-version? Is there any rationale behind this? No, there isn't any rationale behind this. > As long as we are backwards compatible we...
This is not really needed for 3.0, especially when we release a version with breaking changes anyway, there's not need to talk about versioning of non-breaking changes, etc. So, I...
> The key features of the integrated administration should be: > - Turn the administration on and off > - Manage users (CRUD) > - Manage groups (CRUD) Agreed. >...
I would schedule this for 3.1 and remove the integration of the registration feature from 3.1.