[jira] [Updated] (SYNCOPE-805) Select destination realm from a drop down list when creating a task

[Colm O hEigeartaigh (JIRA)]

 [ 
https://issues.apache.org/jira/browse/SYNCOPE-805?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Colm O hEigeartaigh updated SYNCOPE-805:

Description: 
When creating a (pull) task, if you have to explicitly specify the realm. 
However, a better idea would be if the user could select the realm from a 
dropdown list. 

Incidentally, when currently creating a pull task, if you fail to specify the 
realm you get an error message: 

org.apache.syncope.common.lib.SyncopeClientException: InvalidPath 
[MalformedPathException: Malformed path: null]

This should be updated to let the user know the realm needs to be specified. 
But this is probably not required if the user has to select the realm from a 
list.

  was:
When creating a pull task, if you fail to specify the realm you get an error 
message: 

org.apache.syncope.common.lib.SyncopeClientException: InvalidPath 
[MalformedPathException: Malformed path: null]

This should be updated to let the user know the realm needs to be specified.

 Issue Type: Improvement  (was: Bug)
Summary: Select destination realm from a drop down list when creating a 
task  (was: Unhelpful error message when a realm is not specified in a pull 
task)

> Select destination realm from a drop down list when creating a task
> ---
>
> Key: SYNCOPE-805
> URL: https://issues.apache.org/jira/browse/SYNCOPE-805
> Project: Syncope
>  Issue Type: Improvement
>  Components: console
>Affects Versions: 2.0.0-M2
>Reporter: Colm O hEigeartaigh
>Priority: Minor
> Fix For: 2.0.0
>
>
> When creating a (pull) task, if you have to explicitly specify the realm. 
> However, a better idea would be if the user could select the realm from a 
> dropdown list. 
> Incidentally, when currently creating a pull task, if you fail to specify the 
> realm you get an error message: 
> org.apache.syncope.common.lib.SyncopeClientException: InvalidPath 
> [MalformedPathException: Malformed path: null]
> This should be updated to let the user know the realm needs to be specified. 
> But this is probably not required if the user has to select the realm from a 
> list.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Re: Some comments on Connectors

[Colm O hEigeartaigh]

On Wed, Mar 23, 2016 at 4:35 PM, Francesco Chicchiriccò  wrote:

>
> a) I filed a bug (SYNCOPE-805) for when the user doesn't specify a
>> destination realm for a pull task. However, I wonder if it would it be
>> possible for the user to select the destination realm from a drop-down
>> list?
>>
>
> Sounds good: can you suggest this as alternative fix for SYNCOPE-805?
>

Done.


>
> b) When running Syncope via a Maven archetype + mvn -Pembedded (using the
>> core main, not test, configuration) I don't see anything relating to
>> "Extensions" in the UI. I see it when I download the standalone
>> distribution though. Perhaps the default configuration for the archetype
>> needs to be updated to reference Camel etc?
>>
>
> The idea is to not enable extensions (nor Camel nor Swagger UI, which are
> the extensions currently available) by default; maybe an idea is to add a
> further "all" profile - similarly to what we do with fit/core-reference so
> that one can run
>
> * mvn -Pembedded to get the environment without extensions
> * mvn -Pembedded,all to get the environment with extensions
>

Yep that'd be great.


>
> WDYT?
>
> c) I noticed here (
>> https://dist.apache.org/repos/dist/dev/syncope/2.0.0-M2/)
>> that half of the artifacts start with "apache-syncope" and the other half
>> with "syncope". Any reason why they are not all starting with
>> "apache-syncope" for consistency?
>>
>
> Essentially, .deb packages have the "apache-syncope" prefix rather than
> "syncope" - as all other artifacts, which take the name off of Maven
> modules, do instead.
>
> We might want to change the .deb packages prefix to "syncope" (and
> generated directories as /etc/apache-syncope, /var/log/apache-syncope etc)
> for consistency; anyway, this is following the practice we have since 1.2.0.
>

Ok thanks for the explanation. TBH I wouldn't bother changing things, it's
just a trivial issue really.

Colm.


>
> Regards.
>
>
> On Wed, Mar 23, 2016 at 3:56 PM, Colm O hEigeartaigh 
>> wrote:
>>
>> Answers inline:
>>>
>>> On Tue, Mar 22, 2016 at 3:49 PM, Francesco Chicchiriccò <
>>> ilgro...@apache.org> wrote:
>>>
>>> On 22/03/2016 15:09, Colm O hEigeartaigh wrote:

 a) In the "Capabilities" tab, the header is "capabilitiesPalette" which
