[jira] [Created] (SYNCOPE-1166) No propagation task is created for resources where the password is not propagated

2017-07-17 Thread Marco Di Sabatino Di Diodoro (JIRA)
Marco Di Sabatino Di Diodoro created SYNCOPE-1166: - Summary: No propagation task is created for resources where the password is not propagated Key: SYNCOPE-1166 URL: https://issues.apache.org/jira/

[jira] [Updated] (SYNCOPE-1160) When defining the provisioning rules of a resource disable the first Previous button

2017-07-17 Thread JIRA
[ https://issues.apache.org/jira/browse/SYNCOPE-1160?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Francesco Chicchiriccò updated SYNCOPE-1160: Fix Version/s: (was: 2.0.5) (was: 2.1.0) > When

[jira] [Closed] (SYNCOPE-1160) When defining the provisioning rules of a resource disable the first Previous button

2017-07-17 Thread JIRA
[ https://issues.apache.org/jira/browse/SYNCOPE-1160?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Francesco Chicchiriccò closed SYNCOPE-1160. --- Resolution: Won't Fix Without such first Previous button, it won't be possib

Encryptor + AES + key size

2017-07-17 Thread Colm O hEigeartaigh
Hi all, When AES is used as the cipher algorithm, and if the supplied secret key length is < 16, Encryptor prints the debug message: "actualKey too short, adding some random characters" However the random characters are just 0s. I think instead we should be using some random bytes instead! Optio

Re: Encryptor + AES + key size

2017-07-17 Thread Francesco Chicchiriccò
On 17/07/2017 16:32, Colm O hEigeartaigh wrote: Hi all, When AES is used as the cipher algorithm, and if the supplied secret key length is < 16, Encryptor prints the debug message: "actualKey too short, adding some random characters" However the random characters are just 0s. I think instead w

Re: Encryptor + AES + key size

2017-07-17 Thread Colm O hEigeartaigh
Yes why not. I will take care of it. What do you think about imposing a size constraint on the secret key length as well? Colm. On Mon, Jul 17, 2017 at 3:34 PM, Francesco Chicchiriccò wrote: > On 17/07/2017 16:32, Colm O hEigeartaigh wrote: > >> Hi all, >> >> When AES is used as the cipher algo

[jira] [Commented] (SYNCOPE-1160) When defining the provisioning rules of a resource disable the first Previous button

2017-07-17 Thread Filipe Silva (JIRA)
[ https://issues.apache.org/jira/browse/SYNCOPE-1160?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16089929#comment-16089929 ] Filipe Silva commented on SYNCOPE-1160: --- I think I didn't made myself clear. Afte

[jira] [Commented] (SYNCOPE-1160) When defining the provisioning rules of a resource disable the first Previous button

2017-07-17 Thread JIRA
[ https://issues.apache.org/jira/browse/SYNCOPE-1160?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16089932#comment-16089932 ] Francesco Chicchiriccò commented on SYNCOPE-1160: - When you are just cre

Re: Encryptor + AES + key size

2017-07-17 Thread Francesco Chicchiriccò
On 17/07/2017 16:38, Colm O hEigeartaigh wrote: Yes why not. I will take care of it. What do you think about imposing a size constraint on the secret key length as well? I don't have any strong opinion WRT this, I'll trust your experience, then :-) Regards. On Mon, Jul 17, 2017 at 3:34 PM,

2.0.x test failures

2017-07-17 Thread Colm O hEigeartaigh
Hi all, I'm seeing some test failures on 2.0.x in the FIT Enduser Reference tests: 2) syncope enduser user password reset should reset password for user donizetti Message: Failed: No element found using locator: By(css selector, *[id="passwordreset"]) Stack: NoSuchElementError: No el

Re: 2.0.x test failures

2017-07-17 Thread Francesco Chicchiriccò
On 17/07/2017 22:05, Colm O hEigeartaigh wrote: Hi all, I'm seeing some test failures on 2.0.x in the FIT Enduser Reference tests: 2) syncope enduser user password reset should reset password for user donizetti Message: Failed: No element found using locator: By(css selector, *[id="pas