[jira] [Assigned] (SYNCOPE-506) Connector configuration tab in connector modal page does not accept new values
[ https://issues.apache.org/jira/browse/SYNCOPE-506?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marco Di Sabatino Di Diodoro reassigned SYNCOPE-506: Assignee: Marco Di Sabatino Di Diodoro Connector configuration tab in connector modal page does not accept new values -- Key: SYNCOPE-506 URL: https://issues.apache.org/jira/browse/SYNCOPE-506 Project: Syncope Issue Type: Bug Components: console Affects Versions: 1.2.0 Reporter: Andrea Patricelli Assignee: Marco Di Sabatino Di Diodoro Fix For: 1.2.0 To reproduce the problem: 1) launch Syncope in embedded mode. 2) log into console and open resources page, then click on connector tab and edit a connector (ApacheDS is a good example). 3) Edit, for example listening, port for connector ApacheDS, edit other fields and save. 4) Open connector just updated and you will notice that values haven't changed and modifications haven't been submitted. Notes: some values are updated during submit, other values (as port number) not. More problematic fields are numeric ones (port number, Change Log Block Size), which are never updated. -- This message was sent by Atlassian JIRA (v6.2#6252)
Re: ApacheCon CFP closes June 25
On 11/06/2014 14:02, Francesco Chicchiriccò wrote: Dear Syncoper, As you may be aware, ApacheCon will be held this year in Budapest, on November 17-23. (See http://apachecon.eu for more info.) The Call For Papers for that conference is still open, but will be closing soon. We need you talk proposals, to represent Syncope at ApacheCon. We need all kinds of talks - deep technical talks, hands-on tutorials, introductions for beginners, or case studies about the awesome stuff you're doing with Syncope. Please consider submitting a proposal, at http://events.linuxfoundation.org/events/apachecon-europe/program/cfp I've just submitted mine: anyone else? -- Francesco Chicchiriccò Tirasa - Open Source Excellence http://www.tirasa.net/ Involved at The Apache Software Foundation: member, Syncope PMC chair, Cocoon PMC, Olingo PMC http://people.apache.org/~ilgrosso/
[jira] [Commented] (SYNCOPE-506) Connector configuration tab in connector modal page does not accept new values
[ https://issues.apache.org/jira/browse/SYNCOPE-506?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14030428#comment-14030428 ] ASF subversion and git services commented on SYNCOPE-506: - Commit 1602351 from [~mdisabatino] in branch 'syncope/trunk' [ https://svn.apache.org/r1602351 ] [SYNCOPE-506] Connector configuration tab in connector modal page does not accept new values -- Key: SYNCOPE-506 URL: https://issues.apache.org/jira/browse/SYNCOPE-506 Project: Syncope Issue Type: Bug Components: console Affects Versions: 1.2.0 Reporter: Andrea Patricelli Assignee: Marco Di Sabatino Di Diodoro Fix For: 1.2.0 To reproduce the problem: 1) launch Syncope in embedded mode. 2) log into console and open resources page, then click on connector tab and edit a connector (ApacheDS is a good example). 3) Edit, for example listening, port for connector ApacheDS, edit other fields and save. 4) Open connector just updated and you will notice that values haven't changed and modifications haven't been submitted. Notes: some values are updated during submit, other values (as port number) not. More problematic fields are numeric ones (port number, Change Log Block Size), which are never updated. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (SYNCOPE-502) Allow list of PropagationActions for Resource, SyncActions for SyncTask and PushActions for PushTask
[
https://issues.apache.org/jira/browse/SYNCOPE-502?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14030645#comment-14030645
]
ASF subversion and git services commented on SYNCOPE-502:
-
Commit 1602430 from [~ilgrosso] in branch 'syncope/trunk'
[ https://svn.apache.org/r1602430 ]
[SYNCOPE-502] Implementation provided for both core and console
Allow list of PropagationActions for Resource, SyncActions for SyncTask and
PushActions for PushTask
Key: SYNCOPE-502
URL: https://issues.apache.org/jira/browse/SYNCOPE-502
Project: Syncope
Issue Type: Improvement
Reporter: Francesco Chicchiriccò
Assignee: Francesco Chicchiriccò
Fix For: 1.2.0
Currently {{Resource}} can define a single
[PropagationActions|https://cwiki.apache.org/confluence/display/SYNCOPE/PropagationActionsClass]
class, {{SyncTask}} can define a single
[SyncActions|https://cwiki.apache.org/confluence/display/SYNCOPE/SyncActionsClass]
and {{PushTask}} can define a single
[PushActions|https://cwiki.apache.org/confluence/display/SYNCOPE/PushActionsClass]
class.
This is somewhat limiting: a list of actions class, to be invoked in the
specified order, looks more powerful.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Resolved] (SYNCOPE-502) Allow list of PropagationActions for Resource, SyncActions for SyncTask and PushActions for PushTask
[
https://issues.apache.org/jira/browse/SYNCOPE-502?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Francesco Chicchiriccò resolved SYNCOPE-502.
Resolution: Fixed
Allow list of PropagationActions for Resource, SyncActions for SyncTask and
PushActions for PushTask
Key: SYNCOPE-502
URL: https://issues.apache.org/jira/browse/SYNCOPE-502
Project: Syncope
Issue Type: Improvement
Reporter: Francesco Chicchiriccò
Assignee: Francesco Chicchiriccò
Fix For: 1.2.0
Currently {{Resource}} can define a single
[PropagationActions|https://cwiki.apache.org/confluence/display/SYNCOPE/PropagationActionsClass]
class, {{SyncTask}} can define a single
[SyncActions|https://cwiki.apache.org/confluence/display/SYNCOPE/SyncActionsClass]
and {{PushTask}} can define a single
[PushActions|https://cwiki.apache.org/confluence/display/SYNCOPE/PushActionsClass]
class.
This is somewhat limiting: a list of actions class, to be invoked in the
specified order, looks more powerful.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Resolved] (SYNCOPE-313) Support synchronizing non-cleartext passwords from external resources
[
https://issues.apache.org/jira/browse/SYNCOPE-313?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Colm O hEigeartaigh resolved SYNCOPE-313.
-
Resolution: Fixed
Tested both LDAP + DB SyncActions properly.
Colm.
Support synchronizing non-cleartext passwords from external resources
-
Key: SYNCOPE-313
URL: https://issues.apache.org/jira/browse/SYNCOPE-313
Project: Syncope
Issue Type: Improvement
Reporter: Colm O hEigeartaigh
Assignee: Colm O hEigeartaigh
Fix For: 1.2.0
Currently we can synchronize cleartext passwords from external resources.
However, we can't handle non-cleartext passwords, as they get treated as if
they are plaintext passwords when imported into Syncope, and hence hashed
again according to user.cipherAlgorithm().
This task is to treat an imported password as hashed according to a give
cipher algorithm configured on the connector (for example via 'Password
Cipher Algorithm' for the DB Connector).
This is specific to each individual connector, as for example for the DB
Connector, it might just be a hashed value stored in a table, whereas for
LDAP it'll be of the form CIPHER}VALUE etc.
Note that we we cannot refer to any specific connector bundle from inside the
SyncopeSyncResultHandler, hence we should find the cleanest place to
encapsulate the following logic:
if (password.isClearText()) {
// do as currently done
} else {
if (connector.isLDAP()) {
// extract cipher and value
} else if (connector.isDBTable()) {
// treat value as ciphered with the cipher defined in connector
configuration
} else {
...
}
}
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Assigned] (SYNCOPE-505) Support propagating non-cleartext passwords to external resources
[
https://issues.apache.org/jira/browse/SYNCOPE-505?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Colm O hEigeartaigh reassigned SYNCOPE-505:
---
Assignee: Colm O hEigeartaigh
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)
[jira] [Commented] (SYNCOPE-505) Support propagating non-cleartext passwords to external resources
[
https://issues.apache.org/jira/browse/SYNCOPE-505?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14030710#comment-14030710
]
Colm O hEigeartaigh commented on SYNCOPE-505:
-
Hi Francesco,
I'm just wondering what the use-case is here: Is it when we have users
synchronized into Syncope from one resource with non-cleartext passwords, that
we then want to propagate to another resource? When we create users in Syncope,
then we can just propagate out the password hashed according to the connector
property, right?
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)
UI regression
Hi all, The Create new task button has been removed on Syncope trunk from the Propagation Tasks + Notification Tasks tabs. It's there for Synchronization and Scheduled Tasks. Colm. -- Colm O hEigeartaigh Talend Community Coder http://coders.talend.com
Default Sync/Push/Propagation Actions
Hi all, A rather minor point, but WDYT about making the default Sync/Push/Propagation Actions abstract? I don't see any reason why you should be able to instantiate the classes directly, seeing as they don't actually do anything. In the UI I think it may mislead a user into thinking they have to select the default, when this is not necessary. Colm. -- Colm O hEigeartaigh Talend Community Coder http://coders.talend.com
Re: UI regression
On 13/06/2014 17:18, Colm O hEigeartaigh wrote: Hi all, The Create new task button has been removed on Syncope trunk from the Propagation Tasks + Notification Tasks tabs. It's there for Synchronization and Scheduled Tasks. Actualy... it has never been there :-) Propagation and Notification tasks are created internally by the PropagationManager and NotificationManager respectively. You can compare the trunk UI with 1.1.X running at http://syncopedemo.tirasa.net Regards. -- Francesco Chicchiriccò Tirasa - Open Source Excellence http://www.tirasa.net/ Involved at The Apache Software Foundation: member, Syncope PMC chair, Cocoon PMC, Olingo PMC http://people.apache.org/~ilgrosso/
Re: Default Sync/Push/Propagation Actions
On 13/06/2014 17:20, Colm O hEigeartaigh wrote: Hi all, A rather minor point, but WDYT about making the default Sync/Push/Propagation Actions abstract? I don't see any reason why you should be able to instantiate the classes directly, seeing as they don't actually do anything. In the UI I think it may mislead a user into thinking they have to select the default, when this is not necessary. +1 this sounds reasonable. Default*Actions are somehow needed in 1.1.X but can be made abstract for sure in 1.2.X - especially after SYNCOPE-502 Regards. -- Francesco Chicchiriccò Tirasa - Open Source Excellence http://www.tirasa.net/ Involved at The Apache Software Foundation: member, Syncope PMC chair, Cocoon PMC, Olingo PMC http://people.apache.org/~ilgrosso/
Re: UI regression
Ah, I had a feeling I was missing something alright :-) Colm. On Fri, Jun 13, 2014 at 4:20 PM, Francesco Chicchiriccò ilgro...@apache.org wrote: On 13/06/2014 17:18, Colm O hEigeartaigh wrote: Hi all, The Create new task button has been removed on Syncope trunk from the Propagation Tasks + Notification Tasks tabs. It's there for Synchronization and Scheduled Tasks. Actualy... it has never been there :-) Propagation and Notification tasks are created internally by the PropagationManager and NotificationManager respectively. You can compare the trunk UI with 1.1.X running at http://syncopedemo.tirasa.net Regards. -- Francesco Chicchiriccò Tirasa - Open Source Excellence http://www.tirasa.net/ Involved at The Apache Software Foundation: member, Syncope PMC chair, Cocoon PMC, Olingo PMC http://people.apache.org/~ilgrosso/ -- Colm O hEigeartaigh Talend Community Coder http://coders.talend.com
[jira] [Commented] (SYNCOPE-505) Support propagating non-cleartext passwords to external resources
[
https://issues.apache.org/jira/browse/SYNCOPE-505?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14030741#comment-14030741
]
Francesco Chicchiriccò commented on SYNCOPE-505:
The use case you mention above is one of use cases this issue should cover, but
not the only one.
Syncope requires an input password when subscribing an user to a new resource,
unless {{AES}} is used or that resource does not define a password mapping
entry.
With this issue, password could be actually propagated to a resource - even
from internal storage - when plugging-in the {{*PasswordPropagationActions}}:
for this reason I think it is important to take care not to overwrite any
password already prepared for propagation by the {{PropagationManager}}, in the
{{*PasswordPropagationActions}} code.
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)