> seems a bit unnecessary IMO. An "all" checkbox would possibly be useful
> here which would select all of the other checkboxes.
>
> Agree: would you mind opening an improvement for this?

>>> https://issues.apache.org/jira/browse/SYNCOPE-802
>>>
>>>
>>> b) In the "Configuration" tab, it's not clear to me what the On/Off
> buttons
> mean?
>

 As for 1.2, such buttons sets the possibility to override the related
 properties in the resources using the given connector.
 I agree it is not clear now: again, could you please take care of filing
 another improvement for this?

>>> https://issues.apache.org/jira/browse/SYNCOPE-803
>>>
>>> c) In previous Syncope versions, one could hover over the textfields IIRC

> and get an explanation as to what the configuration item meant. However
> this is not working, unless I am missing something.
>
> Once more, I agree with you; third required improvement in a row.

 https://issues.apache.org/jira/browse/SYNCOPE-804
>>>
>>> d) Not related to Connectors, but I noticed that all of the table
 listings

> in the UI have both the header and footer containing the column names.
> IMO
> it would be sufficient just to have the header there.
>
> This was set according to the Admin LTE template that we have chosen
 for
 the new admin console: see [1]; however, as you can imagine, we can
 easily
 revert to the single-header version; it's more a matter of taste.

>>> Sure, it's not an important issue anyway.
>>>
>>> Colm.
>>>
>>> WDYT?

 Regards.

 [1] https://almsaeedstudio.com/themes/AdminLTE/pages/tables/data.html

>>>
> --
> Francesco Chicchiriccò
>
> Tirasa - Open Source Excellence
> http://www.tirasa.net/
>
> Involved at The Apache Software Foundation:
> member, Syncope PMC chair, Cocoon PMC, Olingo PMC, CXF committer
> http://home.apache.org/~ilgrosso/
>
>
>


-- 
Colm O hEigeartaigh

Talend Community Coder
http://coders.talend.com

Re: Some comments on Connectors

[Francesco Chicchiriccò]

Hi Colm,
first of all, thanks for spending time for careful examination of 
2.0.0-M2 from a kind of "external" point of view, and for opening issues 
accordingly.


On 23/03/2016 17:06, Colm O hEigeartaigh wrote:

A few other random thoughts:

a) I filed a bug (SYNCOPE-805) for when the user doesn't specify a
destination realm for a pull task. However, I wonder if it would it be
possible for the user to select the destination realm from a drop-down list?


Sounds good: can you suggest this as alternative fix for SYNCOPE-805?


b) When running Syncope via a Maven archetype + mvn -Pembedded (using the
core main, not test, configuration) I don't see anything relating to
"Extensions" in the UI. I see it when I download the standalone
distribution though. Perhaps the default configuration for the archetype
needs to be updated to reference Camel etc?


The idea is to not enable extensions (nor Camel nor Swagger UI, which 
are the extensions currently available) by default; maybe an idea is to 
add a further "all" profile - similarly to what we do with 
fit/core-reference so that one can run


* mvn -Pembedded to get the environment without extensions
* mvn -Pembedded,all to get the environment with extensions

WDYT?


c) I noticed here (https://dist.apache.org/repos/dist/dev/syncope/2.0.0-M2/)
that half of the artifacts start with "apache-syncope" and the other half
with "syncope". Any reason why they are not all starting with
"apache-syncope" for consistency?


Essentially, .deb packages have the "apache-syncope" prefix rather than 
"syncope" - as all other artifacts, which take the name off of Maven 
modules, do instead.


We might want to change the .deb packages prefix to "syncope" (and 
generated directories as /etc/apache-syncope, /var/log/apache-syncope 
etc) for consistency; anyway, this is following the practice we have 
since 1.2.0.



Regards.


On Wed, Mar 23, 2016 at 3:56 PM, Colm O hEigeartaigh 
wrote:


Answers inline:

On Tue, Mar 22, 2016 at 3:49 PM, Francesco Chicchiriccò <
ilgro...@apache.org> wrote:


On 22/03/2016 15:09, Colm O hEigeartaigh wrote:


a) In the "Capabilities" tab, the header is "capabilitiesPalette" which
seems a bit unnecessary IMO. An "all" checkbox would possibly be useful
here which would select all of the other checkboxes.


