[jira] [Assigned] (SYNCOPE-1074) Realm navigator: show only relevant realms for delegated admin

[fabio martelli (JIRA)]

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

fabio martelli reassigned SYNCOPE-1074:
---

Assignee: fabio martelli

> Realm navigator: show only relevant realms for delegated admin
> --
>
> Key: SYNCOPE-1074
> URL: https://issues.apache.org/jira/browse/SYNCOPE-1074
> Project: Syncope
>  Issue Type: Improvement
>  Components: console
>Reporter: Francesco Chicchiriccò
>Assignee: fabio martelli
> Fix For: 2.0.4, 2.1.0
>
>
> The realm navigator always shows all the available realms, even if the logged 
> admin does not own any relevant entitlement for each of them.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Resolved] (SYNCOPE-1074) Realm navigator: show only relevant realms for delegated admin

[fabio martelli (JIRA)]

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

fabio martelli resolved SYNCOPE-1074.
-
Resolution: Fixed

> Realm navigator: show only relevant realms for delegated admin
> --
>
> Key: SYNCOPE-1074
> URL: https://issues.apache.org/jira/browse/SYNCOPE-1074
> Project: Syncope
>  Issue Type: Improvement
>  Components: console
>Reporter: Francesco Chicchiriccò
>Assignee: fabio martelli
> Fix For: 2.0.4, 2.1.0
>
>
> The realm navigator always shows all the available realms, even if the logged 
> admin does not own any relevant entitlement for each of them.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (SYNCOPE-1074) Realm navigator: show only relevant realms for delegated admin

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on SYNCOPE-1074:
--

