Re: [DISCUSS] Manage millions of identities

Hi, Am 16.10.18 um 10:54 schrieb Francesco Chicchiriccò: Hi all, I think it's time to discuss about how we want to get prepared for scenarios where the number of identities (mostly users, for the vast majority) to manage is considerably high - from 1 million to above; the typical case being

Re: JavaEE connection pool removeAbandoned setting

done (already last Sunday). The generated reference guide was updated as expected. Cheers, Guido Am 01.06.2018 um 08:35 schrieb Francesco Chicchiriccò: On 31/05/2018 19:30, Guido Wimmel wrote: Hi Francesco, Am 30.05.2018 um 11:11 schrieb Francesco Chicchiriccò: On 29/05/2018 20:36, Guido

Re: JavaEE connection pool removeAbandoned setting

Hi Francesco, Am 30.05.2018 um 11:11 schrieb Francesco Chicchiriccò: On 29/05/2018 20:36, Guido Wimmel wrote: Hi, the recommended JavaEE configuration example on http://syncope.apache.org/docs/reference-guide.html#javaee-container contains Is this intentional? Seems strange to me

JavaEE connection pool removeAbandoned setting

Hi, the recommended JavaEE configuration example on http://syncope.apache.org/docs/reference-guide.html#javaee-container contains Is this intentional? Seems strange to me, as this setting is in seconds (corresponding to more than 5 hours), according to

Re: [VOTE] Apache Syncope 1.2.10

+1 Best regards, Guido > Gesendet: Mittwoch, 25. Januar 2017 um 10:27 Uhr > Von: "Marco Di Sabatino Di Diodoro" > An: dev@syncope.apache.org > Betreff: Re: [VOTE] Apache Syncope 1.2.10 > > > > Il 24/01/2017 09:59, Francesco Chicchiriccò ha scritto: > > I've

Re: [VOTE] Apache Syncope 2.0.0

+1 Best regards, Guido Am 11.09.2016 um 09:41 schrieb Giacomo Lamonaco: +1 (non-binding) Excellent work team! Giacomo - Messaggio originale - Da: "Francesco Chicchiriccò" A: "dev" Inviato: Venerdì, 9 settembre 2016 14:42:17 Oggetto:

Re: [VOTE] Apache Syncope 1.2.8

+1 Regards, Guido Am 03.06.2016 um 11:31 schrieb Massimiliano Perrone: - Messaggio originale - Da: "Francesco Chicchiriccò" A: "dev" Inviato: Venerdì, 3 giugno 2016 10:19:50 Oggetto: [VOTE] Apache Syncope 1.2.8 I've created a 1.2.8

Re: Errored: apache/syncope#1292 (1_2_X - 0195743)

- Build: #1292 Status: Errored Duration: 1 minute and 23 seconds Commit: 0195743 (1_2_X) Author: Guido Wimmel Message: Upgrading Log4j View the changeset: https://github.com/apache/syncope/compare/9d7dbe0d85de...01957433edad View the full build log and details: https://travis-ci.org/apach

Upgrade Log4j2 in Syncope 1.2.X

Hi, I suggest upgrading Logj42 in Syncope 1.2.X from 2.3 to 2.5 (as in 2.0.0-SNAPSHOT). 2.5 has some nice additional features, in particular https://logging.apache.org/log4j/2.x/manual/appenders.html#CustomDeleteOnRollover If there are no objections, I'd create a JIRA issue (if necessary)

Re: [DISCUSS] Switching to UUID primary keys for users, groups and any objects

I'd also prefer UUIDs over the current primary keys. However, that would make migrations from 1.2.x to 2.0 even more difficult than they probably already will be - especially if someone uses the Syncope user id outside of Syncope. Cheers, Guido Am 04.04.2016 um 15:51 schrieb Colm O

Re: [VOTE] Apache Syncope 1.2.6

+1 Best regards, Guido On 05.11.2015 16:19, Marco Di Sabatino Di Diodoro wrote: Hi All, I've created a 1.2.6 release, with the following artifacts up for a vote: GIT source tag (b701329aa): https://git-wip-us.apache.org/repos/asf?p=syncope.git;a=tag;h=b701329aa List of changes:

