[jira] [Commented] (SYNCOPE-119) Realm-based authorization
[ https://issues.apache.org/jira/browse/SYNCOPE-119?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15027152#comment-15027152 ] ASF subversion and git services commented on SYNCOPE-119: - Commit ca262864747b56e38851a963f45b3a59e1d8592c in syncope's branch refs/heads/master from [~ilgrosso] [ https://git-wip-us.apache.org/repos/asf?p=syncope.git;h=ca26286 ] [SYNCOPE-119] Another small fix for isAssignable queries > Realm-based authorization > - > > Key: SYNCOPE-119 > URL: https://issues.apache.org/jira/browse/SYNCOPE-119 > Project: Syncope > Issue Type: New Feature >Reporter: Francesco Chicchiriccò >Assignee: Francesco Chicchiriccò > Fix For: 2.0.0 > > > The current authentication / authorization model has some weaknesses, as > outlined at [1]. > In the same mail thread a refactoring proposal is shown for implementing a > system-wide realm-based hierarchical security model. > This will impact nearly every component and layer in the system, so great > care should be taken and extensive testing. > Discussion on wiki: > https://cwiki.apache.org/confluence/display/SYNCOPE/%5BDISCUSS%5D+Realms > [1] > http://syncope-dev.1063484.n5.nabble.com/syncope-dev-Authorization-entitlements-td4830322.html -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[ANNOUNCE] CFP open for ApacheCon North America 2016
Community growth starts by talking with those interested in your project. ApacheCon North America is coming, are you? We are delighted to announce that the Call For Presentations (CFP) is now open for ApacheCon North America. You can submit your proposed sessions at http://events.linuxfoundation.org/events/apache-big-data-north-america/program/cfp for big data talks and http://events.linuxfoundation.org/events/apachecon-north-america/program/cfp for all other topics. ApacheCon North America will be held in Vancouver, Canada, May 9-13th 2016. ApacheCon has been running every year since 2000, and is the place to build your project communities. While we will consider individual talks we prefer to see related sessions that are likely to draw users and community members. When submitting your talk work with your project community and with related communities to come up with a full program that will walk attendees through the basics and on into mastery of your project in example use cases. Content that introduces what's new in your latest release is also of particular interest, especially when it builds upon existing well know application models. The goal should be to showcase your project in ways that will attract participants and encourage engagement in your community, Please remember to involve your whole project community (user and dev lists) when building content. This is your chance to create a project specific event within the broader ApacheCon conference. Content at ApacheCon North America will be cross-promoted as mini-conferences, such as ApacheCon Big Data, and ApacheCon Mobile, so be sure to indicate which larger category your proposed sessions fit into. Finally, please plan to attend ApacheCon, even if you're not proposing a talk. The biggest value of the event is community building, and we count on you to make it a place where your project community is likely to congregate, not just for the technical content in sessions, but for hackathons, project summits, and good old fashioned face-to-face networking. -- rbo...@apache.org http://apache.org/
[jira] [Commented] (SYNCOPE-119) Realm-based authorization
[ https://issues.apache.org/jira/browse/SYNCOPE-119?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15026942#comment-15026942 ] ASF subversion and git services commented on SYNCOPE-119: - Commit 2ec09df55e6036b171d1e398949271e9676706ee in syncope's branch refs/heads/master from [~ilgrosso] [ https://git-wip-us.apache.org/repos/asf?p=syncope.git;h=2ec09df ] [SYNCOPE-119] Always include root realm in isAssignable queries > Realm-based authorization > - > > Key: SYNCOPE-119 > URL: https://issues.apache.org/jira/browse/SYNCOPE-119 > Project: Syncope > Issue Type: New Feature >Reporter: Francesco Chicchiriccò >Assignee: Francesco Chicchiriccò > Fix For: 2.0.0 > > > The current authentication / authorization model has some weaknesses, as > outlined at [1]. > In the same mail thread a refactoring proposal is shown for implementing a > system-wide realm-based hierarchical security model. > This will impact nearly every component and layer in the system, so great > care should be taken and extensive testing. > Discussion on wiki: > https://cwiki.apache.org/confluence/display/SYNCOPE/%5BDISCUSS%5D+Realms > [1] > http://syncope-dev.1063484.n5.nabble.com/syncope-dev-Authorization-entitlements-td4830322.html -- This message was sent by Atlassian JIRA (v6.3.4#6332)
Syncope-master - Build # 1177 - Fixed
The Apache Jenkins build system has built Syncope-master (build #1177) Status: Fixed Check console output at https://builds.apache.org/job/Syncope-master/1177/ to view the results.
Syncope-master - Build # 1176 - Failure
The Apache Jenkins build system has built Syncope-master (build #1176) Status: Failure Check console output at https://builds.apache.org/job/Syncope-master/1176/ to view the results.
Syncope-master - Build # 1178 - Failure
The Apache Jenkins build system has built Syncope-master (build #1178) Status: Failure Check console output at https://builds.apache.org/job/Syncope-master/1178/ to view the results.
Syncope-master - Build # 1179 - Fixed
The Apache Jenkins build system has built Syncope-master (build #1179) Status: Fixed Check console output at https://builds.apache.org/job/Syncope-master/1179/ to view the results.
[jira] [Commented] (SYNCOPE-119) Realm-based authorization
[ https://issues.apache.org/jira/browse/SYNCOPE-119?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15026891#comment-15026891 ] ASF subversion and git services commented on SYNCOPE-119: - Commit 59106ffc72dcfb0d7c103c7636770ba246d2bd0b in syncope's branch refs/heads/master from [~ilgrosso] [ https://git-wip-us.apache.org/repos/asf?p=syncope.git;h=59106ff ] [SYNCOPE-119] Avoid duplicate realm specification in assignable queries > Realm-based authorization > - > > Key: SYNCOPE-119 > URL: https://issues.apache.org/jira/browse/SYNCOPE-119 > Project: Syncope > Issue Type: New Feature >Reporter: Francesco Chicchiriccò >Assignee: Francesco Chicchiriccò > Fix For: 2.0.0 > > > The current authentication / authorization model has some weaknesses, as > outlined at [1]. > In the same mail thread a refactoring proposal is shown for implementing a > system-wide realm-based hierarchical security model. > This will impact nearly every component and layer in the system, so great > care should be taken and extensive testing. > Discussion on wiki: > https://cwiki.apache.org/confluence/display/SYNCOPE/%5BDISCUSS%5D+Realms > [1] > http://syncope-dev.1063484.n5.nabble.com/syncope-dev-Authorization-entitlements-td4830322.html -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (SYNCOPE-733) Table sort does not work fine in case of multi paged result
[ https://issues.apache.org/jira/browse/SYNCOPE-733?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marco Di Sabatino Di Diodoro reassigned SYNCOPE-733: Assignee: Marco Di Sabatino Di Diodoro > Table sort does not work fine in case of multi paged result > --- > > Key: SYNCOPE-733 > URL: https://issues.apache.org/jira/browse/SYNCOPE-733 > Project: Syncope > Issue Type: Bug > Components: console >Affects Versions: 2.0.0 >Reporter: fabio martelli >Assignee: Marco Di Sabatino Di Diodoro > Fix For: 2.0.0 > > > By clicking on a column label in order to sort the table results, sort occurs > but a new component for result page browsing is added. At the end we will > have one pagination component for every click performed to sort table results. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (SYNCOPE-733) Table sort does not work fine in case of multi paged result
[ https://issues.apache.org/jira/browse/SYNCOPE-733?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marco Di Sabatino Di Diodoro resolved SYNCOPE-733. -- Resolution: Fixed > Table sort does not work fine in case of multi paged result > --- > > Key: SYNCOPE-733 > URL: https://issues.apache.org/jira/browse/SYNCOPE-733 > Project: Syncope > Issue Type: Bug > Components: console >Affects Versions: 2.0.0 >Reporter: fabio martelli >Assignee: Marco Di Sabatino Di Diodoro > Fix For: 2.0.0 > > > By clicking on a column label in order to sort the table results, sort occurs > but a new component for result page browsing is added. At the end we will > have one pagination component for every click performed to sort table results. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (SYNCOPE-733) Table sort does not work fine in case of multi paged result
[ https://issues.apache.org/jira/browse/SYNCOPE-733?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15026588#comment-15026588 ] ASF subversion and git services commented on SYNCOPE-733: - Commit 7b1cb89bba9b91df3a9153e9bceec5a53a2deec9 in syncope's branch refs/heads/master from [~mdisabatino] [ https://git-wip-us.apache.org/repos/asf?p=syncope.git;h=7b1cb89 ] [SYNCOPE-733] Fix sorting table behavior > Table sort does not work fine in case of multi paged result > --- > > Key: SYNCOPE-733 > URL: https://issues.apache.org/jira/browse/SYNCOPE-733 > Project: Syncope > Issue Type: Bug > Components: console >Affects Versions: 2.0.0 >Reporter: fabio martelli >Assignee: Marco Di Sabatino Di Diodoro > Fix For: 2.0.0 > > > By clicking on a column label in order to sort the table results, sort occurs > but a new component for result page browsing is added. At the end we will > have one pagination component for every click performed to sort table results. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (SYNCOPE-735) Acitiviti history tables uncontrolled growth
[
https://issues.apache.org/jira/browse/SYNCOPE-735?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Francesco Chicchiriccò resolved SYNCOPE-735.
Resolution: Fixed
> Acitiviti history tables uncontrolled growth
>
>
> Key: SYNCOPE-735
> URL: https://issues.apache.org/jira/browse/SYNCOPE-735
> Project: Syncope
> Issue Type: Bug
> Components: core
>Affects Versions: 1.2.6
>Reporter: Francesco Chicchiriccò
>Assignee: Francesco Chicchiriccò
> Fix For: 1.2.7, 2.0.0
>
>
> When using Activiti as workflow engine for users, it seems that three tables
> - managed directly by Activiti - are always added to and never removed from,
> until user gets deleted, when such tables are cleared up.
> The tables are:
> # {{ACT_HI_VARINST}}
> # {{ACT_HI_TASKINST}}
> # {{ACT_HI_ACTINST}}
> A custom "housekeeping" mechanism needs to be implemented in
> {{ActivitiUserWorkflowAdapter}}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (SYNCOPE-735) Acitiviti history tables uncontrolled growth
[
https://issues.apache.org/jira/browse/SYNCOPE-735?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15026644#comment-15026644
]
ASF subversion and git services commented on SYNCOPE-735:
-
Commit 5ad760bd5fdeb62bd695fcc6b888ef5e9fa3a8a8 in syncope's branch
refs/heads/master from [~ilgrosso]
[ https://git-wip-us.apache.org/repos/asf?p=syncope.git;h=5ad760b ]
[SYNCOPE-735] Housekeeping implemented
> Acitiviti history tables uncontrolled growth
>
>
> Key: SYNCOPE-735
> URL: https://issues.apache.org/jira/browse/SYNCOPE-735
> Project: Syncope
> Issue Type: Bug
> Components: core
>Affects Versions: 1.2.6
>Reporter: Francesco Chicchiriccò
>Assignee: Francesco Chicchiriccò
> Fix For: 1.2.7, 2.0.0
>
>
> When using Activiti as workflow engine for users, it seems that three tables
> - managed directly by Activiti - are always added to and never removed from,
> until user gets deleted, when such tables are cleared up.
> The tables are:
> # {{ACT_HI_VARINST}}
> # {{ACT_HI_TASKINST}}
> # {{ACT_HI_ACTINST}}
> A custom "housekeeping" mechanism needs to be implemented in
> {{ActivitiUserWorkflowAdapter}}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (SYNCOPE-735) Acitiviti history tables uncontrolled growth
Francesco Chicchiriccò created SYNCOPE-735:
--
Summary: Acitiviti history tables uncontrolled growth
Key: SYNCOPE-735
URL: https://issues.apache.org/jira/browse/SYNCOPE-735
Project: Syncope
Issue Type: Bug
Components: core
Affects Versions: 1.2.6
Reporter: Francesco Chicchiriccò
Assignee: Francesco Chicchiriccò
Fix For: 1.2.7, 2.0.0
When using Activiti as workflow engine for users, it seems that three tables -
managed directly by Activiti - are always added to and never removed from,
until user gets deleted, when such tables are cleared up.
The tables are:
# {{ACT_HI_VARINST}}
# {{ACT_HI_TASKINST}}
# {{ACT_HI_ACTINST}}
A custom "housekeeping" mechanism needs to be implemented in
{{ActivitiUserWorkflowAdapter}}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (SYNCOPE-735) Acitiviti history tables uncontrolled growth
[
https://issues.apache.org/jira/browse/SYNCOPE-735?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15026631#comment-15026631
]
ASF subversion and git services commented on SYNCOPE-735:
-
Commit e9ff5c73ed144337bf9dc44cbb96bbe01ea3e1d7 in syncope's branch
refs/heads/master from [~ilgrosso]
[ https://git-wip-us.apache.org/repos/asf?p=syncope.git;h=e9ff5c7 ]
[SYNCOPE-735] Merge from 1_2_X
> Acitiviti history tables uncontrolled growth
>
>
> Key: SYNCOPE-735
> URL: https://issues.apache.org/jira/browse/SYNCOPE-735
> Project: Syncope
> Issue Type: Bug
> Components: core
>Affects Versions: 1.2.6
>Reporter: Francesco Chicchiriccò
>Assignee: Francesco Chicchiriccò
> Fix For: 1.2.7, 2.0.0
>
>
> When using Activiti as workflow engine for users, it seems that three tables
> - managed directly by Activiti - are always added to and never removed from,
> until user gets deleted, when such tables are cleared up.
> The tables are:
> # {{ACT_HI_VARINST}}
> # {{ACT_HI_TASKINST}}
> # {{ACT_HI_ACTINST}}
> A custom "housekeeping" mechanism needs to be implemented in
> {{ActivitiUserWorkflowAdapter}}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (SYNCOPE-735) Acitiviti history tables uncontrolled growth
[
https://issues.apache.org/jira/browse/SYNCOPE-735?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15026629#comment-15026629
]
ASF subversion and git services commented on SYNCOPE-735:
-
Commit 5ad760bd5fdeb62bd695fcc6b888ef5e9fa3a8a8 in syncope's branch
refs/heads/1_2_X from [~ilgrosso]
[ https://git-wip-us.apache.org/repos/asf?p=syncope.git;h=5ad760b ]
[SYNCOPE-735] Housekeeping implemented
> Acitiviti history tables uncontrolled growth
>
>
> Key: SYNCOPE-735
> URL: https://issues.apache.org/jira/browse/SYNCOPE-735
> Project: Syncope
> Issue Type: Bug
> Components: core
>Affects Versions: 1.2.6
>Reporter: Francesco Chicchiriccò
>Assignee: Francesco Chicchiriccò
> Fix For: 1.2.7, 2.0.0
>
>
> When using Activiti as workflow engine for users, it seems that three tables
> - managed directly by Activiti - are always added to and never removed from,
> until user gets deleted, when such tables are cleared up.
> The tables are:
> # {{ACT_HI_VARINST}}
> # {{ACT_HI_TASKINST}}
> # {{ACT_HI_ACTINST}}
> A custom "housekeeping" mechanism needs to be implemented in
> {{ActivitiUserWorkflowAdapter}}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (SYNCOPE-119) Realm-based authorization
[ https://issues.apache.org/jira/browse/SYNCOPE-119?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15026630#comment-15026630 ] ASF subversion and git services commented on SYNCOPE-119: - Commit bbb051feb43291de74d7cec215c63d2d68cbca03 in syncope's branch refs/heads/master from [~ilgrosso] [ https://git-wip-us.apache.org/repos/asf?p=syncope.git;h=bbb051f ] [SYNCOPE-119] Added search options and checks to match assignable conditions, for usage with memberships and relationships > Realm-based authorization > - > > Key: SYNCOPE-119 > URL: https://issues.apache.org/jira/browse/SYNCOPE-119 > Project: Syncope > Issue Type: New Feature >Reporter: Francesco Chicchiriccò >Assignee: Francesco Chicchiriccò > Fix For: 2.0.0 > > > The current authentication / authorization model has some weaknesses, as > outlined at [1]. > In the same mail thread a refactoring proposal is shown for implementing a > system-wide realm-based hierarchical security model. > This will impact nearly every component and layer in the system, so great > care should be taken and extensive testing. > Discussion on wiki: > https://cwiki.apache.org/confluence/display/SYNCOPE/%5BDISCUSS%5D+Realms > [1] > http://syncope-dev.1063484.n5.nabble.com/syncope-dev-Authorization-entitlements-td4830322.html -- This message was sent by Atlassian JIRA (v6.3.4#6332)