Agree: would you mind opening an improvement for this?

https://issues.apache.org/jira/browse/SYNCOPE-802



b) In the "Configuration" tab, it's not clear to me what the On/Off buttons
mean?


As for 1.2, such buttons sets the possibility to override the related
properties in the resources using the given connector.
I agree it is not clear now: again, could you please take care of filing
another improvement for this?

https://issues.apache.org/jira/browse/SYNCOPE-803


c) In previous Syncope versions, one could hover over the textfields IIRC

and get an explanation as to what the configuration item meant. However
this is not working, unless I am missing something.


Once more, I agree with you; third required improvement in a row.


https://issues.apache.org/jira/browse/SYNCOPE-804


d) Not related to Connectors, but I noticed that all of the table listings

in the UI have both the header and footer containing the column names.
IMO
it would be sufficient just to have the header there.


This was set according to the Admin LTE template that we have chosen for
the new admin console: see [1]; however, as you can imagine, we can easily
revert to the single-header version; it's more a matter of taste.

Sure, it's not an important issue anyway.

Colm.


WDYT?

Regards.

[1] https://almsaeedstudio.com/themes/AdminLTE/pages/tables/data.html


--
Francesco Chicchiriccò

Tirasa - Open Source Excellence
http://www.tirasa.net/

Involved at The Apache Software Foundation:
member, Syncope PMC chair, Cocoon PMC, Olingo PMC, CXF committer
http://home.apache.org/~ilgrosso/

[jira] [Created] (SYNCOPE-806) Validate "standalone" resource provisioning

[Colm O hEigeartaigh (JIRA)]

Colm O hEigeartaigh created SYNCOPE-806:
---

 Summary: Validate "standalone" resource provisioning
 Key: SYNCOPE-806
 URL: https://issues.apache.org/jira/browse/SYNCOPE-806
 Project: Syncope
  Issue Type: Improvement
  Components: console
Affects Versions: 2.0.0-M2
Reporter: Colm O hEigeartaigh
Priority: Minor
 Fix For: 2.0.0


A lot of the resources configured in the "standalone" distribution appear to be 
missing internal attributes in the provisioning mappings. For example, in 
"resource-ldap" no internal attribute is specified for the mapping to "postal". 
So if you click "Next" on the mapping page you get an error.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (SYNCOPE-801) Provisioning mappings are not saved

[Colm O hEigeartaigh (JIRA)]

[ 
https://issues.apache.org/jira/browse/SYNCOPE-801?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15208668#comment-15208668
 ] 

Colm O hEigeartaigh commented on SYNCOPE-801:
-

That's what I am doing. When I then edit the resource again, the mappings are 
missing.

> Provisioning mappings are not saved
> ---
>
> Key: SYNCOPE-801
> URL: https://issues.apache.org/jira/browse/SYNCOPE-801
> Project: Syncope
>  Issue Type: Bug
>  Components: console
>Affects Versions: 2.0.0-M2
>Reporter: Colm O hEigeartaigh
> Fix For: 2.0.0
>
> Attachments: syncope-missing-mappings.png
>
>
> A fairly major bug here unless I am being stupid again. When I create a new 
> provisioning mapping when creating a resource, it appears to save 
> successfully. However when I edit the resource again, no provisioning 
> mappings appear in the UI.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Re: Some comments on Connectors

[Colm O hEigeartaigh]

A few other random thoughts:

a) I filed a bug (SYNCOPE-805) for when the user doesn't specify a
destination realm for a pull task. However, I wonder if it would it be
possible for the user to select the destination realm from a drop-down list?

b) When running Syncope via a Maven archetype + mvn -Pembedded (using the
core main, not test, configuration) I don't see anything relating to
"Extensions" in the UI. I see it when I download the standalone
distribution though. Perhaps the default configuration for the archetype
needs to be updated to reference Camel etc?