[jira] [Comment Edited] (SYNCOPE-667) simplification of admin roles filter query used in search

[ https://issues.apache.org/jira/browse/SYNCOPE-667?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14541870#comment-14541870 ] Guido Wimmel edited comment on SYNCOPE-667 at 5/13/15 12:59 PM

[jira] [Commented] (SYNCOPE-667) simplification of admin roles filter query used in search

[ https://issues.apache.org/jira/browse/SYNCOPE-667?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14541882#comment-14541882 ] Guido Wimmel commented on SYNCOPE-667: -- ok, I've deleted the branch

[jira] [Commented] (SYNCOPE-667) simplification of admin roles filter query used in search

[ https://issues.apache.org/jira/browse/SYNCOPE-667?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14541870#comment-14541870 ] Guido Wimmel commented on SYNCOPE-667: -- Merged to 1_2_X. [~ilgrosso]: would be nice

[jira] [Commented] (SYNCOPE-667) simplification of admin roles filter query used in search

[ https://issues.apache.org/jira/browse/SYNCOPE-667?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14542021#comment-14542021 ] Guido Wimmel commented on SYNCOPE-667: -- For me the issue can be closed. I only

[jira] [Created] (SYNCOPE-667) simplification of admin roles filter query used in search

Guido Wimmel created SYNCOPE-667: Summary: simplification of admin roles filter query used in search Key: SYNCOPE-667 URL: https://issues.apache.org/jira/browse/SYNCOPE-667 Project: Syncope

[jira] [Commented] (SYNCOPE-667) simplification of admin roles filter query used in search

[ https://issues.apache.org/jira/browse/SYNCOPE-667?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14540011#comment-14540011 ] Guido Wimmel commented on SYNCOPE-667: -- Created a branch: https://git-wip

[jira] [Updated] (SYNCOPE-667) simplification of admin roles filter query used in search

[ https://issues.apache.org/jira/browse/SYNCOPE-667?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guido Wimmel updated SYNCOPE-667: - Description: As discussed on the dev mailing list [1], I think the query generated

Re: getAdminRolesFilter-query

: getAdminRolesFilter-query On 17/04/2015 10:41, Guido Wimmel wrote: Hi Francesco, ok, thanks for the clarification. I can see if I can investigate further and provide a patch. I did run the integration tests but I do not think the admin roles filtering is covered too well. It seems

getAdminRolesFilter-query

Hi, minor detail, but I recently stubled upon the query generated by SubjectSearchDAOImpl.getAdminRolesFilter(), used by search() and count(). Maybe it could be simplified. It seems to determine all users which have roles not in adminRoles (to be able to filter them out by WHERE subject_id NOT

Re: getAdminRolesFilter-query

the way it is. Cheers, Guido On 16.04.2015 11:52, Francesco Chicchiriccò wrote: On 16/04/2015 11:00, Guido Wimmel wrote: Hi, minor detail, but I recently stubled upon the query generated by SubjectSearchDAOImpl.getAdminRolesFilter(), used by search() and count(). Maybe it could

Re: [VOTE] Apache Syncope 1.2.3

+1 Regards, Guido On 20.03.2015 13:31, Marco Di Sabatino Di Diodoro wrote: I've created a 1.2.3 release, with the following artifacts up for a vote: GIT source tag (da0e335b5): https://git-wip-us.apache.org/repos/asf?p=syncope.git;a=tag;h=syncope-1.2.3 List of changes:

[jira] [Assigned] (SYNCOPE-651) SyncopeUser:checkToken() should fail if token is not set on user

[ https://issues.apache.org/jira/browse/SYNCOPE-651?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guido Wimmel reassigned SYNCOPE-651: Assignee: Guido Wimmel SyncopeUser:checkToken() should fail if token is not set on user

[jira] [Created] (SYNCOPE-651) SyncopeUser:checkToken() should fail if token is not set on user

Guido Wimmel created SYNCOPE-651: Summary: SyncopeUser:checkToken() should fail if token is not set on user Key: SYNCOPE-651 URL: https://issues.apache.org/jira/browse/SYNCOPE-651 Project: Syncope

merging to master [was: (SYNCOPE-651) SyncopeUser:checkToken() should fail if token is not set on user]

Issue Type: Improvement Components: core Affects Versions: 1.1.8, 1.2.2 Reporter: Guido Wimmel Assignee: Guido Wimmel Priority: Minor Fix For: 1.1.9, 1.2.3, 2.0.0 Currently, SyncopeUser:checkToken(String token

[jira] [Resolved] (SYNCOPE-651) SyncopeUser:checkToken() should fail if token is not set on user

[ https://issues.apache.org/jira/browse/SYNCOPE-651?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guido Wimmel resolved SYNCOPE-651. -- Resolution: Fixed SyncopeUser:checkToken() should fail if token is not set on user

Re: Code re-organization for 2.0.0 completed

On 13.02.2015 17:09, Francesco Chicchiriccò wrote: On 13/02/2015 16:59, andrea patricelli wrote: Il 13/02/2015 12:49, Francesco Chicchiriccò ha scritto: Hi all, after some time, following our former discussion [1], I've been able to complete the planned refactoring (see SYNCOPE-620). Please

[jira] [Created] (SYNCOPE-634) performance optimization for content loading

Guido Wimmel created SYNCOPE-634: Summary: performance optimization for content loading Key: SYNCOPE-634 URL: https://issues.apache.org/jira/browse/SYNCOPE-634 Project: Syncope Issue Type

[jira] [Assigned] (SYNCOPE-634) performance optimization for content loading

[ https://issues.apache.org/jira/browse/SYNCOPE-634?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guido Wimmel reassigned SYNCOPE-634: Assignee: Guido Wimmel performance optimization for content loading

[jira] [Resolved] (SYNCOPE-634) performance optimization for content loading

[ https://issues.apache.org/jira/browse/SYNCOPE-634?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guido Wimmel resolved SYNCOPE-634. -- Resolution: Fixed performance optimization for content loading

minor optimization for content loading

Hi, I noticed an inefficiency in the code for loading content.xml: before every insert, the whole table content seems to be read just to get the metadata - see ContentLoaderHandler.getParameters(): 57 MapString, Integer colTypes = jdbcTemplate.query(SELECT * FROM + tableName, 58

Re: disable Spring security anonymous authentication for REST API?

Hi Francesco, fine, thanks for the clarification. Cheers, Guido On 06.02.2015 16:46, Francesco Chicchiriccò wrote: On 06/02/2015 14:56, Guido Wimmel wrote: Hi Francesco, ok, thanks for the clarification. I was misled by the comment in SYNCOPE-132 Introducing a special 'anonymous' user

Re: [VOTE] Apache Syncope 1.2.2

+1 FYI, to upgrade my project from 1.2.1 to 1.2.2 I needed to - change coreContext.xml (SYNCOPE-622, class VirAttrCache refactored) - change restContext.xml (SYNCOPE-630, QueryResourceInfoComparator removed - seems to have been re-introduced shortly after the release) - change my implementation

[jira] [Created] (SYNCOPE-626) make it possible to disallow using the username as password

Guido Wimmel created SYNCOPE-626: Summary: make it possible to disallow using the username as password Key: SYNCOPE-626 URL: https://issues.apache.org/jira/browse/SYNCOPE-626 Project: Syncope

[jira] [Created] (SYNCOPE-621) Reduce log level of bean validation errors (in data binder)

Guido Wimmel created SYNCOPE-621: Summary: Reduce log level of bean validation errors (in data binder) Key: SYNCOPE-621 URL: https://issues.apache.org/jira/browse/SYNCOPE-621 Project: Syncope

Re: [PROPOSAL] Code re-organization for Apache Syncope 2.0

Hi Francesco, Gesendet: Donnerstag, 11. Dezember 2014 um 13:48 Uhr Von: Francesco Chicchiriccò ilgro...@apache.org An: dev@syncope.apache.org Betreff: Re: [PROPOSAL] Code re-organization for Apache Syncope 2.0 I have put a proposal at [1] - as you can see it is an empty skeleton with

Re: [PROPOSAL] Code re-organization for Apache Syncope 2.0

Hi Francesco, On 09.12.2014 17:37, Francesco Chicchiriccò wrote: Hi all, I think it is time to re-organize our codebase in order to allow easier maintenance and simplify extendability. I have put a proposal at [1] - as you can see it is an empty skeleton with README.md on each directory

NullPointerException in NotificationJob?

Hi, it seems to me that there is a problem with email notification in Syncope 1.2.X / master. Could someone verify this? (I'm not sure if it is due to my environment; if it can be verified, I can create a JIRA issue). Steps to reproduce: * Checkout 1.2.X * Change

[jira] [Created] (SYNCOPE-614) NotificationJob fails with NullPointerException

Guido Wimmel created SYNCOPE-614: Summary: NotificationJob fails with NullPointerException Key: SYNCOPE-614 URL: https://issues.apache.org/jira/browse/SYNCOPE-614 Project: Syncope Issue Type

[jira] [Commented] (SYNCOPE-614) NotificationJob fails with NullPointerException

[ https://issues.apache.org/jira/browse/SYNCOPE-614?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14234258#comment-14234258 ] Guido Wimmel commented on SYNCOPE-614: -- I suspect this is due to a combination

[jira] [Created] (SYNCOPE-612) prevent writing of velocity.log

Guido Wimmel created SYNCOPE-612: Summary: prevent writing of velocity.log Key: SYNCOPE-612 URL: https://issues.apache.org/jira/browse/SYNCOPE-612 Project: Syncope Issue Type: Bug

[jira] [Updated] (SYNCOPE-612) prevent writing of velocity.log

[ https://issues.apache.org/jira/browse/SYNCOPE-612?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guido Wimmel updated SYNCOPE-612: - Description: Syncope = 1.2.0 tries to write a velocity.log-File. Startup fails

[jira] [Updated] (SYNCOPE-612) explicit configuration of Velocity logging

[ https://issues.apache.org/jira/browse/SYNCOPE-612?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guido Wimmel updated SYNCOPE-612: - Description: If the log4j 1.x API is on the classpath (e.g. in a Syncope-based project

[jira] [Updated] (SYNCOPE-612) explicit configuration of Velocity logging

[ https://issues.apache.org/jira/browse/SYNCOPE-612?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guido Wimmel updated SYNCOPE-612: - Description: If the log4j 1.x API is on the classpath (e.g. in a Syncope-based project

[jira] [Resolved] (SYNCOPE-612) explicit configuration of Velocity logging

[ https://issues.apache.org/jira/browse/SYNCOPE-612?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guido Wimmel resolved SYNCOPE-612. -- Resolution: Fixed explicit configuration of Velocity logging

Aw: Re: prevent writing of velocity.log in Syncope 1.2.X / master?

: Francesco Chicchiriccò ilgro...@apache.org An: dev@syncope.apache.org Betreff: Re: prevent writing of velocity.log in Syncope 1.2.X / master? On 30/11/2014 20:57, Guido Wimmel wrote: Hi, I cannot deploy Syncope 1.2.X on my company's Tomcat server infrastructure. Startup fails, because

prevent writing of velocity.log in Syncope 1.2.X / master?

Hi, I cannot deploy Syncope 1.2.X on my company's Tomcat server infrastructure. Startup fails, because Velocity cannot write the file velocity.log - our Tomcat instances are not granted write access to the file system. This worked in Syncope 1.1.X, because Spring's VelocityEngineFactoryBean by

Re: [VOTE] Apache Syncope 1.2.1

+1 Best regards, Guido On 17.11.2014 10:00, Francesco Chicchiriccò wrote: I've created a 1.2.1 release, with the following artifacts up for a vote: GIT source tag (f06582b6fefacde669a589c7b35b28717ab50a6d):

[jira] [Created] (SYNCOPE-604) allow configuring empty connid location list

Guido Wimmel created SYNCOPE-604: Summary: allow configuring empty connid location list Key: SYNCOPE-604 URL: https://issues.apache.org/jira/browse/SYNCOPE-604 Project: Syncope Issue Type

[jira] [Resolved] (SYNCOPE-604) allow configuring empty connid location list

[ https://issues.apache.org/jira/browse/SYNCOPE-604?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guido Wimmel resolved SYNCOPE-604. -- Resolution: Fixed allow configuring empty connid location list

Re: [DISCUSS] Time to switch to GIT?

Hi Francesco, sorry for missing the exact point of the switch from SVN to Git, but probably good that we have discovered that the SVN repository is still writable with such a simple change. Do we have any special rules / instructions of working with the new Git repository? The branch strategy

[jira] [Commented] (SYNCOPE-574) NullPointerException in ConnInstanceDataBinder with Java 8

[ https://issues.apache.org/jira/browse/SYNCOPE-574?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14178113#comment-14178113 ] Guido Wimmel commented on SYNCOPE-574: -- Ok - I assume the fix will be applied

[jira] [Created] (SYNCOPE-574) NullPointerException in ConnInstanceDataBinder with Java 8

Guido Wimmel created SYNCOPE-574: Summary: NullPointerException in ConnInstanceDataBinder with Java 8 Key: SYNCOPE-574 URL: https://issues.apache.org/jira/browse/SYNCOPE-574 Project: Syncope

[jira] [Comment Edited] (SYNCOPE-574) NullPointerException in ConnInstanceDataBinder with Java 8

[ https://issues.apache.org/jira/browse/SYNCOPE-574?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14176983#comment-14176983 ] Guido Wimmel edited comment on SYNCOPE-574 at 10/20/14 3:30 PM

[jira] [Commented] (SYNCOPE-574) NullPointerException in ConnInstanceDataBinder with Java 8

[ https://issues.apache.org/jira/browse/SYNCOPE-574?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14176983#comment-14176983 ] Guido Wimmel commented on SYNCOPE-574: -- Probably the reason is that in Java 8

[jira] [Comment Edited] (SYNCOPE-574) NullPointerException in ConnInstanceDataBinder with Java 8

[ https://issues.apache.org/jira/browse/SYNCOPE-574?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14176983#comment-14176983 ] Guido Wimmel edited comment on SYNCOPE-574 at 10/20/14 3:32 PM

[jira] [Assigned] (SYNCOPE-574) NullPointerException in ConnInstanceDataBinder with Java 8

[ https://issues.apache.org/jira/browse/SYNCOPE-574?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guido Wimmel reassigned SYNCOPE-574: Assignee: Guido Wimmel NullPointerException in ConnInstanceDataBinder with Java 8

[jira] [Resolved] (SYNCOPE-574) NullPointerException in ConnInstanceDataBinder with Java 8

[ https://issues.apache.org/jira/browse/SYNCOPE-574?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guido Wimmel resolved SYNCOPE-574. -- Resolution: Fixed NullPointerException in ConnInstanceDataBinder with Java 8

Re: [VOTE] Apache Syncope 1.2.0

+1 I only wondered why syncope-build-tools-1.2.0-classes.jar (which is referenced from the parent pom) is not deployed on the Maven staging repo. Cheers, Guido Gesendet: Freitag, 03. Oktober 2014 um 17:27 Uhr Von: Francesco Chicchiriccò ilgro...@apache.org An: dev@syncope.apache.org

Re: [VOTE] Apache Syncope 1.2.0

Gesendet: Montag, 06. Oktober 2014 um 12:55 Uhr Von: Francesco Chicchiriccò ilgro...@apache.org An: dev@syncope.apache.org Betreff: Re: [VOTE] Apache Syncope 1.2.0 On 06/10/2014 12:49, Guido Wimmel wrote: +1 I only wondered why syncope-build-tools-1.2.0-classes.jar (which

[jira] [Resolved] (SYNCOPE-555) check for id != 0 in *Controller.resolveReference()

[ https://issues.apache.org/jira/browse/SYNCOPE-555?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guido Wimmel resolved SYNCOPE-555. -- Resolution: Fixed check for id != 0 in *Controller.resolveReference

check for id!=0 in UserController?

Hi, we observed that when UserController.resolveReferences() is called before the creation of a User via UserController.create(), Syncope tries to read the user with id==0 (via binder.getUserTO()). This always fails (which is ignored), but may cause an unnecessary query to the database and the

Aw: [VOTE] Apache Syncope 1.2.0-M1

+1 Best regards, Guido Gesendet: Montag, 08. September 2014 um 17:43 Uhr Von: Francesco Chicchiriccò ilgro...@apache.org An: dev@syncope.apache.org Betreff: [VOTE] Apache Syncope 1.2.0-M1 I've created a version release, with the following artifacts up for a vote: SVN source tag

Aw: Re: [DISCUSS] Debian packages

Hi, sounds good to me too. +1 [...] This boils down to separating the application in: configuration, binaries (jars) and application data (logs, data, database). You should be able to supply the path to the main configuration file via system property and all other configuration files

[jira] [Resolved] (SYNCOPE-531) Failed login counter not reset if log.lastlogindate==false

[ https://issues.apache.org/jira/browse/SYNCOPE-531?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guido Wimmel resolved SYNCOPE-531. -- Resolution: Fixed Failed login counter not reset if log.lastlogindate==false

[jira] [Created] (SYNCOPE-531) Failed login counter not reset if log.lastlogindate==false

Guido Wimmel created SYNCOPE-531: Summary: Failed login counter not reset if log.lastlogindate==false Key: SYNCOPE-531 URL: https://issues.apache.org/jira/browse/SYNCOPE-531 Project: Syncope

[jira] [Commented] (SYNCOPE-531) Failed login counter not reset if log.lastlogindate==false

[ https://issues.apache.org/jira/browse/SYNCOPE-531?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14052946#comment-14052946 ] Guido Wimmel commented on SYNCOPE-531: -- Just checked in a fix into 1_1_X. Verified

[jira] [Commented] (SYNCOPE-507) User login date conditional logging

[ https://issues.apache.org/jira/browse/SYNCOPE-507?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14052321#comment-14052321 ] Guido Wimmel commented on SYNCOPE-507: -- Would it be an improvement to reset

[jira] [Commented] (SYNCOPE-507) User login date conditional logging

[ https://issues.apache.org/jira/browse/SYNCOPE-507?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14052373#comment-14052373 ] Guido Wimmel commented on SYNCOPE-507: -- Ok. I also think it would be ok to possibly

Re: [VOTE] Apache Syncope 1.1.8

Gesendet: Donnerstag, 03. Juli 2014 um 14:02 Uhr Von: Francesco Chicchiriccò ilgro...@apache.org An: dev@syncope.apache.org Betreff: [VOTE] Apache Syncope 1.1.8 I've created a 1.1.8 release, with the following artifacts up for a vote: SVN source tag (r1607578):

Aw: [jira] [Resolved] (SYNCOPE-507) User login date conditional logging

Hi Francesco, about the reworked patch: a bit late and I'm unsure, but wouldn't it be more consistent to also setFailedLogins(0) on successful login even if log.lastlogindate=false? Otherwise the semantics of getFailedLogins() differs depending on the setting of log.lastlogindate, which looks

[jira] [Commented] (SYNCOPE-507) User login date conditional logging

[ https://issues.apache.org/jira/browse/SYNCOPE-507?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14051864#comment-14051864 ] Guido Wimmel commented on SYNCOPE-507: -- Hi Francesco, about the reworked patch

[jira] [Resolved] (SYNCOPE-487) make Velocity tools available in templates for notifications

[ https://issues.apache.org/jira/browse/SYNCOPE-487?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guido Wimmel resolved SYNCOPE-487. -- Resolution: Fixed make Velocity tools available in templates for notifications

[jira] [Assigned] (SYNCOPE-487) make Velocity tools available in templates for notifications

[ https://issues.apache.org/jira/browse/SYNCOPE-487?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guido Wimmel reassigned SYNCOPE-487: Assignee: Guido Wimmel make Velocity tools available in templates for notifications

[jira] [Commented] (SYNCOPE-487) make Velocity tools available in templates for notifications

[ https://issues.apache.org/jira/browse/SYNCOPE-487?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13947740#comment-13947740 ] Guido Wimmel commented on SYNCOPE-487: -- I have committed a basic implementation

[jira] [Commented] (SYNCOPE-487) make Velocity tools available in templates for notifications

[ https://issues.apache.org/jira/browse/SYNCOPE-487?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13948254#comment-13948254 ] Guido Wimmel commented on SYNCOPE-487: -- I had a problem with merging - one of my new

Aw: Re: Escaping in Velocity templates for notifications

Chicchiriccò wrote: On 10/03/2014 15:55, Guido Wimmel wrote: Hi, we have the requirement that the username in a notification mail must be URL-encoded (as part of a link inside the mail). Is there a way to do this in Syncope currently? As far as I understand the code generating the mails

Escaping in Velocity templates for notifications

Hi, we have the requirement that the username in a notification mail must be URL-encoded (as part of a link inside the mail). Is there a way to do this in Syncope currently? As far as I understand the code generating the mails (NotificationManager), probably not? If not, a way to achieve this

[jira] [Commented] (SYNCOPE-460) Default datasource uses BasicDataSource

[ https://issues.apache.org/jira/browse/SYNCOPE-460?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13859954#comment-13859954 ] Guido Wimmel commented on SYNCOPE-460: -- I've investigated a bit further

Aw: Re: BasicDataSource usage in persistence.xml

Hi Francesco, Gesendet: Dienstag, 10. Dezember 2013 um 10:20 Uhr Von: Francesco Chicchiriccò ilgro...@apache.org Gesendet: Montag, 09. Dezember 2013 um 22:22 Uhr Von: Oliver Wulff owu...@talend.com @Guido, is the property connectionProperties sufficient which is a semi-colon

Aw: Re: BasicDataSource usage in persistence.xml

Hi Oliver, FYI: we use such a setup (with dbcp.BasicDataSource) in our project, thus avoiding the need to configure a data source in the container. This works fine; also with our own unit/integration tests. We also used the standard MySQL isolation level (REPEATABLE_READ), as we had problems

Aw: RE: BasicDataSource usage in persistence.xml

in persistence.xml Will do ;-) Cheers Oli From: Francesco Chicchiriccò [ilgro...@apache.org] Sent: 06 December 2013 13:22 To: dev@syncope.apache.org Subject: Re: BasicDataSource usage in persistence.xml On 06/12/2013 12:49, Guido Wimmel wrote: Hi Oliver, FYI: we

OpenJPA dependency overlaps?

Hi,   I'm not an OpenJPA expert, but can it be the case that all OpenJPA classes needed by Syncope that are included in openjpa-2.2.2.jar are also included in {openjpa-kernel-2.2.2.jar, openjpa-jdbc-2.2.2.jar, openjpa-lib-2.2.2.jar, openjpa-persistence-2.2.2.jar,

[jira] [Created] (SYNCOPE-424) Resolve OpenJPA dependency overlap

Guido Wimmel created SYNCOPE-424: Summary: Resolve OpenJPA dependency overlap Key: SYNCOPE-424 URL: https://issues.apache.org/jira/browse/SYNCOPE-424 Project: Syncope Issue Type: Improvement

[jira] [Updated] (SYNCOPE-424) Resolve OpenJPA dependency overlap

[ https://issues.apache.org/jira/browse/SYNCOPE-424?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guido Wimmel updated SYNCOPE-424: - Attachment: syncopeOpenJPADependencies.patch Attached a patch that removes the dependency

[jira] [Created] (SYNCOPE-415) Reduce log level of bean validation errors

Guido Wimmel created SYNCOPE-415: Summary: Reduce log level of bean validation errors Key: SYNCOPE-415 URL: https://issues.apache.org/jira/browse/SYNCOPE-415 Project: Syncope Issue Type

[jira] [Created] (SYNCOPE-416) AttributableSearchDAOImpl / Avoid query construction with string concatenation

Guido Wimmel created SYNCOPE-416: Summary: AttributableSearchDAOImpl / Avoid query construction with string concatenation Key: SYNCOPE-416 URL: https://issues.apache.org/jira/browse/SYNCOPE-416

Aw: Re: EntityValidationInterceptor / log level of bean validation errors

Hi Francesco, Gesendet: Dienstag, 10. September 2013 um 15:18 Uhr Von: Francesco Chicchiriccò ilgro...@apache.org An: dev@syncope.apache.org Betreff: Re: EntityValidationInterceptor / log level of bean validation errors On 10/09/2013 13:27, Guido Wimmel wrote: currently

[jira] [Updated] (SYNCOPE-411) Perform retries on failed notifications

[ https://issues.apache.org/jira/browse/SYNCOPE-411?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guido Wimmel updated SYNCOPE-411: - Component/s: (was: console) Perform retries on failed notifications

[jira] [Updated] (SYNCOPE-411) Perform retries on failed notifications

[ https://issues.apache.org/jira/browse/SYNCOPE-411?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guido Wimmel updated SYNCOPE-411: - Attachment: syncopeNotificationRetry.patch Perform retries on failed notifications

[jira] [Commented] (SYNCOPE-411) Perform retries on failed notifications

[ https://issues.apache.org/jira/browse/SYNCOPE-411?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13739597#comment-13739597 ] Guido Wimmel commented on SYNCOPE-411: -- I have attached a patch with a possible

[jira] [Created] (SYNCOPE-411) Perform retries on failed notifications

Guido Wimmel created SYNCOPE-411: Summary: Perform retries on failed notifications Key: SYNCOPE-411 URL: https://issues.apache.org/jira/browse/SYNCOPE-411 Project: Syncope Issue Type

[jira] [Commented] (SYNCOPE-411) Perform retries on failed notifications

[ https://issues.apache.org/jira/browse/SYNCOPE-411?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13736867#comment-13736867 ] Guido Wimmel commented on SYNCOPE-411: -- A possible way to implement this could

[jira] [Created] (SYNCOPE-410) Make username pattern configurable via account policy

Guido Wimmel created SYNCOPE-410: Summary: Make username pattern configurable via account policy Key: SYNCOPE-410 URL: https://issues.apache.org/jira/browse/SYNCOPE-410 Project: Syncope

[jira] [Commented] (SYNCOPE-410) Make username pattern configurable via account policy

[ https://issues.apache.org/jira/browse/SYNCOPE-410?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13734849#comment-13734849 ] Guido Wimmel commented on SYNCOPE-410: -- I've attached a patch with a suggested

[jira] [Updated] (SYNCOPE-410) Make username pattern configurable via account policy

[ https://issues.apache.org/jira/browse/SYNCOPE-410?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guido Wimmel updated SYNCOPE-410: - Attachment: syncopeAccountPolicyPattern.patch Make username pattern configurable via

[jira] [Commented] (SYNCOPE-409) Allow notifications with empty about field

[ https://issues.apache.org/jira/browse/SYNCOPE-409?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13733571#comment-13733571 ] Guido Wimmel commented on SYNCOPE-409: -- I tried to provide an implementation

Re: AccountPolicyEnforcer / allowed characters in username

to keep regexp in object as is. +1 for Guido proposal. Rgds, F. Francesco Chicchiriccò ilgro...@apache.org ha scritto: On 02/08/2013 10:22, Guido Wimmel wrote: Hi, is there a specific reason for the particular fixed choice of characters allowed in Syncope usernames

AccountPolicyEnforcer / allowed characters in username

Hi,   is there a specific reason for the particular fixed choice of characters allowed in Syncope usernames? ( AccountPolicyEnforcer.PATTERN = Pattern.compile([a-zA-Z0-9-_@. ]+); ) We use email addresses as usernames, so we had create our own modified copy of AccountPolicyEnforcer to extend

[jira] [Updated] (SYNCOPE-408) Add index on task.executed

[ https://issues.apache.org/jira/browse/SYNCOPE-408?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guido Wimmel updated SYNCOPE-408: - Attachment: indexes.xml.patch Add index on task.executed

  1   2   >