Commit cf3eb46dad9dee4c5b04b212098e6dc9b87d208c in syncope's branch 
refs/heads/master from [~fmartelli]
[ https://git-wip-us.apache.org/repos/asf?p=syncope.git;h=cf3eb46 ]

[SYNCOPE-1074] adds for entitlements check to enable realm list items


> Realm navigator: show only relevant realms for delegated admin
> --
>
> Key: SYNCOPE-1074
> URL: https://issues.apache.org/jira/browse/SYNCOPE-1074
> Project: Syncope
>  Issue Type: Improvement
>  Components: console
>Reporter: Francesco Chicchiriccò
> Fix For: 2.0.4, 2.1.0
>
>
> The realm navigator always shows all the available realms, even if the logged 
> admin does not own any relevant entitlement for each of them.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (SYNCOPE-1074) Realm navigator: show only relevant realms for delegated admin

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on SYNCOPE-1074:
--

Commit 5756a270f590dac1ba31a5c17fa12fac15336664 in syncope's branch 
refs/heads/2_0_X from [~fmartelli]
[ https://git-wip-us.apache.org/repos/asf?p=syncope.git;h=5756a27 ]

[SYNCOPE-1074] adds for entitlements check to enable realm list items


> Realm navigator: show only relevant realms for delegated admin
> --
>
> Key: SYNCOPE-1074
> URL: https://issues.apache.org/jira/browse/SYNCOPE-1074
> Project: Syncope
>  Issue Type: Improvement
>  Components: console
>Reporter: Francesco Chicchiriccò
> Fix For: 2.0.4, 2.1.0
>
>
> The realm navigator always shows all the available realms, even if the logged 
> admin does not own any relevant entitlement for each of them.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (SYNCOPE-1077) Extension: Elasticsearch-based search engine

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on SYNCOPE-1077:
--

Commit 2c59f981546f0a66b24f31985d9ae8331401b78a in syncope's branch 
refs/heads/master from [~ilgrosso]
[ https://git-wip-us.apache.org/repos/asf?p=syncope.git;h=2c59f98 ]

[SYNCOPE-1077] Fixing links 2_0_X -> master


> Extension: Elasticsearch-based search engine
> 
>
> Key: SYNCOPE-1077
> URL: https://issues.apache.org/jira/browse/SYNCOPE-1077
> Project: Syncope
>  Issue Type: New Feature
>  Components: core, extensions
>Reporter: Francesco Chicchiriccò
>Assignee: Francesco Chicchiriccò
> Fix For: 2.0.4, 2.1.0
>
>
> As outlined in SYNCOPE-1006, the current search engine is somehow fragile 
> (being based on SQL views) and highly depends on the DBMS used as internal 
> storage - with frequent issues for MySQL / MariaDB.
> [As 
> suggested|https://issues.apache.org/jira/browse/SYNCOPE-1006?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15856313#comment-15856313],
>  an idea could be to provide another, optional search engine implementation 
> which requires an Elasticsearch node.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (SYNCOPE-1077) Extension: Elasticsearch-based search engine

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on SYNCOPE-1077:
--

Commit 8f33e423faa382dc32260b271246fafc8d3f6e2d in syncope's branch 
refs/heads/2_0_X from [~ilgrosso]
[ https://git-wip-us.apache.org/repos/asf?p=syncope.git;h=8f33e42 ]

[SYNCOPE-1077] Docs


> Extension: Elasticsearch-based search engine
> 
>
> Key: SYNCOPE-1077
> URL: https://issues.apache.org/jira/browse/SYNCOPE-1077
> Project: Syncope
>  Issue Type: New Feature
>  Components: core, extensions
>Reporter: Francesco Chicchiriccò
>Assignee: Francesco Chicchiriccò
> Fix For: 2.0.4, 2.1.0
>
>
> As outlined in SYNCOPE-1006, the current search engine is somehow fragile 
> (being based on SQL views) and highly depends on the DBMS used as internal 
> storage - with frequent issues for MySQL / MariaDB.
> [As 
> suggested|https://issues.apache.org/jira/browse/SYNCOPE-1006?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15856313#comment-15856313],
>  an idea could be to provide another, optional search engine implementation 
> which requires an Elasticsearch node.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (SYNCOPE-1077) Extension: Elasticsearch-based search engine

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on SYNCOPE-1077:
--

Commit 091c74b8a6d2f317c165ede0f1219774dd6383fc in syncope's branch 
refs/heads/master from [~ilgrosso]
[ https://git-wip-us.apache.org/repos/asf?p=syncope.git;h=091c74b ]

[SYNCOPE-1077] Docs


> Extension: Elasticsearch-based search engine
> 
>
> Key: SYNCOPE-1077
> URL: https://issues.apache.org/jira/browse/SYNCOPE-1077
> Project: Syncope
>  Issue Type: New Feature
>  Components: core, extensions
>Reporter: Francesco Chicchiriccò
>Assignee: Francesco Chicchiriccò
> Fix For: 2.0.4, 2.1.0
>
>
> As outlined in SYNCOPE-1006, the current search engine is somehow fragile 
> (being based on SQL views) and highly depends on the DBMS used as internal 
> storage - with frequent issues for MySQL / MariaDB.
> [As 
> suggested|https://issues.apache.org/jira/browse/SYNCOPE-1006?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15856313#comment-15856313],
>  an idea could be to provide another, optional search engine implementation 
> which requires an Elasticsearch node.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Resolved] (SYNCOPE-1077) Extension: Elasticsearch-based search engine

[JIRA]

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

Francesco Chicchiriccò resolved SYNCOPE-1077.
-
Resolution: Fixed

> Extension: Elasticsearch-based search engine
> 
>
> Key: SYNCOPE-1077
> URL: https://issues.apache.org/jira/browse/SYNCOPE-1077
> Project: Syncope
>  Issue Type: New Feature
>  Components: core, extensions
>Reporter: Francesco Chicchiriccò
>Assignee: Francesco Chicchiriccò
> Fix For: 2.0.4, 2.1.0
>
>
> As outlined in SYNCOPE-1006, the current search engine is somehow fragile 
> (being based on SQL views) and highly depends on the DBMS used as internal 
> storage - with frequent issues for MySQL / MariaDB.
> [As 
> suggested|https://issues.apache.org/jira/browse/SYNCOPE-1006?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15856313#comment-15856313],
>  an idea could be to provide another, optional search engine implementation 
> which requires an Elasticsearch node.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Re: Want to start contributing in Syncope project

[Yash Jain]

Hi,

I have created confluence account with username yjain525. you can grant me
access there.
I have submitted the ICLA document to the email id : secret...@apache.org.

Regards,
Yash


On Fri, May 5, 2017 at 1:04 PM, Yash Jain  wrote:

> Thanks buddy!
>
> I will create confluence account and start going through Syncope concepts
> and codebase.
>
> Regards,
> Yash
>
> On Fri, May 5, 2017 at 12:13 PM, Francesco Chicchiriccò <
> ilgro...@apache.org> wrote:
>
>> Hi Yash,
>> see my replies below.
>>
>> Regards.
>>
>> On 04/05/2017 20:46, Yash Jain wrote:
>>
>>> Hi,
>>>
>>> Thanks for providing the documents.
>>>
>>> 1) I am able to build the project on my local using following command :
>>> mvn - PskipTests,all
>>> I have attached txt file for the build results.
>>>
>>
>> Cool.
>>
>> 2)  But when I am running command:
>>>mvn clean install
>>> It is failing . Should I try to debug the issue or should I start going
>>> through the code.
>>>
>>
>> Building Syncope with all tests is quite resource-demanding, so there are
>> some synchronization issues in the integration tests which lead to failure
>> when the underlying system takes a bit more than expected to respond.
>> On my laptop, for example, 'mvn  -T 1C -PskipTests,all' takes around 1.30
>> mins while 'mvn -T 1C clean install' something less than 20 mins.
>>
>> We have however several CI instances in place, including Travis CI:
>>
>> https://travis-ci.org/apache/syncope/builds
>>
>> which take additional care about successful builds.
>>
>> I'd say you'd rather start going through the code ;-)
>>
>> 3) I went through the link [1]  and I think I can work on "social
>>> registration for End user UI" module.
>>> Kindly help me on which sections of code, I should start going through
>>> to further work on this module.
>>>
>>
>> Cool, then you're looking at
>>
>> https://issues.apache.org/jira/browse/SYNCOPE-1018
>>
>> Besides what it is already reported in the issue description and
>> comments, you can now - after Syncope 2.0.3 was released - also have a kind
>> of reference implementation in the SAML 2.0 SP extension, e.g.
>>
>> https://github.com/apache/syncope/tree/2_0_X/ext/saml2sp
>>
>> That extension, in fact, allows to SSO to Admin Console and Enduser UI
>> after authenticating to an external SAML 2.0 IdP.
>>
>> The new extension from SYNCOPE-1018, instead, should enable the Enduser
>> UI (and possibly the Admin Console too, why not?) to SSO after
>> authenticating to an external OAuth 2.0 provider (for existing users) or to
>> pre-populate some attribute (for self-registration, in the Enduser UI).
>>
>> Once you've got some confidence around Syncope concepts and codebase, I
>> suggest to start from
>>
>> https://cwiki.apache.org/confluence/display/SYNCOPE/%5BDISCU
>> SS%5D+SAML+2.0+Service+Provider+feature
>>
>> and to create a similar page for OAuth 2.0.
>> Once done that, you might want to start a separate mail thread here on
>> dev@ to discuss.
>>
>> In order to proceed, we need:
>>
>> * you to sign and submit an ICLA - see http://www.apache.org/licenses
>> /#clas
>> * your Confluence account so I can grant you write access to
>> https://cwiki.apache.org/confluence/display/SYNCOPE
>>
>> Glad to have you onboard, anyway!
>>
>> On Thu, May 4, 2017 at 1:12 PM, Yash Jain > yjain...@gmail.com>> wrote:
>>>
>>> Hi,
>>>
>>> Thanks a lot guys for quick response. I will go through the ideas
>>> and start going through the documents.
>>>
>>>
>>> On Thu, May 4, 2017 at 1:01 PM, Francesco Chicchiriccò
>>> > wrote:
>>>
>>> On 04/05/2017 09:11, Yash Jain wrote:
>>>
>>> Hi Guys,
>>>
>>> I am excited to contribute to syncope project as I find it
>>> quite
>>> interesting and challenging opportunity to learn and
>>> contribute.
>>> I have worked on some projects using spring framework, SQL
>>> and some front
>>> end technologies. I am willing to learn new technologies
>>> while contributing
>>> to such a good project.
>>> Kindly guide me on how to start and in which area I can
>>> start contributing.
>>>
>>>
>>> Welcome to Apache Syncope!
>>>
>>> If you are looking for contribution you can check [1], which
>>> are the ideas for GSoC 2017 that did not unfortunately found
>>> valuable proposals.
>>>
>>> You might also be interested in some background information
>>> about contributing in [2] and building [3].
>>>
>>> Regards.
>>>
>>> [1]
>>> https://issues.apache.org/jira/browse/SYNCOPE-1019?jql=proje
>>> ct%20%3D%20SYNCOPE%20AND%20labels%20%3D%20gsoc2017
>>> >> ect%20%3D%20SYNCOPE%20AND%20labels%20%3D%20gsoc2017>
>>> [2] 

[jira] [Commented] (SYNCOPE-1073) Hide realm management if no realm entitlement are owned

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on SYNCOPE-1073:
--

Commit 5820eb52a37abf3a8d6f288c5fb8a3e311d66179 in syncope's branch 
refs/heads/master from [~fmartelli]
[ https://git-wip-us.apache.org/repos/asf?p=syncope.git;h=5820eb5 ]

[SYNCOPE-1073] provides authorization check for realm details


> Hide realm management if no realm entitlement are owned
> ---
>
> Key: SYNCOPE-1073
> URL: https://issues.apache.org/jira/browse/SYNCOPE-1073
> Project: Syncope
>  Issue Type: Improvement
>  Components: console
>Reporter: Francesco Chicchiriccò
>Assignee: fabio martelli
> Fix For: 2.0.4, 2.1.0
>
>
> Even if no {{REALM_CREATE}}, {{REALM_UPDATE}} or {{REALM_DELETE}} 
> entitlements are owned by the logged admin, the management tab is always 
> shown by the Realms page.
> This can be confusing for delegated administration, when the Realms page 
> needs to be accessed for users, groups or any objects administration.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (SYNCOPE-1073) Hide realm management if no realm entitlement are owned

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on SYNCOPE-1073:
--

Commit da72d30c939c9f141b0460b4d6ed9fbcf0e340c9 in syncope's branch 
refs/heads/2_0_X from [~fmartelli]
[ https://git-wip-us.apache.org/repos/asf?p=syncope.git;h=da72d30 ]

[SYNCOPE-1073] provides authorization check for realm details


> Hide realm management if no realm entitlement are owned
> ---
>
> Key: SYNCOPE-1073
> URL: https://issues.apache.org/jira/browse/SYNCOPE-1073
> Project: Syncope
>  Issue Type: Improvement
>  Components: console
>Reporter: Francesco Chicchiriccò
>Assignee: fabio martelli
> Fix For: 2.0.4, 2.1.0
>
>
> Even if no {{REALM_CREATE}}, {{REALM_UPDATE}} or {{REALM_DELETE}} 
> entitlements are owned by the logged admin, the management tab is always 
> shown by the Realms page.
> This can be confusing for delegated administration, when the Realms page 
> needs to be accessed for users, groups or any objects administration.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Assigned] (SYNCOPE-1073) Hide realm management if no realm entitlement are owned

[fabio martelli (JIRA)]

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

fabio martelli reassigned SYNCOPE-1073:
---

Assignee: fabio martelli

> Hide realm management if no realm entitlement are owned
> ---
>
> Key: SYNCOPE-1073
> URL: https://issues.apache.org/jira/browse/SYNCOPE-1073
> Project: Syncope
>  Issue Type: Improvement
>  Components: console
>Reporter: Francesco Chicchiriccò
>Assignee: fabio martelli
> Fix For: 2.0.4, 2.1.0
>
>
> Even if no {{REALM_CREATE}}, {{REALM_UPDATE}} or {{REALM_DELETE}} 
> entitlements are owned by the logged admin, the management tab is always 
> shown by the Realms page.
> This can be confusing for delegated administration, when the Realms page 
> needs to be accessed for users, groups or any objects administration.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Resolved] (SYNCOPE-1076) The console doesn't allow to download the report in various formats

[fabio martelli (JIRA)]

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

fabio martelli resolved SYNCOPE-1076.
-
Resolution: Fixed

> The console doesn't allow to download the report in various formats
> ---
>
> Key: SYNCOPE-1076
> URL: https://issues.apache.org/jira/browse/SYNCOPE-1076
> Project: Syncope
>  Issue Type: Bug
>  Components: console
>Affects Versions: 2.0.3
>Reporter: Marco Di Sabatino Di Diodoro
>Assignee: fabio martelli
> Fix For: 2.0.4, 2.1.0
>
>
> The console doesn't allow to download the report in various formats. The type 
> of report selected remains persistent even on other donwload links.
> In the SNAPSHOT version, missing the link for downloading xml format.
> The download link for xml format is not present.
> A workaround to download the various formats is to reclick on the report tab 
> and download the desired format.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (SYNCOPE-1076) The console doesn't allow to download the report in various formats

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on SYNCOPE-1076:
--

Commit e0e7a0a360b77b0a7c46dcad58ac96257a3bfbb3 in syncope's branch 
refs/heads/2_0_X from [~fmartelli]
[ https://git-wip-us.apache.org/repos/asf?p=syncope.git;h=e0e7a0a ]

[SYNCOPE-1076] reset stream before ask for new dowbload


> The console doesn't allow to download the report in various formats
> ---
>
> Key: SYNCOPE-1076
> URL: https://issues.apache.org/jira/browse/SYNCOPE-1076
> Project: Syncope
>  Issue Type: Bug
>  Components: console
>Affects Versions: 2.0.3
>Reporter: Marco Di Sabatino Di Diodoro
>Assignee: fabio martelli
> Fix For: 2.0.4, 2.1.0
>
>
> The console doesn't allow to download the report in various formats. The type 
> of report selected remains persistent even on other donwload links.
> In the SNAPSHOT version, missing the link for downloading xml format.
> The download link for xml format is not present.
> A workaround to download the various formats is to reclick on the report tab 
> and download the desired format.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (SYNCOPE-1076) The console doesn't allow to download the report in various formats

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on SYNCOPE-1076:
--

Commit 2f65c14fcd681d1e2e798e4563c6eaa07b5def9f in syncope's branch 
refs/heads/master from [~fmartelli]
[ https://git-wip-us.apache.org/repos/asf?p=syncope.git;h=2f65c14 ]

[SYNCOPE-1076] reset stream before ask for new dowbload


> The console doesn't allow to download the report in various formats
> ---
>
> Key: SYNCOPE-1076
> URL: https://issues.apache.org/jira/browse/SYNCOPE-1076
> Project: Syncope
>  Issue Type: Bug
>  Components: console
>Affects Versions: 2.0.3
>Reporter: Marco Di Sabatino Di Diodoro
>Assignee: fabio martelli
> Fix For: 2.0.4, 2.1.0
>
>
> The console doesn't allow to download the report in various formats. The type 
> of report selected remains persistent even on other donwload links.
> In the SNAPSHOT version, missing the link for downloading xml format.
> The download link for xml format is not present.
> A workaround to download the various formats is to reclick on the report tab 
> and download the desired format.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Assigned] (SYNCOPE-1076) The console doesn't allow to download the report in various formats

[fabio martelli (JIRA)]

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

fabio martelli reassigned SYNCOPE-1076:
---

Assignee: fabio martelli

> The console doesn't allow to download the report in various formats
> ---
>
> Key: SYNCOPE-1076
> URL: https://issues.apache.org/jira/browse/SYNCOPE-1076
> Project: Syncope
>  Issue Type: Bug
>  Components: console
>Affects Versions: 2.0.3
>Reporter: Marco Di Sabatino Di Diodoro
>Assignee: fabio martelli
> Fix For: 2.0.4, 2.1.0
>
>
> The console doesn't allow to download the report in various formats. The type 
> of report selected remains persistent even on other donwload links.
> In the SNAPSHOT version, missing the link for downloading xml format.
> The download link for xml format is not present.
> A workaround to download the various formats is to reclick on the report tab 
> and download the desired format.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (SYNCOPE-1075) User lastChangeDate attribute is not displayed correctly

[JIRA]

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

Francesco Chicchiriccò commented on SYNCOPE-1075:
-

Related commit on master branch: 
https://git-wip-us.apache.org/repos/asf?p=syncope.git;h=018fa9771adee2788be0ba3357c31cdc5da17cba

> User lastChangeDate attribute is not displayed correctly
> 
>
> Key: SYNCOPE-1075
> URL: https://issues.apache.org/jira/browse/SYNCOPE-1075
> Project: Syncope
>  Issue Type: Bug
>  Components: console
>Affects Versions: 2.0.3
>Reporter: Marco Di Sabatino Di Diodoro
>Assignee: Marco Di Sabatino Di Diodoro
>Priority: Minor
> Fix For: 2.0.4, 2.1.0
>
>
> On the user's edit modal page the lastChangeDate attribute is not displayed 
> correctly



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Resolved] (SYNCOPE-1075) User lastChangeDate attribute is not displayed correctly

[Marco Di Sabatino Di Diodoro (JIRA)]

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

Marco Di Sabatino Di Diodoro resolved SYNCOPE-1075.
---
Resolution: Fixed

> User lastChangeDate attribute is not displayed correctly
> 
>
> Key: SYNCOPE-1075
> URL: https://issues.apache.org/jira/browse/SYNCOPE-1075
> Project: Syncope
>  Issue Type: Bug
>  Components: console
>Affects Versions: 2.0.3
>Reporter: Marco Di Sabatino Di Diodoro
>Assignee: Marco Di Sabatino Di Diodoro
>Priority: Minor
> Fix For: 2.0.4, 2.1.0
>
>
> On the user's edit modal page the lastChangeDate attribute is not displayed 
> correctly



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (SYNCOPE-1077) Extension: Elasticsearch-based search engine

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on SYNCOPE-1077:
--

Commit 46427608914cb4fa52c39cd4af960cbe3ff20896 in syncope's branch 
refs/heads/2_0_X from [~ilgrosso]
[ https://git-wip-us.apache.org/repos/asf?p=syncope.git;h=4642760 ]

[SYNCOPE-1077] Conditionally build ext/elasticsearch, only when jdk8 is 
available


> Extension: Elasticsearch-based search engine
> 
>
> Key: SYNCOPE-1077
> URL: https://issues.apache.org/jira/browse/SYNCOPE-1077
> Project: Syncope
>  Issue Type: New Feature
>  Components: core, extensions
>Reporter: Francesco Chicchiriccò
>Assignee: Francesco Chicchiriccò
> Fix For: 2.0.4, 2.1.0
>
>
> As outlined in SYNCOPE-1006, the current search engine is somehow fragile 
> (being based on SQL views) and highly depends on the DBMS used as internal 
> storage - with frequent issues for MySQL / MariaDB.
> [As 
> suggested|https://issues.apache.org/jira/browse/SYNCOPE-1006?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15856313#comment-15856313],
>  an idea could be to provide another, optional search engine implementation 
> which requires an Elasticsearch node.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (SYNCOPE-1077) Extension: Elasticsearch-based search engine

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on SYNCOPE-1077:
--

Commit d70c841bf38efb2d37c1aba6ab4b64a1b7946de1 in syncope's branch 
refs/heads/master from [~ilgrosso]
[ https://git-wip-us.apache.org/repos/asf?p=syncope.git;h=d70c841 ]

[SYNCOPE-1077] Adjusting versions


> Extension: Elasticsearch-based search engine
> 
>
> Key: SYNCOPE-1077
> URL: https://issues.apache.org/jira/browse/SYNCOPE-1077
> Project: Syncope
>  Issue Type: New Feature
>  Components: core, extensions
>Reporter: Francesco Chicchiriccò
>Assignee: Francesco Chicchiriccò
> Fix For: 2.0.4, 2.1.0
>
>
> As outlined in SYNCOPE-1006, the current search engine is somehow fragile 
> (being based on SQL views) and highly depends on the DBMS used as internal 
> storage - with frequent issues for MySQL / MariaDB.
> [As 
> suggested|https://issues.apache.org/jira/browse/SYNCOPE-1006?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15856313#comment-15856313],
>  an idea could be to provide another, optional search engine implementation 
> which requires an Elasticsearch node.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (SYNCOPE-1077) Extension: Elasticsearch-based search engine

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on SYNCOPE-1077:
--

Commit 07e31980a076f1276ee2c3667bdcb00143ec2d52 in syncope's branch 
refs/heads/2_0_X from [~ilgrosso]
[ https://git-wip-us.apache.org/repos/asf?p=syncope.git;h=07e3198 ]

[SYNCOPE-1077] Extension provided, not enabled by default in fit/core-reference 
(profile available)


> Extension: Elasticsearch-based search engine
> 
>
> Key: SYNCOPE-1077
> URL: https://issues.apache.org/jira/browse/SYNCOPE-1077
> Project: Syncope
>  Issue Type: New Feature
>  Components: core, extensions
>Reporter: Francesco Chicchiriccò
>Assignee: Francesco Chicchiriccò
> Fix For: 2.0.4, 2.1.0
>
>
> As outlined in SYNCOPE-1006, the current search engine is somehow fragile 
> (being based on SQL views) and highly depends on the DBMS used as internal 
> storage - with frequent issues for MySQL / MariaDB.
> [As 
> suggested|https://issues.apache.org/jira/browse/SYNCOPE-1006?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15856313#comment-15856313],
>  an idea could be to provide another, optional search engine implementation 
> which requires an Elasticsearch node.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (SYNCOPE-1077) Extension: Elasticsearch-based search engine

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on SYNCOPE-1077:
--

Commit 021230445caf8d026a1d09b10ae4722dadb49984 in syncope's branch 
refs/heads/master from [~ilgrosso]
[ https://git-wip-us.apache.org/repos/asf?p=syncope.git;h=0212304 ]

[SYNCOPE-1077] Extension provided, not enabled by default in fit/core-reference 
(profile available)


> Extension: Elasticsearch-based search engine
> 
>
> Key: SYNCOPE-1077
> URL: https://issues.apache.org/jira/browse/SYNCOPE-1077
> Project: Syncope
>  Issue Type: New Feature
>  Components: core, extensions
>Reporter: Francesco Chicchiriccò
>Assignee: Francesco Chicchiriccò
> Fix For: 2.0.4, 2.1.0
>
>
> As outlined in SYNCOPE-1006, the current search engine is somehow fragile 
> (being based on SQL views) and highly depends on the DBMS used as internal 
> storage - with frequent issues for MySQL / MariaDB.
> [As 
> suggested|https://issues.apache.org/jira/browse/SYNCOPE-1006?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15856313#comment-15856313],
>  an idea could be to provide another, optional search engine implementation 
> which requires an Elasticsearch node.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Created] (SYNCOPE-1077) Extension: Elasticsearch-based search engine

[JIRA]

Francesco Chicchiriccò created SYNCOPE-1077:
---

 Summary: Extension: Elasticsearch-based search engine
 Key: SYNCOPE-1077
 URL: https://issues.apache.org/jira/browse/SYNCOPE-1077
 Project: Syncope
  Issue Type: New Feature
  Components: core, extensions
Reporter: Francesco Chicchiriccò
Assignee: Francesco Chicchiriccò
 Fix For: 2.0.4, 2.1.0


As outlined in SYNCOPE-1006, the current search engine is somehow fragile 
(being based on SQL views) and highly depends on the DBMS used as internal 
storage - with frequent issues for MySQL / MariaDB.

[As 
suggested|https://issues.apache.org/jira/browse/SYNCOPE-1006?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15856313#comment-15856313],
 an idea could be to provide another, optional search engine implementation 
which requires an Elasticsearch node.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Created] (SYNCOPE-1076) The console doesn't allow to download the report in various formats

[Marco Di Sabatino Di Diodoro (JIRA)]

Marco Di Sabatino Di Diodoro created SYNCOPE-1076:
-

 Summary: The console doesn't allow to download the report in 
various formats
 Key: SYNCOPE-1076
 URL: https://issues.apache.org/jira/browse/SYNCOPE-1076
 Project: Syncope
  Issue Type: Bug
  Components: console
Affects Versions: 2.0.3
Reporter: Marco Di Sabatino Di Diodoro
 Fix For: 2.0.4, 2.1.0


The console doesn't allow to download the report in various formats. The type 
of report selected remains persistent even on other donwload links.
In the SNAPSHOT version, missing the link for downloading xml format.

The download link for xml format is not present.

A workaround to download the various formats is to reclick on the report tab 
and download the desired format.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)