c) I noticed here (https://dist.apache.org/repos/dist/dev/syncope/2.0.0-M2/)
that half of the artifacts start with "apache-syncope" and the other half
with "syncope". Any reason why they are not all starting with
"apache-syncope" for consistency?

Thanks,

Colm.

On Wed, Mar 23, 2016 at 3:56 PM, Colm O hEigeartaigh 
wrote:

> Answers inline:
>
> On Tue, Mar 22, 2016 at 3:49 PM, Francesco Chicchiriccò <
> ilgro...@apache.org> wrote:
>
>> On 22/03/2016 15:09, Colm O hEigeartaigh wrote:
>>
>>>
>>> a) In the "Capabilities" tab, the header is "capabilitiesPalette" which
>>> seems a bit unnecessary IMO. An "all" checkbox would possibly be useful
>>> here which would select all of the other checkboxes.
>>>
>>
>> Agree: would you mind opening an improvement for this?
>>
>
> https://issues.apache.org/jira/browse/SYNCOPE-802
>
>
>>
>> b) In the "Configuration" tab, it's not clear to me what the On/Off
>>> buttons
>>> mean?
>>>
>>
>> As for 1.2, such buttons sets the possibility to override the related
>> properties in the resources using the given connector.
>> I agree it is not clear now: again, could you please take care of filing
>> another improvement for this?
>>
>
> https://issues.apache.org/jira/browse/SYNCOPE-803
>
>
>>
>> c) In previous Syncope versions, one could hover over the textfields IIRC
>>> and get an explanation as to what the configuration item meant. However
>>> this is not working, unless I am missing something.
>>>
>>
>> Once more, I agree with you; third required improvement in a row.
>>
>
> https://issues.apache.org/jira/browse/SYNCOPE-804
>
>
>>
>> d) Not related to Connectors, but I noticed that all of the table listings
>>> in the UI have both the header and footer containing the column names.
>>> IMO
>>> it would be sufficient just to have the header there.
>>>
>>
>> This was set according to the Admin LTE template that we have chosen for
>> the new admin console: see [1]; however, as you can imagine, we can easily
>> revert to the single-header version; it's more a matter of taste.
>>
>
> Sure, it's not an important issue anyway.
>
> Colm.
>
>
>>
>> WDYT?
>>
>> Regards.
>>
>> [1] https://almsaeedstudio.com/themes/AdminLTE/pages/tables/data.html
>>
>> --
>> Francesco Chicchiriccò
>>
>> Tirasa - Open Source Excellence
>> http://www.tirasa.net/
>>
>> Involved at The Apache Software Foundation:
>> member, Syncope PMC chair, Cocoon PMC, Olingo PMC, CXF committer
>> http://home.apache.org/~ilgrosso/
>>
>>
>>
>
>
> --
> Colm O hEigeartaigh
>
> Talend Community Coder
> http://coders.talend.com
>



-- 
Colm O hEigeartaigh

Talend Community Coder
http://coders.talend.com

[jira] [Commented] (SYNCOPE-801) Provisioning mappings are not saved

[JIRA]

[ 
https://issues.apache.org/jira/browse/SYNCOPE-801?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15208657#comment-15208657
 ] 

Francesco Chicchiriccò commented on SYNCOPE-801:


When editing a resource (new or existing), and adding / modifying provision(s), 
you'll need anyway to save the resource at the end to commit the whole 
modification.

> Provisioning mappings are not saved
> ---
>
> Key: SYNCOPE-801
> URL: https://issues.apache.org/jira/browse/SYNCOPE-801
> Project: Syncope
>  Issue Type: Bug
>  Components: console
>Affects Versions: 2.0.0-M2
>Reporter: Colm O hEigeartaigh
> Fix For: 2.0.0
>
> Attachments: syncope-missing-mappings.png
>
>
> A fairly major bug here unless I am being stupid again. When I create a new 
> provisioning mapping when creating a resource, it appears to save 
> successfully. However when I edit the resource again, no provisioning 
> mappings appear in the UI.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (SYNCOPE-805) Unhelpful error message when a realm is not specified in a pull task

