[jira] [Updated] (SYNCOPE-514) Core doesn't deploy on Glassfish

2014-06-23 Thread JIRA 

 [ 
https://issues.apache.org/jira/browse/SYNCOPE-514?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Francesco Chicchiriccò updated SYNCOPE-514:
---

  Description: 
Now, trying to deploy the core on Glassfish 4 the result is:
[17:07:50.688][info][talledLocalContainer] remote failure: Error occurred 
during deployment: Exception while loading the app : 
java.lang.IllegalStateException: ContainerBase.addChild: start: 
org.apache.catalina.LifecycleException: 
org.springframework.beans.factory.BeanCreationException: Error creating bean 
with name 'validator' defined in file 
[/tmp/trunk/core/target/syncope-core-test/WEB-INF/classes/persistenceContext.xml]:
 Invocation of init method failed; nested exception is 
java.lang.AbstractMethodError: 
org.apache.bval.jsr303.ConfigurationImpl.getDefaultParameterNameProvider()Ljavax/validation/ParameterNameProvider;.
 Please see server.log for more details.

I have been able to deploy it deleting bval dependencies and replacing them 
with hibernate-validator libraries.

Considering that SYNCOPE-46 suggests to replace BVal with Hibernate Validator, 
what do you think to replace it now?

  was:
Now, trying to deploy the core on Glassfish 4 the result is:
[17:07:50.688][info][talledLocalContainer] remote failure: Error occurred 
during deployment: Exception while loading the app : 
java.lang.IllegalStateException: ContainerBase.addChild: start: 
org.apache.catalina.LifecycleException: 
org.springframework.beans.factory.BeanCreationException: Error creating bean 
with name 'validator' defined in file 
[/tmp/trunk/core/target/syncope-core-test/WEB-INF/classes/persistenceContext.xml]:
 Invocation of init method failed; nested exception is 
java.lang.AbstractMethodError: 
org.apache.bval.jsr303.ConfigurationImpl.getDefaultParameterNameProvider()Ljavax/validation/ParameterNameProvider;.
 Please see server.log for more details.

I have been able to deploy it deleting bval dependencies and replacing them 
with hibernate-validator libraries.

Considering that a 
href=https://issues.apache.org/jira/browse/SYNCOPE-461;SYNCOPE-461/a issue 
suggests to replace the bval libreries, what do you think to replace it now?

  Environment: Glassfish 4
Fix Version/s: 1.2.0

 Core doesn't deploy on Glassfish
 

 Key: SYNCOPE-514
 URL: https://issues.apache.org/jira/browse/SYNCOPE-514
 Project: Syncope
  Issue Type: Bug
  Components: core
Affects Versions: 1.2.0
 Environment: Glassfish 4
Reporter: Massimiliano Perrone
Assignee: Massimiliano Perrone
 Fix For: 1.2.0


 Now, trying to deploy the core on Glassfish 4 the result is:
 [17:07:50.688][info][talledLocalContainer] remote failure: Error occurred 
 during deployment: Exception while loading the app : 
 java.lang.IllegalStateException: ContainerBase.addChild: start: 
 org.apache.catalina.LifecycleException: 
 org.springframework.beans.factory.BeanCreationException: Error creating bean 
 with name 'validator' defined in file 
 [/tmp/trunk/core/target/syncope-core-test/WEB-INF/classes/persistenceContext.xml]:
  Invocation of init method failed; nested exception is 
 java.lang.AbstractMethodError: 
 org.apache.bval.jsr303.ConfigurationImpl.getDefaultParameterNameProvider()Ljavax/validation/ParameterNameProvider;.
  Please see server.log for more details.
 I have been able to deploy it deleting bval dependencies and replacing them 
 with hibernate-validator libraries.
 Considering that SYNCOPE-46 suggests to replace BVal with Hibernate 
 Validator, what do you think to replace it now?



--
This message was sent by Atlassian JIRA
(v6.2#6252)

[jira] [Commented] (SYNCOPE-514) Core doesn't deploy on Glassfish

2014-06-23 Thread JIRA 

[ 
https://issues.apache.org/jira/browse/SYNCOPE-514?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14040868#comment-14040868
 ] 

Francesco Chicchiriccò commented on SYNCOPE-514:


Unfortunately it seems that BVal is stuck in its pre-1.1 spec implementation 
since a (long) while: I would prefer being more ASF-friendly, but it seems that 
Hibernate Validator - licensed under ASF 2.0, so no license issues - is the 
logical choice.

+1 from me

 Core doesn't deploy on Glassfish
 

 Key: SYNCOPE-514
 URL: https://issues.apache.org/jira/browse/SYNCOPE-514
 Project: Syncope
  Issue Type: Bug
  Components: core
Affects Versions: 1.2.0
 Environment: Glassfish 4
Reporter: Massimiliano Perrone
Assignee: Massimiliano Perrone
 Fix For: 1.2.0


 Now, trying to deploy the core on Glassfish 4 the result is:
 [17:07:50.688][info][talledLocalContainer] remote failure: Error occurred 
 during deployment: Exception while loading the app : 
 java.lang.IllegalStateException: ContainerBase.addChild: start: 
 org.apache.catalina.LifecycleException: 
 org.springframework.beans.factory.BeanCreationException: Error creating bean 
 with name 'validator' defined in file 
 [/tmp/trunk/core/target/syncope-core-test/WEB-INF/classes/persistenceContext.xml]:
  Invocation of init method failed; nested exception is 
 java.lang.AbstractMethodError: 
 org.apache.bval.jsr303.ConfigurationImpl.getDefaultParameterNameProvider()Ljavax/validation/ParameterNameProvider;.
  Please see server.log for more details.
 I have been able to deploy it deleting bval dependencies and replacing them 
 with hibernate-validator libraries.
 Considering that SYNCOPE-46 suggests to replace BVal with Hibernate 
 Validator, what do you think to replace it now?



--
This message was sent by Atlassian JIRA
(v6.2#6252)

[jira] [Commented] (SYNCOPE-505) Support propagating non-cleartext passwords to external resources

2014-06-23 Thread Colm O hEigeartaigh (JIRA) 

[ 
https://issues.apache.org/jira/browse/SYNCOPE-505?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14040896#comment-14040896
 ] 

Colm O hEigeartaigh commented on SYNCOPE-505:
-

Hi Francesco,

I have this working for LDAP as well but wanted to validate my approach.

For the DB Connector we are sending an extra attribute over to tell the 
Connector that the password is already hashed. For LDAP, we could do this as 
well, but I implemented the reverse of the Sync Action. So if the configured 
cipher algorithm of the user matches that of the LDAP Connector, it takes the 
user password, de-hexes it + Base64 encodes it. It then writes out the same 
type of value that it syncs, i.e. {sha}XYZ...==.

The LDAP Connector needs a change to detect a password of this form { + 
matching digest + } + rest-of-password, and if so it simply stores the 
received password as is.

WDYT?

Colm.

 Support propagating non-cleartext passwords to external resources
 -

 Key: SYNCOPE-505
 URL: https://issues.apache.org/jira/browse/SYNCOPE-505
 Project: Syncope
  Issue Type: Improvement
  Components: core
Reporter: Francesco Chicchiriccò
Assignee: Colm O hEigeartaigh
 Fix For: 1.2.0


 Similarly to SYNCOPE-313 during synchronization, it seems feasible to provide 
 some Propagation Actions classes (say {{DBPasswordPropagationActions}} and 
 {{LDAPPasswordPropagationActions}} that will propagate non-cleartext password 
 values to external resources.
 This might require some changes in the related connector bundles.



--
This message was sent by Atlassian JIRA
(v6.2#6252)