[jira] [Updated] (SYNCOPE-404) LDAP Roles lose entitlement upon LDAP synchronization
[ https://issues.apache.org/jira/browse/SYNCOPE-404?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Francesco Chicchiriccò updated SYNCOPE-404: --- Affects Version/s: 1.1.3 Fix Version/s: 1.2.0 1.1.4 Labels: entitlement (was: core entitlement syncope) LDAP Roles lose entitlement upon LDAP synchronization - Key: SYNCOPE-404 URL: https://issues.apache.org/jira/browse/SYNCOPE-404 Project: Syncope Issue Type: Bug Components: core Affects Versions: 1.1.0, 1.1.3 Reporter: bryan staley Labels: entitlement Fix For: 1.1.4, 1.2.0 After creating a new role in Syncope, and assigning that role to an LDAP resource, i added some Syncope entitlements to the new role. The entitlements were saved to the Syncope database, but upon the following synchronization with LDAP, the entitlements were removed. Steps: Create role (newrole) in syncope Assign ldap as a resource to newrole Assign entitlements to newrole Save newrole Wait for next LDAP synchronization task Examine newrole entitlements (they are empty for me) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (SYNCOPE-404) LDAP Roles lose entitlement upon LDAP synchronization
[ https://issues.apache.org/jira/browse/SYNCOPE-404?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Francesco Chicchiriccò resolved SYNCOPE-404. Resolution: Fixed Assignee: Francesco Chicchiriccò 1_1_X: http://svn.apache.org/r1505611 trunk: http://svn.apache.org/r1505612 LDAP Roles lose entitlement upon LDAP synchronization - Key: SYNCOPE-404 URL: https://issues.apache.org/jira/browse/SYNCOPE-404 Project: Syncope Issue Type: Bug Components: core Affects Versions: 1.1.0, 1.1.3 Reporter: bryan staley Assignee: Francesco Chicchiriccò Labels: entitlement Fix For: 1.1.4, 1.2.0 After creating a new role in Syncope, and assigning that role to an LDAP resource, i added some Syncope entitlements to the new role. The entitlements were saved to the Syncope database, but upon the following synchronization with LDAP, the entitlements were removed. Steps: Create role (newrole) in syncope Assign ldap as a resource to newrole Assign entitlements to newrole Save newrole Wait for next LDAP synchronization task Examine newrole entitlements (they are empty for me) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[DISCUSS] Replace logback with log4j 2
Hi all, I have recently read a stunning post from Christian Grobmeier [1] and I was thinking why not to switch the trunk (1.2.0) from logback to log4j 2 (with new AsyncLoggers, of course!). I was also thinking to keep the SLF4J layer, so that code changes would be minimal. Besides performance benefit, we will also increase our non-ASF dependency level. WDYT? [1] http://www.grobmeier.de/log4j-2-performance-close-to-insane-20072013.html#.Ue0KLRe9hyc -- Francesco Chicchiriccò ASF Member, Apache Syncope PMC chair, Apache Cocoon PMC Member http://people.apache.org/~ilgrosso/
Re: [DISCUSS] Replace logback with log4j 2
On 22/07/2013 12:45, Francesco Chicchiriccò wrote: On 22/07/2013 12:41, Francesco Chicchiriccò wrote: Hi all, I have recently read a stunning post from Christian Grobmeier [1] and I was thinking why not to switch the trunk (1.2.0) from logback to log4j 2 (with new AsyncLoggers, of course!). I was also thinking to keep the SLF4J layer, so that code changes would be minimal. Besides performance benefit, we will also increase our non-ASF dependency level. Ops, I was meaning ...we will also *decrease* our non-ASF dependency level. WDYT? +1 [1] http://www.grobmeier.de/log4j-2-performance-close-to-insane-20072013.html#.Ue0KLRe9hyc -- Massimiliano Perrone Tel +39 393 9121310 Tirasa S.r.l. Viale D'Annunzio 267 - 65127 Pescara Tel +39 0859116307 / FAX +39 085973 http://www.tirasa.net Apache Syncope PMC Member http://people.apache.org/~massi/ L'apprendere molte cose non insegna l'intelligenza (Eraclito)
Re: [DISCUSS] Replace logback with log4j 2
Il 22/07/2013 12:50, Massimiliano Perrone ha scritto: On 22/07/2013 12:45, Francesco Chicchiriccò wrote: On 22/07/2013 12:41, Francesco Chicchiriccò wrote: Hi all, I have recently read a stunning post from Christian Grobmeier [1] and I was thinking why not to switch the trunk (1.2.0) from logback to log4j 2 (with new AsyncLoggers, of course!). I was also thinking to keep the SLF4J layer, so that code changes would be minimal. Besides performance benefit, we will also increase our non-ASF dependency level. Ops, I was meaning ...we will also *decrease* our non-ASF dependency level. WDYT? +1 [1] http://www.grobmeier.de/log4j-2-performance-close-to-insane-20072013.html#.Ue0KLRe9hyc +1 -- Dott. Andrea Patricelli Tel +393204524292 Trainee @ Tirasa S.r.l. Viale D'Annunzio 267 - 65127 Pescara Tel +390859116307 / FAX +39 085973 http://www.tirasa.net
Syncope-trunk - Build # 257 - Failure
The Apache Jenkins build system has built Syncope-trunk (build #257) Status: Failure Check console output at https://builds.apache.org/job/Syncope-trunk/257/ to view the results.
RE: [DISCUSS] Replace logback with log4j 2
I assume there are no dependencies within the code which would allow the users to still give the option to use logback? log4j 2 is still in beta. Do we know when it should be released? Just my two cents... Thanks Oli From: cschneider...@gmail.com [cschneider...@gmail.com] on behalf of Christian Schneider [ch...@die-schneider.net] Sent: 22 July 2013 13:30 To: dev@syncope.apache.org Subject: Re: [DISCUSS] Replace logback with log4j 2 +1 For switching to log4j. I would also keep the slf4j layer. This minimizes direct dependencies on the log framework and also works great in OSGi. Christian 2013/7/22 Francesco Chicchiriccò ilgro...@apache.org Hi all, I have recently read a stunning post from Christian Grobmeier [1] and I was thinking why not to switch the trunk (1.2.0) from logback to log4j 2 (with new AsyncLoggers, of course!). I was also thinking to keep the SLF4J layer, so that code changes would be minimal. Besides performance benefit, we will also increase our non-ASF dependency level. WDYT? [1] http://www.grobmeier.de/log4j-**2-performance-close-to-insane-** 20072013.html#.Ue0KLRe9hychttp://www.grobmeier.de/log4j-2-performance-close-to-insane-20072013.html#.Ue0KLRe9hyc -- Francesco Chicchiriccò ASF Member, Apache Syncope PMC chair, Apache Cocoon PMC Member http://people.apache.org/~**ilgrosso/http://people.apache.org/~ilgrosso/ -- -- Christian Schneider http://www.liquid-reality.dehttps://owa.talend.com/owa/redir.aspx?C=3aa4083e0c744ae1ba52bd062c5a7e46URL=http%3a%2f%2fwww.liquid-reality.de Open Source Architect http://www.talend.comhttps://owa.talend.com/owa/redir.aspx?C=3aa4083e0c744ae1ba52bd062c5a7e46URL=http%3a%2f%2fwww.talend.com
Re: [DISCUSS] Replace logback with log4j 2
On 22/07/2013 14:29, Oliver Wulff wrote: I assume there are no dependencies within the code which would allow the users to still give the option to use logback? There are also direct references in the source code to Logback internal classes (the LoggerController, for example) since the SLF4J APIs do not expose methods for programmatically changing appender's level. I don't see very meaningful for end users to keep with logback, Syncope is not a general purpose framework for which it can make sense to choice that. log4j 2 is still in beta. Do we know when it should be released? Soon, as far as they claim (they've already reach beta 8!), and anyway before than 1.2.0 sees the light. Regards. From: cschneider...@gmail.com [cschneider...@gmail.com] on behalf of Christian Schneider [ch...@die-schneider.net] Sent: 22 July 2013 13:30 To: dev@syncope.apache.org Subject: Re: [DISCUSS] Replace logback with log4j 2 +1 For switching to log4j. I would also keep the slf4j layer. This minimizes direct dependencies on the log framework and also works great in OSGi. Christian 2013/7/22 Francesco Chicchiriccò ilgro...@apache.org Hi all, I have recently read a stunning post from Christian Grobmeier [1] and I was thinking why not to switch the trunk (1.2.0) from logback to log4j 2 (with new AsyncLoggers, of course!). I was also thinking to keep the SLF4J layer, so that code changes would be minimal. Besides performance benefit, we will also increase our non-ASF dependency level. WDYT? [1] http://www.grobmeier.de/log4j-**2-performance-close-to-insane-** 20072013.html#.Ue0KLRe9hychttp://www.grobmeier.de/log4j-2-performance-close-to-insane-20072013.html#.Ue0KLRe9hyc -- Francesco Chicchiriccò ASF Member, Apache Syncope PMC chair, Apache Cocoon PMC Member http://people.apache.org/~ilgrosso/
[jira] [Reopened] (SYNCOPE-403) Enrich PropagationStatusTO to report possible propagation exception message
[ https://issues.apache.org/jira/browse/SYNCOPE-403?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Patricelli reopened SYNCOPE-403: --- FailureMessageModalPage.html missing wicket:extend tag Enrich PropagationStatusTO to report possible propagation exception message --- Key: SYNCOPE-403 URL: https://issues.apache.org/jira/browse/SYNCOPE-403 Project: Syncope Issue Type: Improvement Components: common, console, core Affects Versions: 1.1.2, 1.1.3 Reporter: Andrea Patricelli Assignee: Marco Di Sabatino Di Diodoro Fix For: 1.1.4, 1.2.0 Attachments: SYNCOPE-403.patch PropagationStatusTO may be enriched with a field reporting possible propagation exception message, so that trace exception returned by a resource and get its specific message. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
Syncope-trunk - Build # 258 - Fixed
The Apache Jenkins build system has built Syncope-trunk (build #258) Status: Fixed Check console output at https://builds.apache.org/job/Syncope-trunk/258/ to view the results.