[Colm O hEigeartaigh (JIRA)]

Colm O hEigeartaigh created SYNCOPE-805:
---

 Summary: Unhelpful error message when a realm is not specified in 
a pull task
 Key: SYNCOPE-805
 URL: https://issues.apache.org/jira/browse/SYNCOPE-805
 Project: Syncope
  Issue Type: Bug
  Components: console
Affects Versions: 2.0.0-M2
Reporter: Colm O hEigeartaigh
Priority: Minor
 Fix For: 2.0.0


When creating a pull task, if you fail to specify the realm you get an error 
message: 

org.apache.syncope.common.lib.SyncopeClientException: InvalidPath 
[MalformedPathException: Malformed path: null]

This should be updated to let the user know the realm needs to be specified.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Re: Some comments on Connectors

[Colm O hEigeartaigh]

Answers inline:

On Tue, Mar 22, 2016 at 3:49 PM, Francesco Chicchiriccò  wrote:

> On 22/03/2016 15:09, Colm O hEigeartaigh wrote:
>
>>
>> a) In the "Capabilities" tab, the header is "capabilitiesPalette" which
>> seems a bit unnecessary IMO. An "all" checkbox would possibly be useful
>> here which would select all of the other checkboxes.
>>
>
> Agree: would you mind opening an improvement for this?
>

https://issues.apache.org/jira/browse/SYNCOPE-802


>
> b) In the "Configuration" tab, it's not clear to me what the On/Off buttons
>> mean?
>>
>
> As for 1.2, such buttons sets the possibility to override the related
> properties in the resources using the given connector.
> I agree it is not clear now: again, could you please take care of filing
> another improvement for this?
>

https://issues.apache.org/jira/browse/SYNCOPE-803


>
> c) In previous Syncope versions, one could hover over the textfields IIRC
>> and get an explanation as to what the configuration item meant. However
>> this is not working, unless I am missing something.
>>
>
> Once more, I agree with you; third required improvement in a row.
>

https://issues.apache.org/jira/browse/SYNCOPE-804


>
> d) Not related to Connectors, but I noticed that all of the table listings
>> in the UI have both the header and footer containing the column names. IMO
>> it would be sufficient just to have the header there.
>>
>
> This was set according to the Admin LTE template that we have chosen for
> the new admin console: see [1]; however, as you can imagine, we can easily
> revert to the single-header version; it's more a matter of taste.
>

Sure, it's not an important issue anyway.

Colm.


>
> WDYT?
>
> Regards.
>
> [1] https://almsaeedstudio.com/themes/AdminLTE/pages/tables/data.html
>
> --
> Francesco Chicchiriccò
>
> Tirasa - Open Source Excellence
> http://www.tirasa.net/
>
> Involved at The Apache Software Foundation:
> member, Syncope PMC chair, Cocoon PMC, Olingo PMC, CXF committer
> http://home.apache.org/~ilgrosso/
>
>
>


-- 
Colm O hEigeartaigh

Talend Community Coder
http://coders.talend.com

[jira] [Created] (SYNCOPE-804) Support the explanation of the Connector Configuration properties

[Colm O hEigeartaigh (JIRA)]

Colm O hEigeartaigh created SYNCOPE-804:
---

 Summary: Support the explanation of the Connector Configuration 
properties
 Key: SYNCOPE-804
 URL: https://issues.apache.org/jira/browse/SYNCOPE-804
 Project: Syncope
  Issue Type: Improvement
  Components: console
Affects Versions: 2.0.0-M2
Reporter: Colm O hEigeartaigh
Priority: Minor
 Fix For: 2.0.0


In previous Syncope versions, one could hover over the textfields when 
configuring Connector properties, and get an explanation as to what the 
configuration item meant. However this is not working in the latest release.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (SYNCOPE-803) Improve explanation for on/off buttons in the Connector Configuration

[Colm O hEigeartaigh (JIRA)]

Colm O hEigeartaigh created SYNCOPE-803:
---

 Summary: Improve explanation for on/off buttons in the Connector 
Configuration
 Key: SYNCOPE-803
 URL: https://issues.apache.org/jira/browse/SYNCOPE-803
 Project: Syncope
  Issue Type: Improvement
  Components: console
