[jira] [Commented] (SYNCOPE-457) Must be able to configure JavaMailSender used by NotificationJob
[
https://issues.apache.org/jira/browse/SYNCOPE-457?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13837437#comment-13837437
]
Francesco Chicchiriccò commented on SYNCOPE-457:
IMO, according to Syncope configuration style, I'd move {{smtp.host}} and
{{smtp.port}} out of {{SyncopeConf}} and define a {{JavaMailSenderImpl}} Spring
bean in {{core/src/main/resources/syncopeContext.xml}}, with parameters from an
external {{core/src/main/resources/mail.properties}}.
Finally, {{JavaMailSenderImpl}} will be {{@Autowired}} in {{NotificationJob}}.
WDYT?
Must be able to configure JavaMailSender used by NotificationJob
Key: SYNCOPE-457
URL: https://issues.apache.org/jira/browse/SYNCOPE-457
Project: Syncope
Issue Type: Bug
Components: core
Affects Versions: 1.1.5, 1.2.0
Reporter: Hadrian Zbarcea
Assignee: Hadrian Zbarcea
Fix For: 1.2.0
In NotificationJob.executeSingle we instantiate a new JavaMailSenderImpl()
which we then populate with some values. There are however other properties
[1] that can be set on the Session. Some of them are very useful, especially
in production environments.
In particular, the 'mail.smtp.connectiontimeout' should be set to a different
value than the default 'infinite' which would cause the thread to hang,
waiting for a unresponsive SMTP server (either misconfiguration of server
down).
I will try to come up with a patch towards the end of the week if nobody
beats me to it.
[1] https://javamail.java.net/nonav/docs/api/
--
This message was sent by Atlassian JIRA
(v6.1#6144)
[jira] [Commented] (SYNCOPE-450) Support JAX-RS 2.0
[ https://issues.apache.org/jira/browse/SYNCOPE-450?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13837522#comment-13837522 ] ASF subversion and git services commented on SYNCOPE-450: - Commit 1547331 from [~ilgrosso] in branch 'syncope/trunk' [ https://svn.apache.org/r1547331 ] [SYNCOPE-450] CXF 3.0.0-SNAPSHOT updated artifacts finally available Support JAX-RS 2.0 -- Key: SYNCOPE-450 URL: https://issues.apache.org/jira/browse/SYNCOPE-450 Project: Syncope Issue Type: Improvement Components: client, core Reporter: Francesco Chicchiriccò Assignee: Francesco Chicchiriccò Fix For: 1.2.0 Attachments: SYNCOPE-450.patch Upgrade CXF to 3.0.0 (3.0.0-milestone1 has been recently released) and benefit from JAX-RS upgrade to 2.0 there. Migration guide: https://cwiki.apache.org/confluence/display/CXF20DOC/JAX-RS#JAX-RS-FromCXF2.7.xtoCXF3.0.0 -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Resolved] (SYNCOPE-450) Support JAX-RS 2.0
[ https://issues.apache.org/jira/browse/SYNCOPE-450?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Francesco Chicchiriccò resolved SYNCOPE-450. Resolution: Fixed Support JAX-RS 2.0 -- Key: SYNCOPE-450 URL: https://issues.apache.org/jira/browse/SYNCOPE-450 Project: Syncope Issue Type: Improvement Components: client, core Reporter: Francesco Chicchiriccò Assignee: Francesco Chicchiriccò Fix For: 1.2.0 Attachments: SYNCOPE-450.patch Upgrade CXF to 3.0.0 (3.0.0-milestone1 has been recently released) and benefit from JAX-RS upgrade to 2.0 there. Migration guide: https://cwiki.apache.org/confluence/display/CXF20DOC/JAX-RS#JAX-RS-FromCXF2.7.xtoCXF3.0.0 -- This message was sent by Atlassian JIRA (v6.1#6144)
Re: [DISCUSS] JavaFX or Swing to Apache Syncope installer GUI
On 02/12/2013 10:37, Massimiliano Perrone wrote: Hi dev, I would like to close this issue [1]. IMO the only two possible way are: 1) Swing; 2) JavaFX. I found several debate about the topic JavaFX vs Swing and the better answer on it are [2] [3]. In summary: *) Java 6 will not run JavaFX 2 out of the box. *) From OpenJDK website: The project intends to file a JSR in the Java SE 9 timeframe and hopes to eventually be part of the JDK proper. *) JavaFX 2 offers good integration with Java Webstart So, I would have liked to use JavaFX but I think that the right choice is to use Swing. Any other suggestion? Hi Max, generally speaking, I must agree with you: JavaFX 2 could be nice, but is not the ideal solution either for not being natively supported by Java 6 and possibly for other weird license issues that can come out from Oracle. Why don't you give a chance to IzPack [4]? It seems to be widely used, and has a good license (AL 2.0). Regards. [1] https://issues.apache.org/jira/browse/SYNCOPE-143 [2] http://stackoverflow.com/questions/1318645/javafx-or-swing [3] http://stackoverflow.com/questions/13696061/will-java-6-latest-run-javafx-2-out-of-the-bo [4] http://izpack.org/ -- Francesco Chicchiriccò Tirasa - Open Source Excellence http://www.tirasa.net/ ASF Member, Apache Syncope PMC chair, Apache Cocoon PMC Member http://people.apache.org/~ilgrosso/
[jira] [Assigned] (SYNCOPE-452) Generated project not starting in embedded mode
[
https://issues.apache.org/jira/browse/SYNCOPE-452?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Francesco Chicchiriccò reassigned SYNCOPE-452:
--
Assignee: Francesco Chicchiriccò
Generated project not starting in embedded mode
---
Key: SYNCOPE-452
URL: https://issues.apache.org/jira/browse/SYNCOPE-452
Project: Syncope
Issue Type: Bug
Components: archetype
Affects Versions: 1.1.5
Environment: embedded mode
Reporter: fabio martelli
Assignee: Francesco Chicchiriccò
Fix For: 1.1.6, 1.2.0
When generating new project by following instructions at
https://cwiki.apache.org/confluence/display/SYNCOPE/Create+a+new+Syncope+project
and starting via -Pembedded syncope doesn't work. See the following
exception for details.
Caused by: org.springframework.beans.factory.BeanCreationException: Could not
autowire field: private
org.apache.syncope.core.workflow.user.UserWorkflowAdapter
org.apache.syncope.core.rest.controller.WorkflowController.uwfAdapter; nested
exception is org.springframework.beans.factory.CannotLoadBeanClassException:
Cannot find class
[org.apache.syncope.core.rest.data.DoubleValueAttributableTransformer] for
bean with name '${attributableTransformer}#0' defined in file
[/tmp/pp/console/target/cargo/configurations/tomcat7x/webapps/syncope/WEB-INF/classes/restContext.xml];
nested exception is java.lang.ClassNotFoundException:
org.apache.syncope.core.rest.data.DoubleValueAttributableTransformer
at
org.springframework.beans.factory.annotation.AutowiredAnnotationBeanPostProcessor$AutowiredFieldElement.inject(AutowiredAnnotationBeanPostProcessor.java:517)
~[spring-beans-3.2.5.RELEASE.jar:3.2.5.RELEASE]
at
org.springframework.beans.factory.annotation.InjectionMetadata.inject(InjectionMetadata.java:87)
~[spring-beans-3.2.5.RELEASE.jar:3.2.5.RELEASE]
at
org.springframework.beans.factory.annotation.AutowiredAnnotationBeanPostProcessor.postProcessPropertyValues(AutowiredAnnotationBeanPostProcessor.java:286)
~[spring-beans-3.2.5.RELEASE.jar:3.2.5.RELEASE]
... 27 common frames omitted
Caused by: org.springframework.beans.factory.CannotLoadBeanClassException:
Cannot find class
[org.apache.syncope.core.rest.data.DoubleValueAttributableTransformer] for
bean with name '${attributableTransformer}#0' defined in file
[/tmp/pp/console/target/cargo/configurations/tomcat7x/webapps/syncope/WEB-INF/classes/restContext.xml];
nested exception is java.lang.ClassNotFoundException:
org.apache.syncope.core.rest.data.DoubleValueAttributableTransformer
--
This message was sent by Atlassian JIRA
(v6.1#6144)
[jira] [Reopened] (SYNCOPE-456) TaskTestITCase failures
[
https://issues.apache.org/jira/browse/SYNCOPE-456?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hadrian Zbarcea reopened SYNCOPE-456:
-
Sorry, I had a temporary brain freeze. In core/src/test/resources/content.xml,
he hostname should be not-existing.syncope.apache.org not not-existing@s.a.o
('dot' instead of '@'). It does work but it's not quite a correct fqdn :).
Doh...
TaskTestITCase failures
---
Key: SYNCOPE-456
URL: https://issues.apache.org/jira/browse/SYNCOPE-456
Project: Syncope
Issue Type: Bug
Components: core
Affects Versions: 1.2.0
Reporter: Hadrian Zbarcea
Assignee: Hadrian Zbarcea
Attachments: syncope-456.patch
Both issueSYNCOPE81 and issueSYNCOPE86 fail on my system. The symptom is that
TaskController.execute hangs (the line below is the last in the log) and then
there is a timeout on the client side.
22:46:09.087 DEBUG org.apache.syncope.core.rest.controller.ControllerHandler
- Before TaskController.execute([101, false])
I am not sure if anybody saw this, if so please add a comment. I reproduce
the issue consistently on my Ubuntu laptop with both sun and openjdk 6.
Others don't see it in an environment similar to mine. I also saw it on a
CentOS server. I cannot reproduce it on osx though. It is quite likely
related to the environment, but nevertheless syncope should be more robust
and handle errors gracefully in a misconfigured environment.
Since I have environments that both work and don't, I will try to dig deeper,
compare the two and see what the culprit is.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
[jira] [Commented] (SYNCOPE-456) TaskTestITCase failures
[ https://issues.apache.org/jira/browse/SYNCOPE-456?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13837631#comment-13837631 ] Hadrian Zbarcea commented on SYNCOPE-456: - Hmm, but with a valid fqdn I have the same issue :(. Let me dig into this a bit more. There may be some other configuration needed. For now, I think best is to leave this as is (as the tests pass), and I'll put a better fix with SYNCOPE-457. Is that ok? TaskTestITCase failures --- Key: SYNCOPE-456 URL: https://issues.apache.org/jira/browse/SYNCOPE-456 Project: Syncope Issue Type: Bug Components: core Affects Versions: 1.2.0 Reporter: Hadrian Zbarcea Assignee: Hadrian Zbarcea Attachments: syncope-456.patch Both issueSYNCOPE81 and issueSYNCOPE86 fail on my system. The symptom is that TaskController.execute hangs (the line below is the last in the log) and then there is a timeout on the client side. 22:46:09.087 DEBUG org.apache.syncope.core.rest.controller.ControllerHandler - Before TaskController.execute([101, false]) I am not sure if anybody saw this, if so please add a comment. I reproduce the issue consistently on my Ubuntu laptop with both sun and openjdk 6. Others don't see it in an environment similar to mine. I also saw it on a CentOS server. I cannot reproduce it on osx though. It is quite likely related to the environment, but nevertheless syncope should be more robust and handle errors gracefully in a misconfigured environment. Since I have environments that both work and don't, I will try to dig deeper, compare the two and see what the culprit is. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Resolved] (SYNCOPE-456) TaskTestITCase failures
[ https://issues.apache.org/jira/browse/SYNCOPE-456?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hadrian Zbarcea resolved SYNCOPE-456. - Resolution: Fixed TaskTestITCase failures --- Key: SYNCOPE-456 URL: https://issues.apache.org/jira/browse/SYNCOPE-456 Project: Syncope Issue Type: Bug Components: core Affects Versions: 1.2.0 Reporter: Hadrian Zbarcea Assignee: Hadrian Zbarcea Attachments: syncope-456.patch Both issueSYNCOPE81 and issueSYNCOPE86 fail on my system. The symptom is that TaskController.execute hangs (the line below is the last in the log) and then there is a timeout on the client side. 22:46:09.087 DEBUG org.apache.syncope.core.rest.controller.ControllerHandler - Before TaskController.execute([101, false]) I am not sure if anybody saw this, if so please add a comment. I reproduce the issue consistently on my Ubuntu laptop with both sun and openjdk 6. Others don't see it in an environment similar to mine. I also saw it on a CentOS server. I cannot reproduce it on osx though. It is quite likely related to the environment, but nevertheless syncope should be more robust and handle errors gracefully in a misconfigured environment. Since I have environments that both work and don't, I will try to dig deeper, compare the two and see what the culprit is. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Commented] (SYNCOPE-457) Must be able to configure JavaMailSender used by NotificationJob
[ https://issues.apache.org/jira/browse/SYNCOPE-457?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13837633#comment-13837633 ] Hadrian Zbarcea commented on SYNCOPE-457: - I was thinking about something along the same lines. It has the added advantage of not creating a new JavaMailSenderImpl instance for every send. What I am not yet sure about is if we need to have an SMTP host per sender. Can we have multiple/different senders? Still a noob on syncope :). Must be able to configure JavaMailSender used by NotificationJob Key: SYNCOPE-457 URL: https://issues.apache.org/jira/browse/SYNCOPE-457 Project: Syncope Issue Type: Bug Components: core Affects Versions: 1.1.5, 1.2.0 Reporter: Hadrian Zbarcea Assignee: Hadrian Zbarcea Fix For: 1.2.0 In NotificationJob.executeSingle we instantiate a new JavaMailSenderImpl() which we then populate with some values. There are however other properties [1] that can be set on the Session. Some of them are very useful, especially in production environments. In particular, the 'mail.smtp.connectiontimeout' should be set to a different value than the default 'infinite' which would cause the thread to hang, waiting for a unresponsive SMTP server (either misconfiguration of server down). I will try to come up with a patch towards the end of the week if nobody beats me to it. [1] https://javamail.java.net/nonav/docs/api/ -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Commented] (SYNCOPE-456) TaskTestITCase failures
[ https://issues.apache.org/jira/browse/SYNCOPE-456?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13837634#comment-13837634 ] Francesco Chicchiriccò commented on SYNCOPE-456: +1 TaskTestITCase failures --- Key: SYNCOPE-456 URL: https://issues.apache.org/jira/browse/SYNCOPE-456 Project: Syncope Issue Type: Bug Components: core Affects Versions: 1.2.0 Reporter: Hadrian Zbarcea Assignee: Hadrian Zbarcea Attachments: syncope-456.patch Both issueSYNCOPE81 and issueSYNCOPE86 fail on my system. The symptom is that TaskController.execute hangs (the line below is the last in the log) and then there is a timeout on the client side. 22:46:09.087 DEBUG org.apache.syncope.core.rest.controller.ControllerHandler - Before TaskController.execute([101, false]) I am not sure if anybody saw this, if so please add a comment. I reproduce the issue consistently on my Ubuntu laptop with both sun and openjdk 6. Others don't see it in an environment similar to mine. I also saw it on a CentOS server. I cannot reproduce it on osx though. It is quite likely related to the environment, but nevertheless syncope should be more robust and handle errors gracefully in a misconfigured environment. Since I have environments that both work and don't, I will try to dig deeper, compare the two and see what the culprit is. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Commented] (SYNCOPE-457) Must be able to configure JavaMailSender used by NotificationJob
[
https://issues.apache.org/jira/browse/SYNCOPE-457?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13837635#comment-13837635
]
Francesco Chicchiriccò commented on SYNCOPE-457:
I think a singleton {{JavaMailSenderImpl}} should fit the job.
Must be able to configure JavaMailSender used by NotificationJob
Key: SYNCOPE-457
URL: https://issues.apache.org/jira/browse/SYNCOPE-457
Project: Syncope
Issue Type: Bug
Components: core
Affects Versions: 1.1.5, 1.2.0
Reporter: Hadrian Zbarcea
Assignee: Hadrian Zbarcea
Fix For: 1.2.0
In NotificationJob.executeSingle we instantiate a new JavaMailSenderImpl()
which we then populate with some values. There are however other properties
[1] that can be set on the Session. Some of them are very useful, especially
in production environments.
In particular, the 'mail.smtp.connectiontimeout' should be set to a different
value than the default 'infinite' which would cause the thread to hang,
waiting for a unresponsive SMTP server (either misconfiguration of server
down).
I will try to come up with a patch towards the end of the week if nobody
beats me to it.
[1] https://javamail.java.net/nonav/docs/api/
--
This message was sent by Atlassian JIRA
(v6.1#6144)
[jira] [Resolved] (SYNCOPE-452) Generated project not starting in embedded mode
[
https://issues.apache.org/jira/browse/SYNCOPE-452?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Francesco Chicchiriccò resolved SYNCOPE-452.
Resolution: Fixed
Generated project not starting in embedded mode
---
Key: SYNCOPE-452
URL: https://issues.apache.org/jira/browse/SYNCOPE-452
Project: Syncope
Issue Type: Bug
Components: archetype
Affects Versions: 1.1.5
Environment: embedded mode
Reporter: fabio martelli
Assignee: Francesco Chicchiriccò
Fix For: 1.1.6, 1.2.0
When generating new project by following instructions at
https://cwiki.apache.org/confluence/display/SYNCOPE/Create+a+new+Syncope+project
and starting via -Pembedded syncope doesn't work. See the following
exception for details.
Caused by: org.springframework.beans.factory.BeanCreationException: Could not
autowire field: private
org.apache.syncope.core.workflow.user.UserWorkflowAdapter
org.apache.syncope.core.rest.controller.WorkflowController.uwfAdapter; nested
exception is org.springframework.beans.factory.CannotLoadBeanClassException:
Cannot find class
[org.apache.syncope.core.rest.data.DoubleValueAttributableTransformer] for
bean with name '${attributableTransformer}#0' defined in file
[/tmp/pp/console/target/cargo/configurations/tomcat7x/webapps/syncope/WEB-INF/classes/restContext.xml];
nested exception is java.lang.ClassNotFoundException:
org.apache.syncope.core.rest.data.DoubleValueAttributableTransformer
at
org.springframework.beans.factory.annotation.AutowiredAnnotationBeanPostProcessor$AutowiredFieldElement.inject(AutowiredAnnotationBeanPostProcessor.java:517)
~[spring-beans-3.2.5.RELEASE.jar:3.2.5.RELEASE]
at
org.springframework.beans.factory.annotation.InjectionMetadata.inject(InjectionMetadata.java:87)
~[spring-beans-3.2.5.RELEASE.jar:3.2.5.RELEASE]
at
org.springframework.beans.factory.annotation.AutowiredAnnotationBeanPostProcessor.postProcessPropertyValues(AutowiredAnnotationBeanPostProcessor.java:286)
~[spring-beans-3.2.5.RELEASE.jar:3.2.5.RELEASE]
... 27 common frames omitted
Caused by: org.springframework.beans.factory.CannotLoadBeanClassException:
Cannot find class
[org.apache.syncope.core.rest.data.DoubleValueAttributableTransformer] for
bean with name '${attributableTransformer}#0' defined in file
[/tmp/pp/console/target/cargo/configurations/tomcat7x/webapps/syncope/WEB-INF/classes/restContext.xml];
nested exception is java.lang.ClassNotFoundException:
org.apache.syncope.core.rest.data.DoubleValueAttributableTransformer
--
This message was sent by Atlassian JIRA
(v6.1#6144)
[jira] [Commented] (SYNCOPE-453) Propagation problem with role virtual attribute mapped in user mapping
[ https://issues.apache.org/jira/browse/SYNCOPE-453?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13837764#comment-13837764 ] ASF subversion and git services commented on SYNCOPE-453: - Commit 1547414 from [~fmartelli] in branch 'syncope/branches/1_1_X' [ https://svn.apache.org/r1547414 ] Fixes SYNCOPE-453 on 1.1.X Propagation problem with role virtual attribute mapped in user mapping --- Key: SYNCOPE-453 URL: https://issues.apache.org/jira/browse/SYNCOPE-453 Project: Syncope Issue Type: Bug Components: core Affects Versions: 1.1.5 Reporter: fabio martelli Assignee: fabio martelli Fix For: 1.1.6, 1.2.0 Mapped role virtual attributes (read-only or not) in user mapping are ignotred during propagation. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Assigned] (SYNCOPE-454) Update user without password specification involving resource with Generate password if missing enabled, sends password out anyway
[ https://issues.apache.org/jira/browse/SYNCOPE-454?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Francesco Chicchiriccò reassigned SYNCOPE-454: -- Assignee: Francesco Chicchiriccò Update user without password specification involving resource with Generate password if missing enabled, sends password out anyway Key: SYNCOPE-454 URL: https://issues.apache.org/jira/browse/SYNCOPE-454 Project: Syncope Issue Type: Bug Components: core Affects Versions: 1.1.5 Reporter: fabio martelli Assignee: Francesco Chicchiriccò Fix For: 1.1.6, 1.2.0 Updating an existing user on an external resource with Generate password if missing enabled, without requiring password update explicitly, autogenerated password is sent by default. Of course, this is a WRONG behavior that can cause unexpected failures. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Resolved] (SYNCOPE-453) Propagation problem with role virtual attribute mapped in user mapping
[ https://issues.apache.org/jira/browse/SYNCOPE-453?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] fabio martelli resolved SYNCOPE-453. Resolution: Fixed Propagation problem with role virtual attribute mapped in user mapping --- Key: SYNCOPE-453 URL: https://issues.apache.org/jira/browse/SYNCOPE-453 Project: Syncope Issue Type: Bug Components: core Affects Versions: 1.1.5 Reporter: fabio martelli Assignee: fabio martelli Fix For: 1.1.6, 1.2.0 Mapped role virtual attributes (read-only or not) in user mapping are ignotred during propagation. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Commented] (SYNCOPE-454) Update user without password specification involving resource with Generate password if missing enabled, sends password out anyway
[
https://issues.apache.org/jira/browse/SYNCOPE-454?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13837895#comment-13837895
]
Francesco Chicchiriccò commented on SYNCOPE-454:
Simple code for showing this issue:
{code}
// 1. create user with LDAP resource (with 'Generate password if missing'
enabled)
UserTO userTO = getUniqueSampleTO(syncope...@syncope.apache.org);
userTO.getResources().add(RESOURCE_NAME_LDAP);
userTO = createUser(userTO);
assertNotNull(userTO);
// 2. read resource configuration for LDAP binding
ResourceTO ldapRes = resourceService.read(RESOURCE_NAME_LDAP);
MapString, ConnConfProperty ldapConnConf =
connectorService.read(ldapRes.getConnectorId()).getConfigurationMap();
ConnObjectTO connObject =
resourceService.getConnectorObject(RESOURCE_NAME_LDAP, AttributableType.USER,
userTO.getId());
Hashtable env = new Hashtable();
env.put(Context.INITIAL_CONTEXT_FACTORY, com.sun.jndi.ldap.LdapCtxFactory);
env.put(Context.PROVIDER_URL, ldap://; +
ldapConnConf.get(host).getValues().get(0)
+ : + ldapConnConf.get(port).getValues().get(0) + /);
env.put(Context.SECURITY_AUTHENTICATION, simple);
env.put(Context.SECURITY_PRINCIPAL,
connObject.getAttrMap().get(__NAME__).getValues().get(0));
env.put(Context.SECURITY_CREDENTIALS, password123);
// 3. try (and succeed) to perform simple LDAP binding with provided password
('password123')
new InitialDirContext(env);
// 4. update user without any password change request
UserMod userMod = new UserMod();
userMod.setId(userTO.getId());
userMod.setUsername(userTO.getUsername() + XX);
userService.update(userTO.getId(), userMod);
// 5. try (and fail) to perform simple LDAP binding: password has changed
new InitialDirContext(env);
{code}
Update user without password specification involving resource with Generate
password if missing enabled, sends password out anyway
Key: SYNCOPE-454
URL: https://issues.apache.org/jira/browse/SYNCOPE-454
Project: Syncope
Issue Type: Bug
Components: core
Affects Versions: 1.1.5
Reporter: fabio martelli
Assignee: Francesco Chicchiriccò
Fix For: 1.1.6, 1.2.0
Updating an existing user on an external resource with Generate password if
missing enabled, without requiring password update explicitly, autogenerated
password is sent by default.
Of course, this is a WRONG behavior that can cause unexpected failures.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
[jira] [Created] (SYNCOPE-458) Change membership virtual attribute management
fabio martelli created SYNCOPE-458: -- Summary: Change membership virtual attribute management Key: SYNCOPE-458 URL: https://issues.apache.org/jira/browse/SYNCOPE-458 Project: Syncope Issue Type: Bug Components: core Affects Versions: 1.1.5 Reporter: fabio martelli Fix For: 1.2.0 Consider that memberships are not directly interested by a propagation. Membership virtual attribute have to be considered like user virtual attribute: 1. retrieve membership virtual attribute values as done for user attributes 2. manage membership virtual attributes during propagation (create/update) 3. manage membership virtual attributes during membership remove -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Updated] (SYNCOPE-457) Must be able to configure JavaMailSender used by NotificationJob
[ https://issues.apache.org/jira/browse/SYNCOPE-457?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hadrian Zbarcea updated SYNCOPE-457: Attachment: syncope-457.patch Must be able to configure JavaMailSender used by NotificationJob Key: SYNCOPE-457 URL: https://issues.apache.org/jira/browse/SYNCOPE-457 Project: Syncope Issue Type: Bug Components: core Affects Versions: 1.1.5, 1.2.0 Reporter: Hadrian Zbarcea Assignee: Hadrian Zbarcea Fix For: 1.2.0 Attachments: syncope-457.patch In NotificationJob.executeSingle we instantiate a new JavaMailSenderImpl() which we then populate with some values. There are however other properties [1] that can be set on the Session. Some of them are very useful, especially in production environments. In particular, the 'mail.smtp.connectiontimeout' should be set to a different value than the default 'infinite' which would cause the thread to hang, waiting for a unresponsive SMTP server (either misconfiguration of server down). I will try to come up with a patch towards the end of the week if nobody beats me to it. [1] https://javamail.java.net/nonav/docs/api/ -- This message was sent by Atlassian JIRA (v6.1#6144)
