Colm O hEigeartaigh created SYNCOPE-1165:
Summary: Switch the default password cipher algorithm from SHA1 to
SSHA256
Key: SYNCOPE-1165
URL: https://issues.apache.org/jira/browse/SYNCOPE-1165
P
On Fri, Jul 14, 2017 at 1:14 PM, Francesco Chicchiriccò wrote:
> Well, the default jwKey is hard-coded in
>
> https://github.com/apache/syncope/blob/master/core/spring/
> src/main/java/org/apache/syncope/core/spring/security/D
> efaultCredentialChecker.java#L31
>
> no?
>
Sure, but that's only u
Francesco Chicchiriccò created SYNCOPE-1164:
---
Summary: Complete mapping for Realm provisioning
Key: SYNCOPE-1164
URL: https://issues.apache.org/jira/browse/SYNCOPE-1164
Project: Syncope
[
https://issues.apache.org/jira/browse/SYNCOPE-1159?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16087261#comment-16087261
]
ASF subversion and git services commented on SYNCOPE-1159:
--
Com
[
https://issues.apache.org/jira/browse/SYNCOPE-1159?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16087262#comment-16087262
]
ASF subversion and git services commented on SYNCOPE-1159:
--
Com
[
https://issues.apache.org/jira/browse/SYNCOPE-1144?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16087243#comment-16087243
]
ASF subversion and git services commented on SYNCOPE-1144:
--
Com
[
https://issues.apache.org/jira/browse/SYNCOPE-1144?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16087241#comment-16087241
]
ASF subversion and git services commented on SYNCOPE-1144:
--
Com
On 14/07/2017 14:03, Colm O hEigeartaigh wrote:
Well I guess the difference between the two cases is that for SYNCOPE-1119
we need to have some (default) values in security.properties to get Syncope
to start properly (hence logging if the default values are detected).
Whereas for Encryptor, it ha
Well I guess the difference between the two cases is that for SYNCOPE-1119
we need to have some (default) values in security.properties to get Syncope
to start properly (hence logging if the default values are detected).
Whereas for Encryptor, it has the default key hard-coded into the class. It
se
[
https://issues.apache.org/jira/browse/SYNCOPE-1151?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16087212#comment-16087212
]
ASF GitHub Bot commented on SYNCOPE-1151:
-
Github user mat-ale commented on the
Github user mat-ale commented on the issue:
https://github.com/apache/syncope/pull/56
You're welcome @ilgrosso
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes
On 14/07/2017 11:54, Colm O hEigeartaigh wrote:
OK thanks. Well I'd say that "SSHA256" would be best, WDYT?
BTW I'm a bit dubious about "SECRET_KEY = DEFAULT_SECRET_KEY;" in
Encryptor. If SECRET_KEY is null we should probably throw an exception...
We recently took a different approach for defa
[
https://issues.apache.org/jira/browse/SYNCOPE-1151?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16087184#comment-16087184
]
ASF GitHub Bot commented on SYNCOPE-1151:
-
Github user asfgit closed the pull re
[
https://issues.apache.org/jira/browse/SYNCOPE-1151?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16087185#comment-16087185
]
ASF GitHub Bot commented on SYNCOPE-1151:
-
Github user ilgrosso commented on the
Github user asfgit closed the pull request at:
https://github.com/apache/syncope/pull/56
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enab
Github user ilgrosso commented on the issue:
https://github.com/apache/syncope/pull/56
Thanks again @mat-ale
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes s
[
https://issues.apache.org/jira/browse/SYNCOPE-1151?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16087181#comment-16087181
]
ASF subversion and git services commented on SYNCOPE-1151:
--
Com
[
https://issues.apache.org/jira/browse/SYNCOPE-1151?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16087182#comment-16087182
]
ASF subversion and git services commented on SYNCOPE-1151:
--
Com
[
https://issues.apache.org/jira/browse/SYNCOPE-1151?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16087137#comment-16087137
]
ASF GitHub Bot commented on SYNCOPE-1151:
-
GitHub user mat-ale opened a pull req
GitHub user mat-ale opened a pull request:
https://github.com/apache/syncope/pull/56
[SYNCOPE-1151] Realm is correctly loaded after creation - Update
Hi,
this is an update for the PR related to
[[SYNCOPE-1151]](https://github.com/apache/syncope/pull/54).
Regards,
OK thanks. Well I'd say that "SSHA256" would be best, WDYT?
BTW I'm a bit dubious about "SECRET_KEY = DEFAULT_SECRET_KEY;" in
Encryptor. If SECRET_KEY is null we should probably throw an exception...
Colm.
On Fri, Jul 14, 2017 at 10:48 AM, Francesco Chicchiriccò <
ilgro...@apache.org> wrote:
>
On 14/07/2017 11:45, Colm O hEigeartaigh wrote:
How does the salt configuration work for "SSHA256"? Is it stored in
security.properties?
Password values are encrypted by
https://github.com/apache/syncope/blob/master/core/spring/src/main/java/org/apache/syncope/core/spring/security/Encryptor.ja
How does the salt configuration work for "SSHA256"? Is it stored in
security.properties?
Colm.
On Fri, Jul 14, 2017 at 10:41 AM, Francesco Chicchiriccò <
ilgro...@apache.org> wrote:
> On 14/07/2017 11:40, Colm O hEigeartaigh wrote:
>
>> I guess SHA-256 would be a straightforward replacement. May
On 14/07/2017 11:40, Colm O hEigeartaigh wrote:
I guess SHA-256 would be a straightforward replacement. Maybe we should
instead move to a salted hash though?
Well, just set your preference among
https://github.com/apache/syncope/blob/master/common/lib/src/main/java/org/apache/syncope/common/li
I guess SHA-256 would be a straightforward replacement. Maybe we should
instead move to a salted hash though?
Colm.
On Fri, Jul 14, 2017 at 9:52 AM, Francesco Chicchiriccò wrote:
> On 14/07/2017 10:48, Colm O hEigeartaigh wrote:
>
>> Should we change the default password algorithm from SHA1 for
On 14/07/2017 10:48, Colm O hEigeartaigh wrote:
Should we change the default password algorithm from SHA1 for 2.1.0? It's
probably time to migrate from SHA1 IMO.
Makes sense.
The only problem I could see if when pulling hashed password values from
LDAP, where SHA1 is still quite common. Not a
Should we change the default password algorithm from SHA1 for 2.1.0? It's
probably time to migrate from SHA1 IMO.
Colm.
--
Colm O hEigeartaigh
Talend Community Coder
http://coders.talend.com
[
https://issues.apache.org/jira/browse/SYNCOPE-1163?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Francesco Chicchiriccò resolved SYNCOPE-1163.
-
Resolution: Fixed
> External Resource priority is never NULL
> -
[
https://issues.apache.org/jira/browse/SYNCOPE-1163?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16086958#comment-16086958
]
ASF subversion and git services commented on SYNCOPE-1163:
--
Com
[
https://issues.apache.org/jira/browse/SYNCOPE-1163?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16086957#comment-16086957
]
ASF subversion and git services commented on SYNCOPE-1163:
--
Com
[
https://issues.apache.org/jira/browse/SYNCOPE-1163?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Francesco Chicchiriccò updated SYNCOPE-1163:
Description:
Despite setting any External Resource's priority value to NUL
Francesco Chicchiriccò created SYNCOPE-1163:
---
Summary: External Resource priority is never NULL
Key: SYNCOPE-1163
URL: https://issues.apache.org/jira/browse/SYNCOPE-1163
Project: Syncope
32 matches
Mail list logo