Affects Versions: 2.0.0-M2
Reporter: Colm O hEigeartaigh
Priority: Minor
 Fix For: 2.0.0



This task is to improve the explanation for on/off buttons in the Connector 
Configuration, currently it's not clear at all what they mean, as clicking the 
buttons doesn't do anything noticeable.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (SYNCOPE-802) Improve Connector "Capabilities" layout

[Colm O hEigeartaigh (JIRA)]

Colm O hEigeartaigh created SYNCOPE-802:
---

 Summary: Improve Connector "Capabilities" layout
 Key: SYNCOPE-802
 URL: https://issues.apache.org/jira/browse/SYNCOPE-802
 Project: Syncope
  Issue Type: Improvement
  Components: console
Affects Versions: 2.0.0-M2
Reporter: Colm O hEigeartaigh
 Fix For: 2.0.0


In the "Capabilities" tab of "Connectors", the header is "capabilitiesPalette" 
which could be removed. Also, an "all" checkbox would be useful which would 
select all of the other checkboxes.




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (SYNCOPE-801) Provisioning mappings are not saved

[Colm O hEigeartaigh (JIRA)]

Colm O hEigeartaigh created SYNCOPE-801:
---

 Summary: Provisioning mappings are not saved
 Key: SYNCOPE-801
 URL: https://issues.apache.org/jira/browse/SYNCOPE-801
 Project: Syncope
  Issue Type: Bug
  Components: console
Affects Versions: 2.0.0-M2
Reporter: Colm O hEigeartaigh
 Fix For: 2.0.0
 Attachments: syncope-missing-mappings.png

A fairly major bug here unless I am being stupid again. When I create a new 
provisioning mapping when creating a resource, it appears to save successfully. 
However when I edit the resource again, no provisioning mappings appear in the 
UI.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (SYNCOPE-794) UI is insisting on an external attribute for AccountId

[JIRA]

[ 
https://issues.apache.org/jira/browse/SYNCOPE-794?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15208625#comment-15208625
 ] 

Francesco Chicchiriccò commented on SYNCOPE-794:


You're welcome.

> UI is insisting on an external attribute for AccountId
> --
>
> Key: SYNCOPE-794
> URL: https://issues.apache.org/jira/browse/SYNCOPE-794
> Project: Syncope
>  Issue Type: Bug
>  Components: console
>Affects Versions: 2.0.0-M2
>Reporter: Colm O hEigeartaigh
>Priority: Minor
> Attachments: resource-external-attr.png, xfrancesco.png
>
>
> When trying to add a new user mapping from the internal "Username" to the 
> remote AccountId, it appears that Syncope is insisting that an external 
> attribute must be specified. In previous Syncope versions, once the AccountId 
> was checked, the external attribute textbox was grayed out.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (SYNCOPE-800) Synchronization fails in case of accountId mapped on derived attribute starting with literal

[fabio martelli (JIRA)]

fabio martelli created SYNCOPE-800:
--

 Summary: Synchronization fails in case of accountId mapped on 
derived attribute starting with literal
 Key: SYNCOPE-800
 URL: https://issues.apache.org/jira/browse/SYNCOPE-800
 Project: Syncope
  Issue Type: Bug
  Components: core
Affects Versions: 2.0.0-M1, 1.2.7
Reporter: fabio martelli
 Fix For: 1.2.8, 2.0.0


Synchronization fails in case of synchronized resource maps accountId on a 
derived attribute starting with a literal.

See [1] for details.

The bug is into AbstractSubjectDAOImpl.split() method: empty tokens have to be 
discarded.
Be sure to make SyncUtilities.findExisting() method more robust to JPA 
exceptions due to bad queries.

[1] 
http://syncope-user.1051894.n5.nabble.com/LDAP-synchronisation-and-User-derived-attribute-as-account-ID-with-database-resource-tp5708357p5708390.html



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (SYNCOPE-770) IDE plugin

[JIRA]

[ 
https://issues.apache.org/jira/browse/SYNCOPE-770?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15208418#comment-15208418
 ] 

Francesco Chicchiriccò commented on SYNCOPE-770:


About your specific issue (WRT the linked image), it's because you have not 
provided value(s) for one of mandatory attributes.

