Hi Francesco,
On Fri, Sep 8, 2017 at 8:18 AM, Francesco Chicchiriccò
wrote:
>
> Very practical reasons (as said elsewhere I believe): starting with 2.0,
> Entitlements are no more database entities (as they used to be up to 1.2)
> but Java constants.
>
OK thanks for the explanation.
> b) Perh
[
https://issues.apache.org/jira/browse/SYNCOPE-1206?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Francesco Chicchiriccò resolved SYNCOPE-1206.
-
Resolution: Fixed
> Dynamic membership updates not considered for provis
[
https://issues.apache.org/jira/browse/SYNCOPE-1206?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16158649#comment-16158649
]
ASF subversion and git services commented on SYNCOPE-1206:
--
Com
[
https://issues.apache.org/jira/browse/SYNCOPE-1206?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16158648#comment-16158648
]
ASF subversion and git services commented on SYNCOPE-1206:
--
Com
Francesco Chicchiriccò created SYNCOPE-1206:
---
Summary: Dynamic membership updates not considered for
provisioning during update
Key: SYNCOPE-1206
URL: https://issues.apache.org/jira/browse/SYNCOPE-1206
Francesco Chicchiriccò created SYNCOPE-1205:
---
Summary: Serialization exception in the logs when editing users
pending approval
Key: SYNCOPE-1205
URL: https://issues.apache.org/jira/browse/SYNCOPE-1205
Hi Colm,
see my replies below.
Regards.
On 07/09/2017 18:20, Colm O hEigeartaigh wrote:
Hi Francesco,
A few further thoughts on this:
a) Instead of having both entitlements + privileges, would it make sense to
only have privileges, where the "entitlements" are privileges on the
Syncope applic