Passed: apache/syncope#647 (trunk - 514f3cb)
Build Update for apache/syncope - Build: #647 Status: Passed Duration: 16 minutes and 45 seconds Commit: 514f3cb (trunk) Author: Francesco Chicchiriccò Message: [SYNCOPE-143] Now the build should succeed git-svn-id: https://svn.apache.org/repos/asf/syncope/trunk@1607247 13f79535-47bb-0310-9956-ffa450edef68 View the changeset: https://github.com/apache/syncope/compare/f69bd2da9cdc...514f3cb10fe2 View the full build log and details: https://travis-ci.org/apache/syncope/builds/28933305 -- You can configure recipients for build notifications in your .travis.yml file. See http://docs.travis-ci.com/user/notifications
[jira] [Commented] (SYNCOPE-164) Passthrough authentication
[
https://issues.apache.org/jira/browse/SYNCOPE-164?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14049660#comment-14049660
]
Francesco Chicchiriccò commented on SYNCOPE-164:
By taking a look at [the actual
code|https://github.com/Tirasa/ConnIdLDAPBundle/blob/master/src/main/java/org/connid/bundles/ldap/LdapConnection.java#L143]
invoked by LDAP connector's {{authenticate()}} it seems that the underlying
password encoding just does not matter: as expected a JNDI bind is performed
with clear password extracted from passed {{GuardedString}} instance.
This means that connector's digest algorithm does not play any role here.
The cipher algorithm defined on Syncope only matters when performing local
authentication; as you can read from
{{SyncopeAuthenticationProvider#authenticate}}, authentication on external
resources is only attempted when local authentication fails.
> Passthrough authentication
> --
>
> Key: SYNCOPE-164
> URL: https://issues.apache.org/jira/browse/SYNCOPE-164
> Project: Syncope
> Issue Type: New Feature
>Reporter: Francesco Chicchiriccò
>Assignee: Francesco Chicchiriccò
> Fix For: 1.2.0
>
>
> Provide the possibility to authenticate users on external resources.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Commented] (SYNCOPE-143) GUI Installer
[
https://issues.apache.org/jira/browse/SYNCOPE-143?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14049655#comment-14049655
]
Francesco Chicchiriccò commented on SYNCOPE-143:
I've taken a quick look and it seems fine; I'd say that some enhancements are
needed:
# use [newer HttpClient|http://hc.apache.org/httpcomponents-client-ga/] 4.3
instead on [legacy|http://hc.apache.org/httpclient-legacy/index.html] 3.1
# use newer Jackson - the same defined in parent {{pom.xml}}
# remove dependencies of MySQL and PostgreSQL JDBC drivers: they are highly
problematic from a license POV and don't look strictly needed: why don't apply
the same policy as per the Oracle JDBC driver?
> GUI Installer
> -
>
> Key: SYNCOPE-143
> URL: https://issues.apache.org/jira/browse/SYNCOPE-143
> Project: Syncope
> Issue Type: New Feature
> Components: installer
>Reporter: Francesco Chicchiriccò
>Assignee: Massimiliano Perrone
> Fix For: 1.2.0
>
>
> Provide a web interface that will help users configuring an initial setup.
> Relevant discussion: http://markmail.org/message/j36i55z7weiqt2sw
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Updated] (SYNCOPE-143) GUI Installer
[ https://issues.apache.org/jira/browse/SYNCOPE-143?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Francesco Chicchiriccò updated SYNCOPE-143: --- Assignee: Massimiliano Perrone (was: Francesco Chicchiriccò) > GUI Installer > - > > Key: SYNCOPE-143 > URL: https://issues.apache.org/jira/browse/SYNCOPE-143 > Project: Syncope > Issue Type: New Feature > Components: installer >Reporter: Francesco Chicchiriccò >Assignee: Massimiliano Perrone > Fix For: 1.2.0 > > > Provide a web interface that will help users configuring an initial setup. > Relevant discussion: http://markmail.org/message/j36i55z7weiqt2sw -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (SYNCOPE-143) GUI Installer
[ https://issues.apache.org/jira/browse/SYNCOPE-143?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14049653#comment-14049653 ] ASF subversion and git services commented on SYNCOPE-143: - Commit 1607247 from [~ilgrosso] in branch 'syncope/trunk' [ https://svn.apache.org/r1607247 ] [SYNCOPE-143] Now the build should succeed > GUI Installer > - > > Key: SYNCOPE-143 > URL: https://issues.apache.org/jira/browse/SYNCOPE-143 > Project: Syncope > Issue Type: New Feature > Components: installer >Reporter: Francesco Chicchiriccò >Assignee: Massimiliano Perrone > Fix For: 1.2.0 > > > Provide a web interface that will help users configuring an initial setup. > Relevant discussion: http://markmail.org/message/j36i55z7weiqt2sw -- This message was sent by Atlassian JIRA (v6.2#6252)
Errored: apache/syncope#646 (trunk - f69bd2d)
Build Update for apache/syncope - Build: #646 Status: Errored Duration: 9 minutes and 51 seconds Commit: f69bd2d (trunk) Author: Massimiliano Perrone Message: mvn clean verify works fine #SYNCOPE-143 git-svn-id: https://svn.apache.org/repos/asf/syncope/trunk@1607109 13f79535-47bb-0310-9956-ffa450edef68 View the changeset: https://github.com/apache/syncope/compare/269735e0c24c...f69bd2da9cdc View the full build log and details: https://travis-ci.org/apache/syncope/builds/28879940 -- You can configure recipients for build notifications in your .travis.yml file. See http://docs.travis-ci.com/user/notifications
Errored: apache/syncope#645 (trunk - 269735e)
Build Update for apache/syncope - Build: #645 Status: Errored Duration: 10 minutes and 2 seconds Commit: 269735e (trunk) Author: Massimiliano Perrone Message: License #SYNCOPE-143 git-svn-id: https://svn.apache.org/repos/asf/syncope/trunk@1607098 13f79535-47bb-0310-9956-ffa450edef68 View the changeset: https://github.com/apache/syncope/compare/b0426668f01f...269735e0c24c View the full build log and details: https://travis-ci.org/apache/syncope/builds/28875947 -- You can configure recipients for build notifications in your .travis.yml file. See http://docs.travis-ci.com/user/notifications
Syncope-trunk - Build # 639 - Still Failing
The Apache Jenkins build system has built Syncope-trunk (build #639) Status: Still Failing Check console output at https://builds.apache.org/job/Syncope-trunk/639/ to view the results.
[jira] [Commented] (SYNCOPE-143) GUI Installer
[ https://issues.apache.org/jira/browse/SYNCOPE-143?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14048955#comment-14048955 ] ASF subversion and git services commented on SYNCOPE-143: - Commit 1607109 from [~massi] in branch 'syncope/trunk' [ https://svn.apache.org/r1607109 ] mvn clean verify works fine #SYNCOPE-143 > GUI Installer > - > > Key: SYNCOPE-143 > URL: https://issues.apache.org/jira/browse/SYNCOPE-143 > Project: Syncope > Issue Type: New Feature > Components: installer >Reporter: Francesco Chicchiriccò >Assignee: Massimiliano Perrone > Fix For: 1.2.0 > > > Provide a web interface that will help users configuring an initial setup. > Relevant discussion: http://markmail.org/message/j36i55z7weiqt2sw -- This message was sent by Atlassian JIRA (v6.2#6252)
Syncope-trunk - Build # 638 - Failure
The Apache Jenkins build system has built Syncope-trunk (build #638) Status: Failure Check console output at https://builds.apache.org/job/Syncope-trunk/638/ to view the results.
[jira] [Updated] (SYNCOPE-143) GUI Installer
[ https://issues.apache.org/jira/browse/SYNCOPE-143?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Massimiliano Perrone updated SYNCOPE-143: - Component/s: installer > GUI Installer > - > > Key: SYNCOPE-143 > URL: https://issues.apache.org/jira/browse/SYNCOPE-143 > Project: Syncope > Issue Type: New Feature > Components: installer >Reporter: Francesco Chicchiriccò >Assignee: Massimiliano Perrone > Fix For: 1.2.0 > > > Provide a web interface that will help users configuring an initial setup. > Relevant discussion: http://markmail.org/message/j36i55z7weiqt2sw -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (SYNCOPE-143) GUI Installer
[ https://issues.apache.org/jira/browse/SYNCOPE-143?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14048912#comment-14048912 ] ASF subversion and git services commented on SYNCOPE-143: - Commit 1607098 from [~massi] in branch 'syncope/trunk' [ https://svn.apache.org/r1607098 ] License #SYNCOPE-143 > GUI Installer > - > > Key: SYNCOPE-143 > URL: https://issues.apache.org/jira/browse/SYNCOPE-143 > Project: Syncope > Issue Type: New Feature >Reporter: Francesco Chicchiriccò >Assignee: Massimiliano Perrone > Fix For: 1.2.0 > > > Provide a web interface that will help users configuring an initial setup. > Relevant discussion: http://markmail.org/message/j36i55z7weiqt2sw -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (SYNCOPE-164) Passthrough authentication
[ https://issues.apache.org/jira/browse/SYNCOPE-164?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14048911#comment-14048911 ] Colm O hEigeartaigh commented on SYNCOPE-164: - Hi Francesco, I just experimented a bit with this feature, by syncing in some users from LDAP and not providing a password mapping. I can log on via the REST API fine when the user has either a plaintext, SHA or SSHA password in LDAP. However authentication doesn't seem to work when the user has a SHA-256 password. Is the global user cipher algorithm, or the password digest algorithm of the Connector in play here? Thanks, Colm. > Passthrough authentication > -- > > Key: SYNCOPE-164 > URL: https://issues.apache.org/jira/browse/SYNCOPE-164 > Project: Syncope > Issue Type: New Feature >Reporter: Francesco Chicchiriccò >Assignee: Francesco Chicchiriccò > Fix For: 1.2.0 > > > Provide the possibility to authenticate users on external resources. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (SYNCOPE-143) GUI Installer
[ https://issues.apache.org/jira/browse/SYNCOPE-143?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14048903#comment-14048903 ] ASF subversion and git services commented on SYNCOPE-143: - Commit 1607092 from [~massi] in branch 'syncope/trunk' [ https://svn.apache.org/r1607092 ] beta version of installer #SYNCOPE-143 > GUI Installer > - > > Key: SYNCOPE-143 > URL: https://issues.apache.org/jira/browse/SYNCOPE-143 > Project: Syncope > Issue Type: New Feature >Reporter: Francesco Chicchiriccò >Assignee: Massimiliano Perrone > Fix For: 1.2.0 > > > Provide a web interface that will help users configuring an initial setup. > Relevant discussion: http://markmail.org/message/j36i55z7weiqt2sw -- This message was sent by Atlassian JIRA (v6.2#6252)
Passed: apache/syncope#643 (trunk - 82e1c6c)
Build Update for apache/syncope - Build: #643 Status: Passed Duration: 19 minutes and 8 seconds Commit: 82e1c6c (trunk) Author: Francesco Chicchiriccò Message: [SYNCOPE_519] Merge from 1_1_X git-svn-id: https://svn.apache.org/repos/asf/syncope/trunk@1607059 13f79535-47bb-0310-9956-ffa450edef68 View the changeset: https://github.com/apache/syncope/compare/36e8f49dac9d...82e1c6c19fc4 View the full build log and details: https://travis-ci.org/apache/syncope/builds/28863980 -- You can configure recipients for build notifications in your .travis.yml file. See http://docs.travis-ci.com/user/notifications
[jira] [Commented] (SYNCOPE-392) Full reconciliation from syncope to resource
[ https://issues.apache.org/jira/browse/SYNCOPE-392?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14048870#comment-14048870 ] ASF subversion and git services commented on SYNCOPE-392: - Commit 1607071 from [~fmartelli] in branch 'syncope/trunk' [ https://svn.apache.org/r1607071 ] [SYNCOPE-392, SYNCOPE-471] integration test improvement > Full reconciliation from syncope to resource > > > Key: SYNCOPE-392 > URL: https://issues.apache.org/jira/browse/SYNCOPE-392 > Project: Syncope > Issue Type: Improvement > Components: console, core >Affects Versions: 1.1.4, 1.2.0 >Reporter: fabio martelli >Assignee: fabio martelli >Priority: Minor > Fix For: 1.2.0 > > > Implement a full reconciliation from syncope towards a specific resource. > Unmatching (user found on syncope but not on the resource): > * ignore; > * unlink the resource (keep user on syncope and remove resource link) > * create (create user on resource - if create capability is given) > * delete (remove user on syncope) > Matching (users found on syncope and on the resource): > * ignore > * update > * unlink (perform deprovisioning - if delete capability is given) > * delete (delete on syncope and perform deprovisioning - if delete capability > is given) -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (SYNCOPE-471) Provide matching/unmatchig rule management for push tasks
[ https://issues.apache.org/jira/browse/SYNCOPE-471?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14048871#comment-14048871 ] ASF subversion and git services commented on SYNCOPE-471: - Commit 1607071 from [~fmartelli] in branch 'syncope/trunk' [ https://svn.apache.org/r1607071 ] [SYNCOPE-392, SYNCOPE-471] integration test improvement > Provide matching/unmatchig rule management for push tasks > - > > Key: SYNCOPE-471 > URL: https://issues.apache.org/jira/browse/SYNCOPE-471 > Project: Syncope > Issue Type: Sub-task > Components: console, core >Affects Versions: 1.2.0 >Reporter: fabio martelli >Assignee: fabio martelli > Fix For: 1.2.0 > > > Provide matching/unmatching rule management: > Unmatching (user found on syncope but not on the resource and viceversa): > * IGNORE (Do not perform any action); > * UNLINK (Just unlink resource without performing any (de-)provisioning > operation; in case of sync task UNLINK and IGNORE will coincide); > * ASSIGN (Link the resource and create entity); > * PROVISION (Create entity without linking the resource). > Matching (users found on syncope and on the resource): > * IGNORE (Do not perform any action); > * UPDATE (Update matching entity); > * DEPROVISION (Delete resource entity); > * UNASSIGN (Unlink resource and delete resource entity) ; > * UNLINK (Just unlink resource without performing any (de-)provisioning > operation); > * LINK (Just link resource without performing any (de-)provisioning > operation). -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Comment Edited] (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:comment-tabpanel&focusedCommentId=14048799#comment-14048799
]
Francesco Chicchiriccò edited comment on SYNCOPE-313 at 7/1/14 12:15 PM:
-
Take a look at {{TaskTestITCase}} - there is plenty of {{SyncTask}} executions.
was (Author: ilgrosso):
Take a look at {{TaskTestITCase}} - there is plenty of {{SyncTask}} execution.
> 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] [Commented] (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:comment-tabpanel&focusedCommentId=14048799#comment-14048799
]
Francesco Chicchiriccò commented on SYNCOPE-313:
Take a look at {{TaskTestITCase}} - there is plenty of {{SyncTask}} execution.
> 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] [Commented] (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:comment-tabpanel&focusedCommentId=14048797#comment-14048797
]
Colm O hEigeartaigh commented on SYNCOPE-313:
-
Integration tests merged for SYNCOPE-505. Is there any example of a SyncTask
executing successfully in the integration test-code? The idea I had was to
extend the tests in SYNCOPE-505, by changing the local password, and then
sync'ing from the resource again + checking the password was changed. When I
add a SyncTask via something like this, it doesn't seem to have fired (in
time?) and the user is not updated:
SyncTaskTO syncTask = new SyncTaskTO();
syncTask.setName("DB Sync Task");
syncTask.setDescription("DB Sync Task description");
syncTask.setPerformCreate(true);
syncTask.setPerformUpdate(true);
syncTask.setFullReconciliation(true);
syncTask.setResource(RESOURCE_NAME_TESTDB);
syncTask.setStartDate(new Date());
syncTask.getActionsClassNames().add(DBPasswordSyncActions.class.getName());
Response taskResponse = taskService.create(syncTask);
String taskId = taskResponse.getHeaderString(RESTHeaders.RESOURCE_ID);
TaskExecTO taskExec = taskService.execute(Long.valueOf(taskId), false);
Any ideas?
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] [Commented] (SYNCOPE-519) Report default values for connector properties
[ https://issues.apache.org/jira/browse/SYNCOPE-519?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14048796#comment-14048796 ] Francesco Chicchiriccò commented on SYNCOPE-519: Commit 1607059 from Francesco Chicchiriccò in branch 'syncope/trunk' [ https://svn.apache.org/r1607059 ] SYNCOPE-519 Merge from 1_1_X > Report default values for connector properties > -- > > Key: SYNCOPE-519 > URL: https://issues.apache.org/jira/browse/SYNCOPE-519 > Project: Syncope > Issue Type: Improvement > Components: common, console, core >Reporter: Francesco Chicchiriccò >Assignee: Francesco Chicchiriccò > Fix For: 1.1.8, 1.2.0 > > > Currently default values for connector properties are not returned by REST > methods nor shown in the admin console. > Such information, however, is available from the ConnId framework and needs > only to be picked. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Resolved] (SYNCOPE-519) Report default values for connector properties
[ https://issues.apache.org/jira/browse/SYNCOPE-519?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Francesco Chicchiriccò resolved SYNCOPE-519. Resolution: Fixed > Report default values for connector properties > -- > > Key: SYNCOPE-519 > URL: https://issues.apache.org/jira/browse/SYNCOPE-519 > Project: Syncope > Issue Type: Improvement > Components: common, console, core >Reporter: Francesco Chicchiriccò >Assignee: Francesco Chicchiriccò > Fix For: 1.1.8, 1.2.0 > > > Currently default values for connector properties are not returned by REST > methods nor shown in the admin console. > Such information, however, is available from the ConnId framework and needs > only to be picked. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (SYNCOPE-519) Report default values for connector properties
[ https://issues.apache.org/jira/browse/SYNCOPE-519?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14048773#comment-14048773 ] ASF subversion and git services commented on SYNCOPE-519: - Commit 1607045 from [~ilgrosso] in branch 'syncope/branches/1_1_X' [ https://svn.apache.org/r1607045 ] [SYNCOPE-519] Fixing JAX-RS problems > Report default values for connector properties > -- > > Key: SYNCOPE-519 > URL: https://issues.apache.org/jira/browse/SYNCOPE-519 > Project: Syncope > Issue Type: Improvement > Components: common, console, core >Reporter: Francesco Chicchiriccò >Assignee: Francesco Chicchiriccò > Fix For: 1.1.8, 1.2.0 > > > Currently default values for connector properties are not returned by REST > methods nor shown in the admin console. > Such information, however, is available from the ConnId framework and needs > only to be picked. -- This message was sent by Atlassian JIRA (v6.2#6252)
