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/
[
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
[
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
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
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
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
[
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
[
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
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,
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
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
11 matches
Mail list logo