About your willing to apply for this proposal, please do it ASAP as student 
application is closing soon!

For any further communication, please subscribe to dev@ as highlighted above.

> IDE plugin
> --
>
> Key: SYNCOPE-770
> URL: https://issues.apache.org/jira/browse/SYNCOPE-770
> Project: Syncope
>  Issue Type: New Feature
>Reporter: Francesco Chicchiriccò
>  Labels: eclipse, gsoc2016, netbeans
>
> Develop plugin(s) for one or more popular open source IDEs (as Netbeans or 
> Eclipse) with purpose of easing the extension of runtime configuration of 
> Apache Syncope deployments.
> SYNCOPE-760 and SYNCOPE-761 introduced the possibility to dynamically reload 
> mail templates (used by notifications) and report stylesheets; such objects 
> are now exposed as REST entities.
> The idea is to enable IDEs with some kind of resource explorer providing 
> access to such dynamic items, allowing to create, edit and remove them from 
> within IDE, by connecting to a running Apache Syncope deployment.
> This item is being discussed at 
> https://cwiki.apache.org/confluence/display/SYNCOPE/GSOC+2016



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Closed] (SYNCOPE-794) UI is insisting on an external attribute for AccountId

[JIRA]

 [ 
https://issues.apache.org/jira/browse/SYNCOPE-794?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Francesco Chicchiriccò closed SYNCOPE-794.
--

> UI is insisting on an external attribute for AccountId
> --
>
> Key: SYNCOPE-794
> URL: https://issues.apache.org/jira/browse/SYNCOPE-794
> Project: Syncope
>  Issue Type: Bug
>  Components: console
>Affects Versions: 2.0.0-M2
>Reporter: Colm O hEigeartaigh
>Priority: Minor
> Attachments: resource-external-attr.png, xfrancesco.png
>
>
> When trying to add a new user mapping from the internal "Username" to the 
> remote AccountId, it appears that Syncope is insisting that an external 
> attribute must be specified. In previous Syncope versions, once the AccountId 
> was checked, the external attribute textbox was grayed out.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Resolved] (SYNCOPE-794) UI is insisting on an external attribute for AccountId

[JIRA]

 [ 
https://issues.apache.org/jira/browse/SYNCOPE-794?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Francesco Chicchiriccò resolved SYNCOPE-794.

   Resolution: Not A Problem
Fix Version/s: (was: 2.0.0)

> UI is insisting on an external attribute for AccountId
> --
>
> Key: SYNCOPE-794
> URL: https://issues.apache.org/jira/browse/SYNCOPE-794
> Project: Syncope
>  Issue Type: Bug
>  Components: console
>Affects Versions: 2.0.0-M2
>Reporter: Colm O hEigeartaigh
>Priority: Minor
> Attachments: resource-external-attr.png, xfrancesco.png
>
>
> When trying to add a new user mapping from the internal "Username" to the 
> remote AccountId, it appears that Syncope is insisting that an external 
> attribute must be specified. In previous Syncope versions, once the AccountId 
> was checked, the external attribute textbox was grayed out.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (SYNCOPE-794) UI is insisting on an external attribute for AccountId

[JIRA]

 [ 
https://issues.apache.org/jira/browse/SYNCOPE-794?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Francesco Chicchiriccò updated SYNCOPE-794:
---
Attachment: xfrancesco.png

[~coheigea] as you can see from the attached screenshot (taken from Syncope 
1.2.8-SNAPSHOT) there is no change compared to 1.2, as explained above.

> UI is insisting on an external attribute for AccountId
> --
>
> Key: SYNCOPE-794
> URL: https://issues.apache.org/jira/browse/SYNCOPE-794
> Project: Syncope
>  Issue Type: Bug
>  Components: console
>Affects Versions: 2.0.0-M2
>Reporter: Colm O hEigeartaigh
>Priority: Minor
> Fix For: 2.0.0
>
> Attachments: resource-external-attr.png, xfrancesco.png
>
>
> When trying to add a new user mapping from the internal "Username" to the 
> remote AccountId, it appears that Syncope is insisting that an external 
> attribute must be specified. In previous Syncope versions, once the AccountId 
> was checked, the external attribute textbox was grayed out.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)