Re: [PROPOSAL] Joining the OpenJDK Quality Outreach initiative

2019-12-16 Thread Massimiliano Perrone

+1


Massi

Il 16/12/19 13:09, Francesco Chicchiriccò ha scritto:

Hi all,
we have the chance to join the OpenJDK Quality Outreach initiative [1].

They try to encourage popular open source projects to test their releases on 
latest OpenJDK Early Access builds (i.e. JDK 14 -ea, atm), by providing them 
with regular information describing new builds, their features, and making sure 
that their bug reports and feedback land in the right hands. So in that sense, 
being able to expand the set of projects testing against the latest JDK Early 
Access builds across many domains
can help detect issues that would otherwise be only detected once a release is 
shipped.

As you can see from [1], there are several ASF projects listed there, so I 
believe there is nothing preventing us to do so.

Since our master branch builds are based on OpenJDK 11, I think the only 
requirement left would be to set up a CI job  against OpenJDK 14-EA, which is 
definitely something we can afford.

WDYT?
Regards.

[1] https://wiki.openjdk.java.net/display/quality/Quality+Outreach


--
Massimiliano Perrone
Tel +39 393 9121310
Tirasa S.r.l.
http://www.tirasa.net
"L'apprendere molte cose non insegna l'intelligenza"
(Eraclito)



Re: [VOTE] Apache Syncope 2.0.11

2018-11-03 Thread Massimiliano Perrone

+1


BR

Massi

Il 02/11/18 16:04, Francesco Chicchiriccò ha scritto:
I've created a 2.0.11 release, with the following artifacts up for a 
vote:


GIT source tag (d8085b6a013754f589ada294db49129f464e07ef):
https://gitbox.apache.org/repos/asf?p=syncope.git;a=tag;h=d8085b6a013754f589ada294db49129f464e07ef 



List of changes:
https://gitbox.apache.org/repos/asf?p=syncope.git;a=blob;f=CHANGES;h=a018252663f769ad5f8f781e8ddfa2ec02f16a79;hb=d8085b6a013754f589ada294db49129f464e07ef 



Staging artifacts:
https://dist.apache.org/repos/dist/dev/syncope/2.0.11/

Maven staging repo:
https://repository.apache.org/content/repositories/orgapachesyncope-1055/

Staging site (yes, same as for 2.1.2, not a typo):
http://syncope.apache.org/2.1.2/index.html

PGP release keys (signed using 273DF287):
http://www.apache.org/dist/syncope/KEYS

Vote will be open for 72 hours.

[ ] +1 approve
[ ] +0 no opinion
[ ] -1 disapprove (and reason why)

Here's my +1
Regards.


--
Massimiliano Perrone
Tel +39 393 9121310
Tirasa S.r.l.
http://www.tirasa.net
"L'apprendere molte cose non insegna l'intelligenza"
(Eraclito)



Re: [VOTE] Apache Syncope 2.1.2

2018-11-03 Thread Massimiliano Perrone

+1


Massi

Il 02/11/18 16:04, Francesco Chicchiriccò ha scritto:

I've created a 2.1.2 release, with the following artifacts up for a vote:

GIT source tag (7ea54c302ea4847f0e4e9d2255305c864ee68b1c):
https://gitbox.apache.org/repos/asf?p=syncope.git;a=tag;h=7ea54c302ea4847f0e4e9d2255305c864ee68b1c 



List of changes:
https://gitbox.apache.org/repos/asf?p=syncope.git;a=blob;f=CHANGES;h=fd9ec50e83ea96c021c60092adcbf2019c006422;hb=7ea54c302ea4847f0e4e9d2255305c864ee68b1c 



Staging artifacts:
https://dist.apache.org/repos/dist/dev/syncope/2.1.2/

Maven staging repo:
https://repository.apache.org/content/repositories/orgapachesyncope-1054/

Staging site:
http://syncope.apache.org/2.1.2/index.html

PGP release keys (signed using 273DF287):
http://www.apache.org/dist/syncope/KEYS

Vote will be open for 72 hours.

[ ] +1 approve
[ ] +0 no opinion
[ ] -1 disapprove (and reason why)

Here's my +1
Regards.


--
Massimiliano Perrone
Tel +39 393 9121310
Tirasa S.r.l.
http://www.tirasa.net
"L'apprendere molte cose non insegna l'intelligenza"
(Eraclito)



Re: [DISCUSS] - gitbox migration / take 2

2018-10-26 Thread Massimiliano Perrone

+1

thanks

Il 25/10/18 13:57, Francesco Chicchiriccò ha scritto:

Hi all,
we briefly discussed this item about one year ago [1], when we did not 
found enough reasons to jump on that.


Now that things seem to work quite well for several other projects 
[2], and that we have seen few PRs coming, I am reconsidering this 
possibility.


WDYT?
Regards.

[1] 
https://lists.apache.org/thread.html/d28709231a99719a3bf26d37b857f05709b02ed89c1de9cbeeddd973@%3Cdev.syncope.apache.org%3E

[2] https://gitbox.apache.org/repos/asf


--
Massimiliano Perrone
Tel +39 393 9121310
Tirasa S.r.l.
http://www.tirasa.net
"L'apprendere molte cose non insegna l'intelligenza"
(Eraclito)



Re: [DISCUSS] Manage millions of identities

2018-10-19 Thread Massimiliano Perrone




Il 16/10/2018 10:54, Francesco Chicchiriccò ha scritto:

Hi all,
I think it's time to discuss about how we want to get prepared for 
scenarios where the number of identities (mostly users, for the vast 
majority) to manage is considerably high - from 1 million to above; 
the typical case being CIAM (Customer IAM).


In the IdM deliveries I've been involved so far, scaling Apache 
Syncope up to hundreds of thousands of identities is not trivial, but 
doable: naturally, most of optimization work shall be done at DBMS 
level, as that is obviously the component which is stressed more.


I think we can agree about the fact that, in such scenarios, the most 
critical data are the ones bound to the actual identities (hence no 
connectors, resources, tasks, reports or any other configuration): 
consider that with 1 million users and 10 attributes for each user, we 
have the following table sizing to deal with:


* SyncopeUser: 1M rows
* UPlainAttr: 10M rows
* UPlainAttrValue: 10M rows

Moreover, the search views [1] are all on the same size order 
(although one can enable the Elasticsearch extension in such cases, to 
improve performances).


I think this is what we need to change in order to get better results.
So far, I have been able to think of a couple of possibilities:

1. Leverage the JSON column support provided by PostgreSQL [2], MySQL 
[3], SQL Server [4] and Oracle DB [5] to extend the current 
OpenJPA-based persistence layer


Pros:
 * reduce the sizing problems by removing the need of UPlainAttr and 
UPlainAttrValue tables, search views and joins
 * limited implementation effort, as  most of the current JPA layer 
can be retained
 * keep enjoying the benefits of referential integrity and other 
constraints enforced by DBMS (including UNIQUE)


Cons:
 * each DBMS provides JSON support in its own fashion: implementation 
wouldn't be trivial (while we can make it incremental, and add support 
for one DBMS at a time)
 * scaling capabilities and performance might be overrated - even 
though there seems to be very nice references, at least for PostgreSQL 
[6][7]


2. Implement a new persistence layer based on a different technology - 
I have done some experiments with Apache Cassandra [8] and the 
Datastax Java Driver [9]


Pros:
 * built native for scalability and high availability
 * proven and widespread adoption
 * Object Mapper [10] allows to semi-transparently convert between 
query results and domain, somehow similar as JPA's EntityManager


Cons:
 * relations are obviously not available, only custom types [11]: the 
persistence model shall be redesigned to cope with such situation
 * constraints are not available - more specifically UNIQUE, which 
will require additional code handling
 * implementation effort: all the persistence layer shall be redone, 
not only identity-related entities as User, UPlainAttr, 
UPlainAttrValue...


Besides the two above, there are of course other options in the NoSQL 
world (Neo4j, MongoDB, ...), but I am afraid they all present similar 
challenges as Cassandra.


WDYT?


Hi,
IMHO I think the better choice is the last one.

More difficult but definitive.

BR
Massi


Regards.

[1] 
https://github.com/apache/syncope/blob/master/core/persistence-jpa/src/main/resources/views.xml#L50-L94

[2] https://www.postgresql.org/docs/10/static/functions-json.html
[3] https://dev.mysql.com/doc/refman/8.0/en/json.html
[4] 
https://docs.microsoft.com/en-us/sql/relational-databases/json/json-data-sql-server?view=sql-server-2017

[5] https://docs.oracle.com/database/121/ADXDB/json.htm#ADXDB6246
[6] 
https://www.postgresql.eu/events/fosdem2018/sessions/session/1691/slides/63/High-Performance%20JSON_%20PostgreSQL%20Vs.%20MongoDB.pdf
[7] 
http://coussej.github.io/2016/01/14/Replacing-EAV-with-JSONB-in-PostgreSQL/

[8] http://cassandra.apache.org/
[9] https://github.com/datastax/java-driver
[10] 
https://docs.datastax.com/en/developer/java-driver/3.5/manual/object_mapper/
[11] 
http://cassandra.apache.org/doc/latest/cql/types.html?highlight=user%20defined%20types#user-defined-types




--
Massimiliano Perrone
Tel +39 393 9121310
Tirasa S.r.l.
http://www.tirasa.net
"L'apprendere molte cose non insegna l'intelligenza"
(Eraclito)



Re: [VOTE] Apache Syncope 2.1.1

2018-08-20 Thread Massimiliano Perrone

+1

br

massi


Il 20/08/2018 09:34, Fabio Martelli ha scritto:

Il 17/08/2018 11:15, Francesco Chicchiriccò ha scritto:
I've created a 2.1.1 release, with the following artifacts up for a 
vote:


GIT source tag (a9022c6c2cb8ccba306e0aa4a65f7f60c40ed5d9):
https://git-wip-us.apache.org/repos/asf?p=syncope.git;a=tag;h=a9022c6c2cb8ccba306e0aa4a65f7f60c40ed5d9 



List of changes:
https://git-wip-us.apache.org/repos/asf?p=syncope.git;a=blob;f=CHANGES;h=80c7c2180ca84f0e7aa04b4cae4c69c3711aace4;hb=a9022c6c2cb8ccba306e0aa4a65f7f60c40ed5d9 



Staging artifacts:
https://dist.apache.org/repos/dist/dev/syncope/2.1.1/

Maven staging repo:
https://repository.apache.org/content/repositories/orgapachesyncope-1052/ 



Staging site:
http://syncope.apache.org/2.1.1/index.html

PGP release keys (signed using 273DF287):
http://www.apache.org/dist/syncope/KEYS

Vote will be open for 72 hours.

[ ] +1 approve
[ ] +0 no opinion
[ ] -1 disapprove (and reason why)

Here's my +1
Regards.


+1

Regards



--
Massimiliano Perrone
Tel +39 393 9121310
Tirasa S.r.l.
http://www.tirasa.net
"L'apprendere molte cose non insegna l'intelligenza"
(Eraclito)



Re: [VOTE] Apache Syncope 2.0.10

2018-08-20 Thread Massimiliano Perrone

+1

br

massi


Il 20/08/2018 09:09, Fabio Martelli ha scritto:

Il 17/08/2018 11:15, Francesco Chicchiriccò ha scritto:
I've created a 2.0.10 release, with the following artifacts up for a 
vote:


GIT source tag (7081e00f2501c3fed3f124d5ccd601e494e94557):
https://git-wip-us.apache.org/repos/asf?p=syncope.git;a=tag;h=7081e00f2501c3fed3f124d5ccd601e494e94557 



List of changes:
https://git-wip-us.apache.org/repos/asf?p=syncope.git;a=blob;f=CHANGES;h=70fa4ae05bbef053f83d4d1132153f3bc77e0edf;hb=7081e00f2501c3fed3f124d5ccd601e494e94557 



Staging artifacts:
https://dist.apache.org/repos/dist/dev/syncope/2.0.10/

Maven staging repo:
https://repository.apache.org/content/repositories/orgapachesyncope-1053/ 



Staging site (yes, same as for 2.1.1, not a typo):
http://syncope.apache.org/2.1.1/index.html

PGP release keys (signed using 273DF287):
http://www.apache.org/dist/syncope/KEYS

Vote will be open for 72 hours.

[ ] +1 approve
[ ] +0 no opinion
[ ] -1 disapprove (and reason why)

Here's my +1
Regards.


+1

Regards



--
Massimiliano Perrone
Tel +39 393 9121310
Tirasa S.r.l.
http://www.tirasa.net
"L'apprendere molte cose non insegna l'intelligenza"
(Eraclito)



[jira] [Commented] (SYNCOPE-1349) Please add OWASP Dependency Check to the build (pom.xml)

2018-08-06 Thread Massimiliano Perrone (JIRA)


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

Massimiliano Perrone commented on SYNCOPE-1349:
---

Hi [~ABakerIII],
I don't know which kind of Open Source projects have you analyzed in the past 
with your tool and, sincerely, I can have good dreams also without this 
information.

Coming to your comments... you are talking about lucky, precisely *exceedily 
lucky.* A question for you. Do you think that the dependencies choice for an 
Open Source (or not) project is a lottery? Especially for a security middleware 
as usually Syncope is used?

Something like:
"I need a dependency but, which one? Ah, this one seems to be nice hopefully 
all go well! (finger crossed, image the emoticon ;))."

Second thing from your words: *99.999% of projects are no so lucky.* Another 
time lucky... Oh well... anyway, 99.99% are you sure?
So only Syncope is vulnerability free? Or there is at least one project without 
security issue? We are the only *lucky* guys in the open source world?

I don't know if [~ilgrosso] will choice to use your tool, he is the boss. 
Personally I'm not agree because of your bad presentation.



Anyway, after your comments today I'm feeling lucky; so it's the right day to 
buy a scratch card and, of course, choise the right library!

Have a good day Albert and good luck :)
 

> Please add OWASP Dependency Check to the build (pom.xml)
> 
>
> Key: SYNCOPE-1349
> URL: https://issues.apache.org/jira/browse/SYNCOPE-1349
> Project: Syncope
>  Issue Type: New Feature
>Affects Versions: 2.0.10, 2.1.1, 3.0.0
> Environment: All development, build, test, environments.
>Reporter: Albert Baker
>Priority: Major
>  Labels: build, easy-fix, security
> Attachments: dependency-check-report.html
>
>   Original Estimate: 1h
>  Remaining Estimate: 1h
>
>  Please add OWASP Dependency Check to the build (pom.xml).  OWASP DC makes an 
> outbound REST call to MITRE Common Vulnerabilities & Exposures (CVE) to 
> perform a lookup for each dependant .jar to list any/all known 
> vulnerabilities for each jar.  This step is needed because a manual MITRE CVE 
> lookup/check on the main component does not include checking for 
> vulnerabilities in components or in dependant libraries.
> OWASP Dependency check : 
> https://www.owasp.org/index.php/OWASP_Dependency_Check has plug-ins for most 
> Java build/make types (ant, maven, ivy, gradle).   
> Also, add the appropriate command to the nightly build to generate a report 
> of all known vulnerabilities in any/all third party libraries/dependencies 
> that get pulled in. example : mvn -Powasp -Dtest=false -DfailIfNoTests=false 
> clean aggregate
> Generating this report nightly/weekly will help inform the project's 
> development team if any dependant libraries have a reported known 
> vulnerailities.  Project teams that keep up with removing vulnerabilities on 
> a weekly basis will help protect businesses that rely on these open source 
> componets.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Commented] (SYNCOPE-1349) Please add OWASP Dependency Check to the build (pom.xml)

2018-08-06 Thread Massimiliano Perrone (JIRA)


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

Massimiliano Perrone commented on SYNCOPE-1349:
---

Ciao Francecsco,
I don't know if OWASP is pointless or not because I don't see the report.

But looking for his username and "owasp" on Google, I saw that he had 
open the same issue on several Apache project [1], [2] and [3].
I think (and hope) he is "only" a spammer...

BR,

Massi

[1] 
http://mail-archives.apache.org/mod_mbox/mahout-dev/201807.mbox/%3cjira.13175453.1532912821000.114447.1532912880...@atlassian.jira%3E

[2] https://www.mail-archive.com/issues@spark.apache.org/msg197234.html

[3] https://jira.apache.org/jira/browse/CXF-7809



-- 
Massimiliano Perrone
Tel +39 393 9121310
Tirasa S.r.l.
http://www.tirasa.net
"L'apprendere molte cose non insegna l'intelligenza"
(Eraclito)


> Please add OWASP Dependency Check to the build (pom.xml)
> 
>
> Key: SYNCOPE-1349
> URL: https://issues.apache.org/jira/browse/SYNCOPE-1349
> Project: Syncope
>  Issue Type: New Feature
>Affects Versions: 2.0.10, 2.1.1, 3.0.0
> Environment: All development, build, test, environments.
>Reporter: Albert Baker
>Priority: Major
>  Labels: build, easy-fix, security
> Attachments: dependency-check-report.html
>
>   Original Estimate: 1h
>  Remaining Estimate: 1h
>
>  Please add OWASP Dependency Check to the build (pom.xml).  OWASP DC makes an 
> outbound REST call to MITRE Common Vulnerabilities & Exposures (CVE) to 
> perform a lookup for each dependant .jar to list any/all known 
> vulnerabilities for each jar.  This step is needed because a manual MITRE CVE 
> lookup/check on the main component does not include checking for 
> vulnerabilities in components or in dependant libraries.
> OWASP Dependency check : 
> https://www.owasp.org/index.php/OWASP_Dependency_Check has plug-ins for most 
> Java build/make types (ant, maven, ivy, gradle).   
> Also, add the appropriate command to the nightly build to generate a report 
> of all known vulnerabilities in any/all third party libraries/dependencies 
> that get pulled in. example : mvn -Powasp -Dtest=false -DfailIfNoTests=false 
> clean aggregate
> Generating this report nightly/weekly will help inform the project's 
> development team if any dependant libraries have a reported known 
> vulnerailities.  Project teams that keep up with removing vulnerabilities on 
> a weekly basis will help protect businesses that rely on these open source 
> componets.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


Re: [VOTE] Apache Syncope 2.1.0

2018-07-09 Thread Massimiliano Perrone

+1

massi


Il 05/07/2018 18:02, Francesco Chicchiriccò ha scritto:

I've created a 2.1.0 release, with the following artifacts up for a vote:

GIT source tag (1c898982ab328617cae8dc1259e89045bf73fbb3):
https://git-wip-us.apache.org/repos/asf?p=syncope.git;a=tag;h=1c898982ab328617cae8dc1259e89045bf73fbb3 



List of changes:
https://git-wip-us.apache.org/repos/asf?p=syncope.git;a=blob;f=CHANGES;h=7babeeaef0ecc2f7a4da042fde9e387a035ceced;hb=e888eef9cf23d33f43ed799ced61d0c1f2d64f02 



Staging artifacts:
https://dist.apache.org/repos/dist/dev/syncope/2.1.0/

Maven staging repo:
https://repository.apache.org/content/repositories/orgapachesyncope-1051/

Staging site:
http://syncope.apache.org/2.0.9/index.html

PGP release keys (signed using 273DF287):
http://www.apache.org/dist/syncope/KEYS

Vote will be open for 72 hours.

[ ] +1 approve
[ ] +0 no opinion
[ ] -1 disapprove (and reason why)

Here's my +1
Regards.



--
Massimiliano Perrone
Tel +39 393 9121310
Tirasa S.r.l.
http://www.tirasa.net
"L'apprendere molte cose non insegna l'intelligenza"
(Eraclito)



Re: [VOTE] Apache Syncope 2.0.9 - take 2

2018-06-29 Thread Massimiliano Perrone

+1

massi


Il 28/06/2018 10:36, Francesco Chicchiriccò ha scritto:

I've created a 2.0.9 release, with the following artifacts up for a vote:

GIT source tag (57db51d9e9def6548be4393ee715877baf17463e):
https://git-wip-us.apache.org/repos/asf?p=syncope.git;a=commit;h=57db51d9e9def6548be4393ee715877baf17463e 



List of changes:
https://git-wip-us.apache.org/repos/asf?p=syncope.git;a=blob;f=CHANGES;h=69cf4eb6cdfb9d4c4855bc80a81e0824fbc8ee3e;hb=57db51d9e9def6548be4393ee715877baf17463e 



Staging artifacts:
https://dist.apache.org/repos/dist/dev/syncope/2.0.9/

Maven staging repo:
https://repository.apache.org/content/repositories/orgapachesyncope-1050/

Staging site:
http://syncope.apache.org/2.0.9/index.html

PGP release keys (signed using 273DF287):
http://www.apache.org/dist/syncope/KEYS

Vote will be open for 72 hours.

[ ] +1 approve
[ ] +0 no opinion
[ ] -1 disapprove (and reason why)

Here's my +1
Regards.


--
Massimiliano Perrone
Tel +39 393 9121310
Tirasa S.r.l.
http://www.tirasa.net
"L'apprendere molte cose non insegna l'intelligenza"
(Eraclito)



Re: [VOTE] Apache Syncope 2.0.8

2018-03-14 Thread Massimiliano Perrone

+1

Massi


Il 13/03/2018 17:50, Francesco Chicchiriccò ha scritto:

I've created a 2.0.8 release, with the following artifacts up for a vote:

GIT source tag (eafe58237a6d8a4c6c5f3fd306385913a1c6a7fc):
https://git-wip-us.apache.org/repos/asf?p=syncope.git;a=commit;h=eafe58237a6d8a4c6c5f3fd306385913a1c6a7fc 



List of changes:
https://git-wip-us.apache.org/repos/asf?p=syncope.git;a=blob;f=CHANGES;h=02eb7683c74cda671da7211ac05655db33018914;hb=eafe58237a6d8a4c6c5f3fd306385913a1c6a7fc 



Staging artifacts:
https://dist.apache.org/repos/dist/dev/syncope/2.0.8/

Maven staging repo:
https://repository.apache.org/content/repositories/orgapachesyncope-1048/

Staging site:
http://syncope.apache.org/2.0.8/index.html

PGP release keys (signed using 273DF287):
http://www.apache.org/dist/syncope/KEYS

Vote will be open for 72 hours.

[ ] +1 approve
[ ] +0 no opinion
[ ] -1 disapprove (and reason why)

Here's my +1
Regards.



--
Massimiliano Perrone
Tel +39 393 9121310
Tirasa S.r.l.
http://www.tirasa.net
"L'apprendere molte cose non insegna l'intelligenza"
(Eraclito)



Re: [VOTE] Apache Syncope 1.2.11

2018-03-14 Thread Massimiliano Perrone

+1

Massi


Il 13/03/2018 17:47, Francesco Chicchiriccò ha scritto:
I've created a 1.2.11 release, with the following artifacts up for a 
vote:


GIT source tag (d3336eef43c5747cdfd0cc3dde470638fbf2c6c3):
https://git-wip-us.apache.org/repos/asf?p=syncope.git;a=commit;h=d3336eef43c5747cdfd0cc3dde470638fbf2c6c3 



List of changes:
https://git-wip-us.apache.org/repos/asf?p=syncope.git;a=blob;f=CHANGES;h=76e85fbe7446aa801905a39440797790f3199c48;hb=d3336eef43c5747cdfd0cc3dde470638fbf2c6c3 



Staging artifacts:
https://dist.apache.org/repos/dist/dev/syncope/1.2.11/

Maven staging repo:
https://repository.apache.org/content/repositories/orgapachesyncope-1047/

Staging site:
http://syncope.apache.org/2.0.8/index.html

PGP release keys (signed using 273DF287):
http://www.apache.org/dist/syncope/KEYS

Vote will be open for 72 hours.

[ ] +1 approve
[ ] +0 no opinion
[ ] -1 disapprove (and reason why)

Here's my +1
Regards.



--
Massimiliano Perrone
Tel +39 393 9121310
Tirasa S.r.l.
http://www.tirasa.net
"L'apprendere molte cose non insegna l'intelligenza"
(Eraclito)



Re: [DISCUSS] Time for 2.0.7?

2017-12-19 Thread Massimiliano Perrone

+1

Massi


Il 19/12/2017 08:50, Francesco Chicchiriccò ha scritto:

Hi all,
it seems quite some work has been done for 2.0.7 [1], and I believe 
the remaining issues [2] can be safely moved to 2.0.8 (or later), 
hence I was thinking: what about delivering Apache Syncope 2.0.7 as a 
nice Christmas present to our community?


Do you see any issue with that?
Regards.

[1] 
https://issues.apache.org/jira/issues/?jql=statusCategory%20%3D%20done%20AND%20project%20%3D%2012313120%20AND%20fixVersion%20%3D%2012341740%20ORDER%20BY%20priority%20DESC%2C%20key%20ASC
[2] 
https://issues.apache.org/jira/issues/?jql=statusCategory%20%3D%20new%20AND%20project%20%3D%2012313120%20AND%20fixVersion%20%3D%2012341740%20ORDER%20BY%20priority%20DESC%2C%20key%20ASC




--
Massimiliano Perrone
Tel +39 393 9121310
Tirasa S.r.l.
http://www.tirasa.net
"L'apprendere molte cose non insegna l'intelligenza"
(Eraclito)



Re: [VOTE] Apache Syncope 2.0.6

2017-10-10 Thread Massimiliano Perrone

+1

Massi


Il 09/10/2017 12:06, Francesco Chicchiriccò ha scritto:

I've created a 2.0.6 release, with the following artifacts up for a vote:

GIT source tag (4d88e9b510014da81291d095830a5ddcae9108c4):
https://git-wip-us.apache.org/repos/asf?p=syncope.git;a=commit;h=d9da82f6ae760c5b612462b064a7ba5fa9b97179 



List of changes:
https://git-wip-us.apache.org/repos/asf?p=syncope.git;a=blob;f=CHANGES;h=42f3c38dd48ab0dc1b857bfdf84c717b43be33e4;hb=d9da82f6ae760c5b612462b064a7ba5fa9b97179 



Staging artifacts:
https://dist.apache.org/repos/dist/dev/syncope/2.0.6/

Maven staging repo:
https://repository.apache.org/content/repositories/orgapachesyncope-1045/

Staging site:
http://syncope.apache.org/2.0.6/index.html

PGP release keys (signed using 273DF287):
http://www.apache.org/dist/syncope/KEYS

Vote will be open for 72 hours.

[ ] +1 approve
[ ] +0 no opinion
[ ] -1 disapprove (and reason why)

Here's my +1
Regards.



--
Massimiliano Perrone
Tel +39 393 9121310
Tirasa S.r.l.
http://www.tirasa.net
"L'apprendere molte cose non insegna l'intelligenza"
(Eraclito)



Re: [DISCUSS] Time for 2.0.6?

2017-10-05 Thread Massimiliano Perrone



Il 05/10/2017 08:38, Francesco Chicchiriccò ha scritto:

Hi all,
it seems that Syncope 2.0.6 is at a point where the issues left [1] 
are either new features that can be safely moved to 2.0.7 (or 2.0.8, 
or even 2.1.0) or minor issues which seem not to have an easy or 
effective fix immediately available.


From the other side, instead, several bugs have been already fixed 
[2], some of them quite relevant.


What about releasing 2.0.6 anytime soon? I don't see many reasons to 
wait for more.


Regards.

[1] 
https://issues.apache.org/jira/issues/?jql=statusCategory%20=%20new%20AND%20project%20=%2012313120%20AND%20fixVersion%20=%2012341555%20ORDER%20BY%20priority%20DESC,%20key%20ASC
[2] 
https://issues.apache.org/jira/issues/?jql=statusCategory%20=%20done%20AND%20project%20=%2012313120%20AND%20fixVersion%20=%2012341555%20ORDER%20BY%20priority%20DESC,%20key%20ASC



+1

Massi

--
Massimiliano Perrone
Tel +39 393 9121310
Tirasa S.r.l.
http://www.tirasa.net
"L'apprendere molte cose non insegna l'intelligenza"
(Eraclito)



Re: [VOTE] Apache Syncope 2.0.5 (take 3)

2017-09-06 Thread Massimiliano Perrone

+1

Max


Il 06/09/2017 11:36, Francesco Chicchiriccò ha scritto:

I've created a 2.0.5 release, with the following artifacts up for a vote:

GIT source tag (4d88e9b510014da81291d095830a5ddcae9108c4):
https://git-wip-us.apache.org/repos/asf?p=syncope.git;a=commit;h=4d88e9b510014da81291d095830a5ddcae9108c4 



List of changes:
https://git-wip-us.apache.org/repos/asf?p=syncope.git;a=blob;f=CHANGES;h=190515a58cd397a9993aa16935584d2df8fbd123;hb=4d88e9b510014da81291d095830a5ddcae9108c4 



Staging artifacts:
https://dist.apache.org/repos/dist/dev/syncope/2.0.5/

Maven staging repo:
https://repository.apache.org/content/repositories/orgapachesyncope-1044/

Staging site:
http://syncope.apache.org/2.0.5/index.html

PGP release keys (signed using 273DF287):
http://www.apache.org/dist/syncope/KEYS

Vote will be open for 72 hours.

[ ] +1 approve
[ ] +0 no opinion
[ ] -1 disapprove (and reason why)

Here's my +1
Regards.


--
Massimiliano Perrone
Tel +39 393 9121310
Tirasa S.r.l.
http://www.tirasa.net
"L'apprendere molte cose non insegna l'intelligenza"
(Eraclito)



Re: [VOTE] Apache Syncope 2.0.5

2017-09-05 Thread Massimiliano Perrone

+1

Massi


Il 05/09/2017 11:35, Francesco Chicchiriccò ha scritto:

I've created a 2.0.5 release, with the following artifacts up for a vote:

GIT source tag (726614b80cd25168637754f88cdb2f9030e77012):
https://git-wip-us.apache.org/repos/asf?p=syncope.git;a=commit;h=726614b80cd25168637754f88cdb2f9030e77012 



List of changes:
https://git-wip-us.apache.org/repos/asf?p=syncope.git;a=blob;f=CHANGES;h=190515a58cd397a9993aa16935584d2df8fbd123;hb=726614b80cd25168637754f88cdb2f9030e77012 



Staging artifacts:
https://dist.apache.org/repos/dist/dev/syncope/2.0.5/

Maven staging repo:
https://repository.apache.org/content/repositories/orgapachesyncope-1043/

Staging site:
http://syncope.apache.org/2.0.5/index.html

PGP release keys (signed using 273DF287):
http://www.apache.org/dist/syncope/KEYS

Vote will be open for 72 hours.

[ ] +1 approve
[ ] +0 no opinion
[ ] -1 disapprove (and reason why)

Here's my +1
Regards.


--
Massimiliano Perrone
Tel +39 393 9121310
Tirasa S.r.l.
http://www.tirasa.net
"L'apprendere molte cose non insegna l'intelligenza"
(Eraclito)



Re: [VOTE] Apache Syncope 2.0.5

2017-09-04 Thread Massimiliano Perrone

+1


massi


Il 04/09/2017 11:38, Francesco Chicchiriccò ha scritto:

I've created a 2.0.5 release, with the following artifacts up for a vote:

GIT source tag (5c388d4455f58c50c52ee467e81fbac4e2aea017):
https://git-wip-us.apache.org/repos/asf?p=syncope.git;a=commit;h=5c388d4455f58c50c52ee467e81fbac4e2aea017 



List of changes:
https://git-wip-us.apache.org/repos/asf?p=syncope.git;a=blob;f=CHANGES;h=4c69d58b9cac1f46abcd99d0b4fecdd4f5412fbe;hb=5c388d4455f58c50c52ee467e81fbac4e2aea017 



Staging artifacts:
https://dist.apache.org/repos/dist/dev/syncope/2.0.5/

Maven staging repo:
https://repository.apache.org/content/repositories/orgapachesyncope-1042/

Staging site:
http://syncope.apache.org/2.0.5/downloads.html

PGP release keys (signed using 273DF287):
http://www.apache.org/dist/syncope/KEYS

Vote will be open for 72 hours.

[ ] +1 approve
[ ] +0 no opinion
[ ] -1 disapprove (and reason why)

Here's my +1
Regards.



--
Massimiliano Perrone
Tel +39 393 9121310
Tirasa S.r.l.
http://www.tirasa.net
"L'apprendere molte cose non insegna l'intelligenza"
(Eraclito)



Re: Access Tokens label in dashboard panel

2017-07-13 Thread Massimiliano Perrone



Il 13/07/2017 10:08, Francesco Chicchiriccò ha scritto:

On 12/07/2017 19:02, Colm O hEigeartaigh wrote:

(Active) SSO Tokens?


+1 for "SSO Tokens"


+1



Regards.

On Wed, Jul 12, 2017 at 4:51 PM, Francesco Chicchiriccò 
<ilgro...@apache.org> wrote:



Hi ,
I am not completely sure that "Access Token" is actually misleading -
wikipedia does not even mention OAuth about it:

https://en.wikipedia.org/wiki/Access_token

Anyway, if you think so we can change that label; only, I don't 
think that

anything about "session" should be used, as JWT are not sessions.

Other proposals?

Regards.

On 12/07/2017 17:19, Colm O hEigeartaigh wrote:


Yeah makes sense.

Colm.

On Tue, Jul 11, 2017 at 8:53 PM, Massimiliano Perrone <
massimiliano.perr...@tirasa.net> wrote:

Hi guys,

the dashboard page has four tabs. As you know one of this is called
Access
Tokens...

Maybe we should change that name because access token is the standard
name
of an OAuth token so it's misleading. Maybe we can use something like
sessions or authenticated sessions or authenticated users...

WDYT?

Best regards,

Massi




--
Massimiliano Perrone
Tel +39 393 9121310
Tirasa S.r.l.
http://www.tirasa.net
"L'apprendere molte cose non insegna l'intelligenza"
(Eraclito)



Access Tokens label in dashboard panel

2017-07-11 Thread Massimiliano Perrone


Hi guys, 

the dashboard page has four tabs. As you know one of this is called Access 
Tokens... 




Maybe we should change that name because access token is the standard name of 
an OAuth token so it's misleading. Maybe we can use something like sessions or 
authenticated sessions or authenticated users... 




WDYT? 





Best regards, 

Massi 
-- 
Massimiliano Perrone
Tel +39 393 9121310
Tirasa S.r.l. http://www.tirasa.net "L'apprendere molte cose non insegna 
l'intelligenza"
(Eraclito) 



[jira] [Updated] (SYNCOPE-1092) System Information appears scrolling on the right

2017-05-24 Thread Massimiliano Perrone (JIRA)

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

Massimiliano Perrone updated SYNCOPE-1092:
--
Description: 
Going on Syncope Console (I found it using the Apache demo) I found a strange 
behavior scrolling to the right (using the two fingers on a mousepad)...
The System Information table appears! When it should be invisible until someone 
use the up-right-corner botton.

To solve it we need to change the css file [1] at row 717 from 

{code}
.control-sidebar {
  position: absolute;
  padding-top: 50px;
  z-index: 1010;
}
{code}

to 

{code}
.control-sidebar {
  position: fixed;
  padding-top: 50px;
  z-index: 1010;
}
{code}

(please have a check :))

[1] 
http://syncope-vm.apache.org:9080/syncope-console/wicket/resource/org.apache.syncope.client.console.themes.AdminLTECssResourceReference/css/AdminLTE-ver-369B017375C8C4A0878CC3637CD022A5.css

  was:
Going on Syncope Console (I found it using the Apache demo) I found a strange 
behavior scrolling to the right (using the two fingers on a mousepad)...
The System Information table appears! When it should be invisible until someone 
use the up-right-corner botton.

To solve it we need to change the css file [1] at row 717 from 

{code}
.control-sidebar {
  position: absolute;
  padding-top: 50px;
  z-index: 1010;
}
{code}

to 

{code}
.control-sidebar {
  position: fixed;
  padding-top: 50px;
  z-index: 1010;
}
{code}

[1] 
http://syncope-vm.apache.org:9080/syncope-console/wicket/resource/org.apache.syncope.client.console.themes.AdminLTECssResourceReference/css/AdminLTE-ver-369B017375C8C4A0878CC3637CD022A5.css


> System Information appears scrolling on the right
> -
>
> Key: SYNCOPE-1092
> URL: https://issues.apache.org/jira/browse/SYNCOPE-1092
> Project: Syncope
>  Issue Type: Bug
>  Components: console
>Affects Versions: 2.0.3
>    Reporter: Massimiliano Perrone
>Priority: Minor
> Fix For: 2.0.4
>
>
> Going on Syncope Console (I found it using the Apache demo) I found a strange 
> behavior scrolling to the right (using the two fingers on a mousepad)...
> The System Information table appears! When it should be invisible until 
> someone use the up-right-corner botton.
> To solve it we need to change the css file [1] at row 717 from 
> {code}
> .control-sidebar {
>   position: absolute;
>   padding-top: 50px;
>   z-index: 1010;
> }
> {code}
> to 
> {code}
> .control-sidebar {
>   position: fixed;
>   padding-top: 50px;
>   z-index: 1010;
> }
> {code}
> (please have a check :))
> [1] 
> http://syncope-vm.apache.org:9080/syncope-console/wicket/resource/org.apache.syncope.client.console.themes.AdminLTECssResourceReference/css/AdminLTE-ver-369B017375C8C4A0878CC3637CD022A5.css



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


[jira] [Updated] (SYNCOPE-1092) System Information appears scrolling on the right

2017-05-24 Thread Massimiliano Perrone (JIRA)

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

Massimiliano Perrone updated SYNCOPE-1092:
--
Description: 
Going on Syncope Console (I found it using the Apache demo) I found a strange 
behavior scrolling to the right (using the two fingers on a mousepad)...
The System Information table appears! When it should be invisible until someone 
use the up-right-corner botton.

To solve it we need to change the css file [1] at row 717 from 

{code}
.control-sidebar {
  position: absolute;
  padding-top: 50px;
  z-index: 1010;
}
{code}

to 

{code}
.control-sidebar {
  position: fixed;
  padding-top: 50px;
  z-index: 1010;
}
{code}

[1] 
http://syncope-vm.apache.org:9080/syncope-console/wicket/resource/org.apache.syncope.client.console.themes.AdminLTECssResourceReference/css/AdminLTE-ver-369B017375C8C4A0878CC3637CD022A5.css

  was:
Going on Syncope Console (I found it using the Apache demo) I found a strange 
behavior scrolling to the right (using the two fingers on a mousepad)...
The System Information table appears! When it should be invisible until someone 
use the up-right-corner botton.

To solve it we need to change the css file [1] at row 717 from 


.control-sidebar {
  position: absolute;
  padding-top: 50px;
  z-index: 1010;
}


to 


.control-sidebar {
  position: fixed;
  padding-top: 50px;
  z-index: 1010;
}


[1] 
http://syncope-vm.apache.org:9080/syncope-console/wicket/resource/org.apache.syncope.client.console.themes.AdminLTECssResourceReference/css/AdminLTE-ver-369B017375C8C4A0878CC3637CD022A5.css


> System Information appears scrolling on the right
> -
>
> Key: SYNCOPE-1092
> URL: https://issues.apache.org/jira/browse/SYNCOPE-1092
> Project: Syncope
>  Issue Type: Bug
>  Components: console
>Affects Versions: 2.0.3
>    Reporter: Massimiliano Perrone
>Priority: Minor
> Fix For: 2.0.4
>
>
> Going on Syncope Console (I found it using the Apache demo) I found a strange 
> behavior scrolling to the right (using the two fingers on a mousepad)...
> The System Information table appears! When it should be invisible until 
> someone use the up-right-corner botton.
> To solve it we need to change the css file [1] at row 717 from 
> {code}
> .control-sidebar {
>   position: absolute;
>   padding-top: 50px;
>   z-index: 1010;
> }
> {code}
> to 
> {code}
> .control-sidebar {
>   position: fixed;
>   padding-top: 50px;
>   z-index: 1010;
> }
> {code}
> [1] 
> http://syncope-vm.apache.org:9080/syncope-console/wicket/resource/org.apache.syncope.client.console.themes.AdminLTECssResourceReference/css/AdminLTE-ver-369B017375C8C4A0878CC3637CD022A5.css



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


[jira] [Created] (SYNCOPE-1092) System Information appears scrolling on the right

2017-05-24 Thread Massimiliano Perrone (JIRA)
Massimiliano Perrone created SYNCOPE-1092:
-

 Summary: System Information appears scrolling on the right
 Key: SYNCOPE-1092
 URL: https://issues.apache.org/jira/browse/SYNCOPE-1092
 Project: Syncope
  Issue Type: Bug
  Components: console
Affects Versions: 2.0.3
Reporter: Massimiliano Perrone
Priority: Minor
 Fix For: 2.0.4


Going on Syncope Console (I found it using the Apache demo) I found a strange 
behavior scrolling to the right (using the two fingers on a mousepad)...
The System Information table appears! When it should be invisible until someone 
use the up-right-corner botton.

To solve it we need to change the css file [1] at row 717 from 


.control-sidebar {
  position: absolute;
  padding-top: 50px;
  z-index: 1010;
}


to 


.control-sidebar {
  position: fixed;
  padding-top: 50px;
  z-index: 1010;
}


[1] 
http://syncope-vm.apache.org:9080/syncope-console/wicket/resource/org.apache.syncope.client.console.themes.AdminLTECssResourceReference/css/AdminLTE-ver-369B017375C8C4A0878CC3637CD022A5.css



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


Re: [DISCUSS] GSoC 2017

2017-02-06 Thread Massimiliano Perrone


- Messaggio originale -
> Da: "Francesco Chicchiriccò" <ilgro...@apache.org>
> A: "dev" <dev@syncope.apache.org>
> Inviato: Lunedì, 6 febbraio 2017 11:43:26
> Oggetto: [DISCUSS] GSoC 2017

> Hi all,
> GSoC 2017 is coming, and The ASF will be again part of it.
> 
> Last year we had our fist experience with GSoC and, as a result, there
> is now an Eclipse IDE plugin among our published artifacts.
> We could also have a Netbeans IDE plugin, but that one was a bit
> unfortunate, and by the way a PR on such subject is still being worked.
> 
> I was wondering if we want to propose something for this year too; here
> are my ideas:
> 
>  * SCIM v2 RESTful interface (naturally, if Adrian is not still working
>on it, or not intentioned to contribute it back)
>  * Social registration for Enduser UI
>  * Support for enroll / associate mobile devices to users via Enduser UI

+1;

but something else like a mobile app for administrator with TODO list or system 
arch (to check whether every connectors are "green")?

Massi

> 
> WDYT?
> 
> Regards.
> 
> --
> Francesco Chicchiriccò
> 
> Tirasa - Open Source Excellence
> http://www.tirasa.net/
> 
> Member at The Apache Software Foundation
> Syncope, Cocoon, Olingo, CXF, OpenJPA, PonyMail
> http://home.apache.org/~ilgrosso/

-- 
Massimiliano Perrone
Tel +39 393 9121310

Tirasa S.r.l.
Viale D'Annunzio 267 - 65127 Pescara
Tel +39 0859116307 / FAX +39 085973
http://www.tirasa.net

"L'apprendere molte cose non insegna l'intelligenza"
(Eraclito)


Re: [VOTE] Apache Syncope 2.0.2

2017-01-27 Thread Massimiliano Perrone

+1.

Have a nice weekend.
Massi


Il 27/01/2017 17:26, Francesco Chicchiriccò ha scritto:

I've created a 2.0.2 release, with the following artifacts up for a vote:

GIT source tag (1ea194dbd):
https://git-wip-us.apache.org/repos/asf?p=syncope.git;a=tag;h=1ea194dbd

List of changes:
https://git-wip-us.apache.org/repos/asf?p=syncope.git;a=blob;f=CHANGES;h=e0fa5e9544c89df568e437e93622153917699b3f;hb=aff1e09e49b8c8f55966f316318650ae397891b5 



Staging artifacts:
https://dist.apache.org/repos/dist/dev/syncope/2.0.2

Maven staging repo:
https://repository.apache.org/content/repositories/orgapachesyncope-1037/

Staging site:
http://syncope.apache.org/2.0.2/

PGP release keys (signed using 273DF287):
http://www.apache.org/dist/syncope/KEYS

Vote will be open for 72 hours.

[ ] +1 approve
[ ] +0 no opinion
[ ] -1 disapprove (and reason why)

Here's my +1
Regards.



--
Massimiliano Perrone
Tel +39 393 9121310

Tirasa S.r.l.
Viale D'Annunzio 267 - 65127 Pescara
Tel +39 0859116307 / FAX +39 085973
http://www.tirasa.net

"L'apprendere molte cose non insegna l'intelligenza"
(Eraclito)



Re: [VOTE] Apache Syncope 1.2.10

2017-01-24 Thread Massimiliano Perrone

+1,
BR
--
Massimiliano Perrone
Tel +39 393 9121310
Tirasa S.r.l.
http://www.tirasa.net
"L'apprendere molte cose non insegna l'intelligenza"
(Eraclito) martedì, 24 gennaio 2017, 09:59AM +01:00 da Francesco Chicchiriccò  
ilgro...@apache.org :

>I've created a 1.2.10 release, with the following artifacts up for a vote:
>
>GIT source tag (1c1e1f064):
>https://git-wip-us.apache.org/repos/asf?p=syncope.git;a=tag;h=1c1e1f064
>
>List of changes:
>https://git-wip-us.apache.org/repos/asf?p=syncope.git;a=blob;f=CHANGES;h=a79f41d8fd765e492baceb2485a739815f8c8ae7;hb=347833ef654a390e95856c5a9d010e4636a13e57
>
>Staging artifacts:
>https://dist.apache.org/repos/dist/dev/syncope/1.2.10
>
>Maven staging repo:
>https://repository.apache.org/content/repositories/orgapachesyncope-1036/
>
>Staging site:
>http://syncope.apache.org/1.2.10/
>
>PGP release keys (signed using 273DF287):
>http://www.apache.org/dist/syncope/KEYS
>
>Vote will be open for 72 hours.
>
>[ ] +1  approve
>[ ] +0  no opinion
>[ ] -1  disapprove (and reason why)
>
>Here's my +1
>Regards.
>
>-- 
>Francesco Chicchiriccò
>
>Tirasa - Open Source Excellence
>http://www.tirasa.net/
>
>Member at The Apache Software Foundation
>Syncope, Cocoon, Olingo, CXF, OpenJPA, PonyMail
>http://home.apache.org/~ilgrosso/
>
>


Re: [VOTE] Apache Syncope 2.0.1

2016-10-23 Thread Massimiliano Perrone



Il 23/10/2016 11:56, Marco Di Sabatino Di Diodoro ha scritto:



Il 21/10/2016 11:15, Francesco Chicchiriccò ha scritto:

On 21/10/2016 11:13, Francesco Chicchiriccò wrote:
I've created a $VERSION release, with the following artifacts up for 
a vote:


It's 2.0.1, sorry for the inconvenience.


GIT source tag (105228f7f):
https://git-wip-us.apache.org/repos/asf?p=syncope.git;a=tag;h=105228f7f

List of changes:
https://git-wip-us.apache.org/repos/asf?p=syncope.git;a=blob;f=CHANGES;h=2540f4a6564d7a4c5d1e8a38b53a7c0a0b4e06ab;hb=dd0af57f98167158a8aef0dc08a9b60dcd1f1951 



Staging artifacts:
https://dist.apache.org/repos/dist/dev/syncope/2.0.1/

Maven staging repo:
https://repository.apache.org/content/repositories/orgapachesyncope-1035/ 



Staging site:
http://syncope.apache.org/2.0.1/

PGP release keys (signed using 273DF287):
http://www.apache.org/dist/syncope/KEYS

Vote will be open for 72 hours.

[ ] +1  approve
[ ] +0  no opinion
[ ] -1  disapprove (and reason why)


+1
Regards
Marco


+1 for me.

Massi




Here is my +1.
Regards.






--
Massimiliano Perrone
Tel +39 393 9121310

Tirasa S.r.l.
Viale D'Annunzio 267 - 65127 Pescara
Tel +39 0859116307 / FAX +39 085973
http://www.tirasa.net

"L'apprendere molte cose non insegna l'intelligenza"
(Eraclito)



Re: [VOTE] Apache Syncope 1.2.9

2016-10-07 Thread Massimiliano Perrone

+1
--
Massimiliano Perrone
Tel +39 393 9121310
Tirasa S.r.l.
http://www.tirasa.net
"L'apprendere molte cose non insegna l'intelligenza"
(Eraclito) venerdì, 07 ottobre 2016, 11:31AM +02:00 da Francesco Chicchiriccò  
ilgro...@apache.org :

>I've created a 1.2.9 release, with the following artifacts up for a vote:
>
>GIT source tag (f18724eff):
>https://git-wip-us.apache.org/repos/asf?p=syncope.git;a=tag;h=f18724eff
>
>List of changes:
>https://git-wip-us.apache.org/repos/asf?p=syncope.git;a=blob;f=CHANGES;h=040373c225cf12dfdeb7752db29dfae380d64e2c;hb=fb9e88ba2a250bedaee768360214e66194bff1ba
>
>
>Staging artifacts:
>https://dist.apache.org/repos/dist/dev/syncope/1.2.9
>
>Maven staging repo:
>https://repository.apache.org/content/repositories/orgapachesyncope-1034/
>
>Staging site:
>http://syncope.apache.org/1.2.9/
>
>PGP release keys (signed using 273DF287):
>http://www.apache.org/dist/syncope/KEYS
>
>Vote will be open for 72 hours.
>
>[ ] +1  approve
>[ ] +0  no opinion
>[ ] -1  disapprove (and reason why)
>
>
>Here's my +1
>Regards.
>
>-- 
>Francesco Chicchiriccò
>
>Tirasa - Open Source Excellence
>http://www.tirasa.net/
>
>Member at The Apache Software Foundation
>Syncope, Cocoon, Olingo, CXF, OpenJPA, PonyMail
>http://home.apache.org/~ilgrosso/
>


Re: [VOTE] Apache Syncope 2.0.0

2016-09-09 Thread Massimiliano Perrone

+1
Massi
--
Massimiliano Perrone
Tel +39 393 9121310
Tirasa S.r.l.
http://www.tirasa.net
"L'apprendere molte cose non insegna l'intelligenza"
(Eraclito) venerdì, 09 settembre 2016, 02:42PM +02:00 da Francesco Chicchiriccò 
 ilgro...@apache.org :

>I've created a 2.0.0 release, with the following artifacts up for a vote:
>
>GIT source tag (002c01ab8):
>https://git-wip-us.apache.org/repos/asf?p=syncope.git;a=tag;h=002c01ab8
>
>List of changes:
>https://git-wip-us.apache.org/repos/asf?p=syncope.git;a=blob;f=CHANGES;h=a9814cb348cfb8a39d42a16c50ed873eed5ab9b3
>
>Staging artifacts:
>https://dist.apache.org/repos/dist/dev/syncope/2.0.0/
>
>Maven staging repo:
>https://repository.apache.org/content/repositories/orgapachesyncope-1033/
>
>Staging site:
>http://syncope.apache.org/2.0.0/
>
>PGP release keys (signed using 273DF287):
>http://www.apache.org/dist/syncope/KEYS
>
>Vote will be open for 72 hours.
>
>[ ] +1 approve
>[ ] +0 no opinion
>[ ] -1 disapprove (and reason why)
>
>Here's my +1.
>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,
>CXF Committer, OpenJPA Committer, PonyMail PPMC
>http://home.apache.org/~ilgrosso/
>


Re: [DISCUSS] Next releases

2016-08-24 Thread Massimiliano Perrone

+ 1
Also because this is a very important release so I think it's better to wait 
for half September when will start "the new year" and the people have surely 
finished their holidays.
Regards,
Massi
--
Massimiliano Perrone
Tel +39 393 9121310
Tirasa S.r.l.
http://www.tirasa.net
"L'apprendere molte cose non insegna l'intelligenza"
(Eraclito) mercoledì, 24 agosto 2016, 09:54AM +02:00 da Francesco Chicchiriccò  
ilgro...@apache.org :

>Hi all,
>the work towards 2.0.0 seems to be almost complete: I should be able to 
>finish the larger missing part (e.g. documentation as per SYNCOPE-700) 
>by the end of this week.
>
>At that point I would like to cut the last milestone release 2.0.0-M5 
>(mainly to verify once more that the release process is tuned up) then, 
>after a week or two, go out with 2.0.0.
>
>Do you see any problems with this approach?
>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,
>CXF Committer, OpenJPA Committer, PonyMail PPMC
>http://home.apache.org/~ilgrosso/
>


Re: REST API authentication in 2.0.0

2016-06-28 Thread Massimiliano Perrone


- Messaggio originale -
> Da: "Colm O hEigeartaigh" <cohei...@apache.org>
> A: "dev" <dev@syncope.apache.org>
> Inviato: Martedì, 28 giugno 2016 17:15:28
> Oggetto: Re: REST API authentication in 2.0.0

> Ok thanks, this sounds like a bug then? 

I think so.

Max

> The user is not authenticated and
> so Syncope should be returning 401 instead of 403? As things stand, there
> is no way to use a web browser to access the REST API unless you manually
> configure the basic auth parameters somehow.
> 
> Colm.
> 
> On Tue, Jun 28, 2016 at 4:09 PM, Massimiliano Perrone <
> massimiliano.perr...@tirasa.net> wrote:
> 
>>
>>
>> - Messaggio originale -
>> > Da: "Sergey Beryozkin" <sberyoz...@gmail.com>
>> > A: "dev" <dev@syncope.apache.org>
>> > Inviato: Martedì, 28 giugno 2016 17:00:05
>> > Oggetto: Re: REST API authentication in 2.0.0
>>
>> > 403 is typically reported when the authenticated user is forbidden (not
>> > in some role) to access a given resource. So might be a regression. I'm
>> > not 100% sure if some sites do return 403 instead of 401 though when the
>> > authentication fails. Possible confusion can arise given that 401 error
>> > message is "Unauthorized"
>>
>>
>> My experience is 100% with 403 for authenticated user with no permissions
>> (e.g roles), 401 for a resource that needs an authenticated user and you
>> are trying to use it without authentication.
>>
>> BR,
>> Massi
>>
>> >
>> > Cheers, Sergey
>> > On 28/06/16 15:40, Colm O hEigeartaigh wrote:
>> >> Hi,
>> >>
>> >> Just wanted to check before filing a JIRA. With the latest
>> 2.0.0-SNAPSHOT,
>> >> I noticed that accessing the REST API without supplying a
>> username/password
>> >> returns 403 as opposed to the old 401.
>> >>
>> >> wget http://localhost:9080/syncope/rest/users
>> >>
>> >> --2016-06-28 15:40:01--  http://localhost:9080/syncope/rest/users
>> >> Resolving localhost (localhost)... 127.0.0.1
>> >> Connecting to localhost (localhost)|127.0.0.1|:9080... connected.
>> >> HTTP request sent, awaiting response... 403
>> >> 2016-06-28 15:40:01 ERROR 403: (no description).
>> >>
>> >> Whereas with 1.2.7:
>> >>
>> >> wget http://localhost:9080/syncope/rest/users
>> >> --2016-06-28 15:29:42--  http://localhost:9080/syncope/rest/users
>> >> Resolving localhost (localhost)... 127.0.0.1
>> >> Connecting to localhost (localhost)|127.0.0.1|:9080... connected.
>> >> HTTP request sent, awaiting response... 401 Unauthorized
>> >>
>> >> Username/Password Authentication Failed.
>> >>
>> >> This means that if you open up a web browser and try to access say:
>> >>
>> >> http://localhost:9080/syncope/rest/users
>> >>
>> >> a pop-up windows does not appear for the user to enter the
>> user/password.
>> >> Was there a reason for this change or will I file a bug?
>> >>
>> >> Thanks,
>> >>
>> >> Colm.
>> >>
>>
>> --
>> Massimiliano Perrone
>> Tel +39 393 9121310
>>
>> Tirasa S.r.l.
>> Viale D'Annunzio 267 - 65127 Pescara
>> Tel +39 0859116307 / FAX +39 085973
>> http://www.tirasa.net
>>
>> "L'apprendere molte cose non insegna l'intelligenza"
>> (Eraclito)
>>
> 
> 
> 
> --
> Colm O hEigeartaigh
> 
> Talend Community Coder
> http://coders.talend.com

-- 
Massimiliano Perrone
Tel +39 393 9121310

Tirasa S.r.l.
Viale D'Annunzio 267 - 65127 Pescara
Tel +39 0859116307 / FAX +39 085973
http://www.tirasa.net

"L'apprendere molte cose non insegna l'intelligenza"
(Eraclito)


Re: REST API authentication in 2.0.0

2016-06-28 Thread Massimiliano Perrone


- Messaggio originale -
> Da: "Sergey Beryozkin" <sberyoz...@gmail.com>
> A: "dev" <dev@syncope.apache.org>
> Inviato: Martedì, 28 giugno 2016 17:00:05
> Oggetto: Re: REST API authentication in 2.0.0

> 403 is typically reported when the authenticated user is forbidden (not
> in some role) to access a given resource. So might be a regression. I'm
> not 100% sure if some sites do return 403 instead of 401 though when the
> authentication fails. Possible confusion can arise given that 401 error
> message is "Unauthorized"


My experience is 100% with 403 for authenticated user with no permissions (e.g 
roles), 401 for a resource that needs an authenticated user and you are trying 
to use it without authentication.

BR,
Massi

> 
> Cheers, Sergey
> On 28/06/16 15:40, Colm O hEigeartaigh wrote:
>> Hi,
>>
>> Just wanted to check before filing a JIRA. With the latest 2.0.0-SNAPSHOT,
>> I noticed that accessing the REST API without supplying a username/password
>> returns 403 as opposed to the old 401.
>>
>> wget http://localhost:9080/syncope/rest/users
>>
>> --2016-06-28 15:40:01--  http://localhost:9080/syncope/rest/users
>> Resolving localhost (localhost)... 127.0.0.1
>> Connecting to localhost (localhost)|127.0.0.1|:9080... connected.
>> HTTP request sent, awaiting response... 403
>> 2016-06-28 15:40:01 ERROR 403: (no description).
>>
>> Whereas with 1.2.7:
>>
>> wget http://localhost:9080/syncope/rest/users
>> --2016-06-28 15:29:42--  http://localhost:9080/syncope/rest/users
>> Resolving localhost (localhost)... 127.0.0.1
>> Connecting to localhost (localhost)|127.0.0.1|:9080... connected.
>> HTTP request sent, awaiting response... 401 Unauthorized
>>
>> Username/Password Authentication Failed.
>>
>> This means that if you open up a web browser and try to access say:
>>
>> http://localhost:9080/syncope/rest/users
>>
>> a pop-up windows does not appear for the user to enter the user/password.
>> Was there a reason for this change or will I file a bug?
>>
>> Thanks,
>>
>> Colm.
>>

-- 
Massimiliano Perrone
Tel +39 393 9121310

Tirasa S.r.l.
Viale D'Annunzio 267 - 65127 Pescara
Tel +39 0859116307 / FAX +39 085973
http://www.tirasa.net

"L'apprendere molte cose non insegna l'intelligenza"
(Eraclito)


Re: [VOTE] Apache Syncope 2.0.0-M4

2016-06-24 Thread Massimiliano Perrone



Il 24/06/2016 11:39, Francesco Chicchiriccò ha scritto:
I've created a 2.0.0-M4 release, with the following artifacts up for a 
vote:


GIT source tag (07ca994c6):
https://git-wip-us.apache.org/repos/asf?p=syncope.git;a=tag;h=07ca994c6

List of changes:
https://git-wip-us.apache.org/repos/asf?p=syncope.git;a=blob_plain;f=CHANGES;h=bbaca1d028f206d3f01a35c08bd9107459e8953d 



Staging artifacts:
https://dist.apache.org/repos/dist/dev/syncope/2.0.0-M4/

Maven staging repo:
https://repository.apache.org/content/repositories/orgapachesyncope-1028/

Staging site:
http://syncope.apache.org/2.0.0-M4/

PGP release keys (signed using 273DF287):
http://www.apache.org/dist/syncope/KEYS

Vote will be open for 72 hours.

[ ] +1  approve
[ ] +0  no opinion
[ ] -1  disapprove (and reason why)

Here's my +1
Regards.


+1
BR,
Massi

--
Massimiliano Perrone
Tel +39 393 9121310

Tirasa S.r.l.
Viale D'Annunzio 267 - 65127 Pescara
Tel +39 0859116307 / FAX +39 085973
http://www.tirasa.net

"L'apprendere molte cose non insegna l'intelligenza"
(Eraclito)



Re: [VOTE] Apache Syncope 1.2.8

2016-06-03 Thread Massimiliano Perrone


- Messaggio originale -
> Da: "Francesco Chicchiriccò" <ilgro...@apache.org>
> A: "dev" <dev@syncope.apache.org>
> Inviato: Venerdì, 3 giugno 2016 10:19:50
> Oggetto: [VOTE] Apache Syncope 1.2.8

> I've created a 1.2.8 release, with the following artifacts up for a vote:
> 
> GIT source tag (a98674da5):
> https://git-wip-us.apache.org/repos/asf?p=syncope.git;a=tag;h=a98674da5
> 
> List of changes:
> https://git-wip-us.apache.org/repos/asf?p=syncope.git;a=blob_plain;f=CHANGES;h=f5de8f636a8ac8af61ce9143d5f5553039ca4baf
> 
> 
> Staging artifacts:
> https://dist.apache.org/repos/dist/dev/syncope/1.2.8/
> 
> Maven staging repo:
> https://repository.apache.org/content/repositories/orgapachesyncope-1026/
> 
> Staging site:
> http://syncope.apache.org/2.0.0-M3/
> 
> PGP release keys (signed using 273DF287):
> http://www.apache.org/dist/syncope/KEYS
> 
> Vote will be open for 72 hours.
> 
> [ ] +1  approve
> [ ] +0  no opinion
> [ ] -1  disapprove (and reason why)

+1
BR,
Massi

> 
> Here's my +1
> 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,
> CXF Committer, OpenJPA Committer, PonyMail PPMC
> http://home.apache.org/~ilgrosso/

-- 
Massimiliano Perrone
Tel +39 393 9121310

Tirasa S.r.l.
Viale D'Annunzio 267 - 65127 Pescara
Tel +39 0859116307 / FAX +39 085973
http://www.tirasa.net

"L'apprendere molte cose non insegna l'intelligenza"
(Eraclito)


Re: [VOTE] Apache Syncope 2.0.0-M3

2016-06-03 Thread Massimiliano Perrone


- Messaggio originale -
> Da: "Francesco Chicchiriccò" <ilgro...@apache.org>
> A: "dev" <dev@syncope.apache.org>
> Inviato: Venerdì, 3 giugno 2016 10:23:32
> Oggetto: [VOTE] Apache Syncope 2.0.0-M3

> I've created a 2.0.0-M3 release, with the following artifacts up for a vote:
> 
> GIT source tag (c20d0c419):
> https://git-wip-us.apache.org/repos/asf?p=syncope.git;a=tag;h=c20d0c419
> 
> List of changes:
> https://git-wip-us.apache.org/repos/asf?p=syncope.git;a=blob_plain;f=CHANGES;h=0b6afc3773b38ce431555a284d34b3157ea5de23
> 
> Staging artifacts:
> https://dist.apache.org/repos/dist/dev/syncope/2.0.0-M3/
> 
> Maven staging repo:
> https://repository.apache.org/content/repositories/orgapachesyncope-1027/
> 
> Staging site:
> http://syncope.apache.org/2.0.0-M3/
> 
> PGP release keys (signed using 273DF287):
> http://www.apache.org/dist/syncope/KEYS
> 
> Vote will be open for 72 hours.
> 
> [ ] +1  approve
> [ ] +0  no opinion
> [ ] -1  disapprove (and reason why)

+1
BR,
Massi

> 
> Here's my +1
> 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,
> CXF Committer, OpenJPA Committer, PonyMail PPMC
> http://home.apache.org/~ilgrosso/

-- 
Massimiliano Perrone
Tel +39 393 9121310

Tirasa S.r.l.
Viale D'Annunzio 267 - 65127 Pescara
Tel +39 0859116307 / FAX +39 085973
http://www.tirasa.net

"L'apprendere molte cose non insegna l'intelligenza"
(Eraclito)


Re: [DISCUSS] Switching to UUID primary keys for users, groups and any objects

2016-04-04 Thread Massimiliano Perrone



Il 04/04/2016 10:23, Francesco Chicchiriccò ha scritto:

Hi all,
a recent e-mail on user@ [1] (about SCIM) made me reconsider one of 
the choices we've made in Syncope since the beginning, e.g. using 
table generators for long primary keys in several entities, and 
especially for users, groups and any objects (and maybe related as 
attributes, memberships and relationships).


It seems that UUID offers several advantages, compared to natural keys 
(as "long" we use for the aforementioned entities) [2][3][4].


There is some open source UUID generator around [5], which is reported 
to perform quite better than standard JDK's, and also features 
time-based generation, particularly useful in cluster scenarios.


Naturally, all this would mean changing some logic and data 
representation, hence a relevant impact on the codebase, but with 
considerable improvements in portability and performance.


It is my opinion, after a quick chat with Mark Struberg on #openjpa, 
that this change might worth the effort, and also that we can make it 
before finalizing 2.0.0.


I am going anyway to ask for details on users@openjpa.

WDYT?


It seems to be a good enhancement, my only doubt is only about the time. 
Do you think it's a good idea (I'm supposing that you know how much time 
you need to implement the feature) implementing it before the 2.0.0 release?


Regards,
Massi


Regards.

[1] 
http://syncope-user.1051894.n5.nabble.com/Get-list-of-Users-from-a-Syncope-Group-td5708406.html

[2] http://blog.codinghorror.com/primary-keys-ids-versus-guids/
[3] 
http://web.archive.org/web/20150511162734/http://databases.aspfaq.com/database/what-should-i-choose-for-my-primary-key.html
[4] 
http://blog.xebia.com/jpa-implementation-patterns-using-uuids-as-primary-keys/

[5] https://github.com/cowtowncoder/java-uuid-generator



--
Massimiliano Perrone
Tel +39 393 9121310

Tirasa S.r.l.
Viale D'Annunzio 267 - 65127 Pescara
Tel +39 0859116307 / FAX +39 085973
http://www.tirasa.net

"L'apprendere molte cose non insegna l'intelligenza"
(Eraclito)



Re: [VOTE] Apache Syncope 2.0.0-M2

2016-03-22 Thread Massimiliano Perrone



Il 22/03/2016 09:38, Marco Di Sabatino Di Diodoro ha scritto:



Il 21/03/2016 17:08, Francesco Chicchiriccò ha scritto:
I've created a 2.0.0-M2 release, with the following artifacts up for 
a vote:


GIT source tag (ee39bd3ee07617e150413523448299747de1d8f2):
https://git-wip-us.apache.org/repos/asf?p=syncope.git;a=tag;h=syncope-2.0.0-M2 



List of changes:
https://git-wip-us.apache.org/repos/asf?p=syncope.git;a=blob;f=CHANGES;h=6744cfd2fa001b28ea404e56779472eefc82fda6 



Staging artifacts:
https://dist.apache.org/repos/dist/dev/syncope/2.0.0-M2

Maven staging repo:
https://repository.apache.org/content/repositories/orgapachesyncope-1025/ 



Staging site:
http://syncope.apache.org/2.0.0-M2/

PGP release keys (signed using 273DF287):
http://www.apache.org/dist/syncope/KEYS

Vote will be open for 72 hours.

[ ] +1  approve
[ ] +0  no opinion
[ ] -1  disapprove (and reason why)


+1

Regards,
Massi


+1

Regards
Marco



Here's my +1
Regards.





--
Massimiliano Perrone
Tel +39 393 9121310

Tirasa S.r.l.
Viale D'Annunzio 267 - 65127 Pescara
Tel +39 0859116307 / FAX +39 085973
http://www.tirasa.net

"L'apprendere molte cose non insegna l'intelligenza"
(Eraclito)



Re: [DISCUSS] Update logo?

2016-01-27 Thread Massimiliano Perrone



Il 27/01/2016 17:26, Francesco Chicchiriccò ha scritto:

Hi all,
as you have probably noticed, today The ASF has announced [1] its new 
"visual identity", including a brand new feather logo [2].


Shall we want to update our project logo accordingly?

I have already received a proposal [3] from Daniel Gruno (in CC).

WDYT?


If the question is: Do you like it?
My answer is: no.

I prefer a "visible" treble clef with the horizontal feather.



Regards.

[1] 
https://blogs.apache.org/foundation/entry/the_apache_software_foundation_announces86

[2] http://apache.org/foundation/press/kit/#links
[3] http://rdo.fosslists.org/images/syncope.png



--
Massimiliano Perrone
Tel +39 393 9121310

Tirasa S.r.l.
Viale D'Annunzio 267 - 65127 Pescara
Tel +39 0859116307 / FAX +39 085973
http://www.tirasa.net

"L'apprendere molte cose non insegna l'intelligenza"
(Eraclito)



Re: [VOTE] Apache Syncope 1.2.7

2016-01-15 Thread Massimiliano Perrone



Il 15/01/2016 11:34, Francesco Chicchiriccò ha scritto:

I've created a 1.2.7 release, with the following artifacts up for a vote:

GIT source tag (5190ec100):
https://git-wip-us.apache.org/repos/asf?p=syncope.git;a=tag;h=5190ec100

List of changes:
https://git-wip-us.apache.org/repos/asf?p=syncope.git;a=blob;f=CHANGES;h=7d9964e5b820d37e929aafb2f45d7444920b4fea 



Staging artifacts:
https://dist.apache.org/repos/dist/dev/syncope/1.2.7

Maven staging repo:
https://repository.apache.org/content/repositories/orgapachesyncope-1024/

Staging site:
http://syncope.apache.org/1.2.7/

PGP release keys (signed using 273DF287):
http://www.apache.org/dist/syncope/KEYS

Vote will be open for 72 hours.

[ ] +1  approve
[ ] +0  no opinion
[ ] -1  disapprove (and reason why)


+1

--
Massimiliano Perrone
Tel +39 393 9121310

Tirasa S.r.l.
Viale D'Annunzio 267 - 65127 Pescara
Tel +39 0859116307 / FAX +39 085973
http://www.tirasa.net

"L'apprendere molte cose non insegna l'intelligenza"
(Eraclito)



Re: Add a link to send information about Syncope installation

2016-01-08 Thread Massimiliano Perrone



Il 22/12/2015 16:46, Francesco Chicchiriccò ha scritto:

On 22/12/2015 13:13, Fabio Martelli wrote:

Il 22/12/2015 12:57, Massimilino Perrone ha scritto:

Hi guys,
I'm sending this mail to share with you an idea to solve the problem 
to know who is using Syncope (and where) to create, for instance, an 
html page on the Syncope website with some reference to the Syncope 
installation around the world.


Basically the idea is to have a REST service (somewhere) where to 
send some anonymous information about the Syncope installation, the 
latter may be sent during the installation through the installer 
(adding a check box) or adding a link in the Info panel, on the 
Syncope console.


Recapping, I'm thinking two use cases:
UC 1) Check box on the installer.
Whether checked, after installation, the installer send "something" 
to the "famous" REST service.

UC 2) Link on the Info panel.
Whether clicked the console send "something" to the "famous" REST 
service.


For "something" I mean only the information as the location, system 
properties etc etc; in this way the information will be anonymous. 
But we could think also something more evolved, for instance a form 
with some *not* anonymous data as company, state, etc etc...


WDYT?

I suggest to have UC1 and 2 both available: UC1 seems to be simple 
and standard but we risky to miss installations performed in a 
different way.

BTW, from my personal point of view this is a great idea.


This looks definitely interesting, and I support Fabio with having 
both UC1 and UC2 available.


In case we agree to go on with this idea, I believe some tasks are 
needed:


 1. check with with comdev@ (or legal@ ?) if there is nothing bad in 
implementing such mechanism
 2. develop the server-side app (to be hosted in a dedicated branch of 
our GIT repo?)

 3. ask infra for a VM where to run this app


Can we keep on with the next step?
Regards,
Massi



Regards.



--
Massimiliano Perrone
Tel +39 393 9121310

Tirasa S.r.l.
Viale D'Annunzio 267 - 65127 Pescara
Tel +39 0859116307 / FAX +39 085973
http://www.tirasa.net

"L'apprendere molte cose non insegna l'intelligenza"
(Eraclito)



[jira] [Updated] (SYNCOPE-757) Problem updating multivalue Virtual Attributes

2016-01-08 Thread Massimiliano Perrone (JIRA)

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

Massimiliano Perrone updated SYNCOPE-757:
-
Affects Version/s: (was: 1.2.6)
Fix Version/s: (was: 1.2.7)

> Problem updating multivalue Virtual Attributes
> --
>
> Key: SYNCOPE-757
> URL: https://issues.apache.org/jira/browse/SYNCOPE-757
> Project: Syncope
>  Issue Type: Bug
>  Components: core
>    Reporter: Massimiliano Perrone
>    Assignee: Massimiliano Perrone
>
> Updating an user with multivalue Virtual Attribute the old values are 
> replaced by the new one also when we want to add the new values with the 
> older.



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


[jira] [Resolved] (SYNCOPE-757) Problem updating multivalue Virtual Attributes

2016-01-08 Thread Massimiliano Perrone (JIRA)

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

Massimiliano Perrone resolved SYNCOPE-757.
--
Resolution: Won't Fix

> Problem updating multivalue Virtual Attributes
> --
>
> Key: SYNCOPE-757
> URL: https://issues.apache.org/jira/browse/SYNCOPE-757
> Project: Syncope
>  Issue Type: Bug
>  Components: core
>    Reporter: Massimiliano Perrone
>    Assignee: Massimiliano Perrone
>
> Updating an user with multivalue Virtual Attribute the old values are 
> replaced by the new one also when we want to add the new values with the 
> older.



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


[jira] [Closed] (SYNCOPE-757) Problem updating multivalue Virtual Attributes

2016-01-08 Thread Massimiliano Perrone (JIRA)

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

Massimiliano Perrone closed SYNCOPE-757.


> Problem updating multivalue Virtual Attributes
> --
>
> Key: SYNCOPE-757
> URL: https://issues.apache.org/jira/browse/SYNCOPE-757
> Project: Syncope
>  Issue Type: Bug
>  Components: core
>    Reporter: Massimiliano Perrone
>    Assignee: Massimiliano Perrone
>
> Updating an user with multivalue Virtual Attribute the old values are 
> replaced by the new one also when we want to add the new values with the 
> older.



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


[jira] [Closed] (SYNCOPE-757) Problem updating multivalue Virtual Attributes

2016-01-08 Thread Massimiliano Perrone (JIRA)

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

Massimiliano Perrone closed SYNCOPE-757.

Resolution: Won't Fix

> Problem updating multivalue Virtual Attributes
> --
>
> Key: SYNCOPE-757
> URL: https://issues.apache.org/jira/browse/SYNCOPE-757
> Project: Syncope
>  Issue Type: Bug
>  Components: core
>Affects Versions: 1.2.6
>    Reporter: Massimiliano Perrone
>        Assignee: Massimiliano Perrone
>
> Updating an user with multivalue Virtual Attribute the old values are 
> replaced by the new one also when we want to add the new values with the 
> older.



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


[jira] [Reopened] (SYNCOPE-757) Problem updating multivalue Virtual Attributes

2016-01-08 Thread Massimiliano Perrone (JIRA)

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

Massimiliano Perrone reopened SYNCOPE-757:
--

> Problem updating multivalue Virtual Attributes
> --
>
> Key: SYNCOPE-757
> URL: https://issues.apache.org/jira/browse/SYNCOPE-757
> Project: Syncope
>  Issue Type: Bug
>  Components: core
>Affects Versions: 1.2.6
>    Reporter: Massimiliano Perrone
>        Assignee: Massimiliano Perrone
>
> Updating an user with multivalue Virtual Attribute the old values are 
> replaced by the new one also when we want to add the new values with the 
> older.



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


[jira] [Created] (SYNCOPE-757) Problem updating multivalue Virtual Attributes

2016-01-05 Thread Massimiliano Perrone (JIRA)
Massimiliano Perrone created SYNCOPE-757:


 Summary: Problem updating multivalue Virtual Attributes
 Key: SYNCOPE-757
 URL: https://issues.apache.org/jira/browse/SYNCOPE-757
 Project: Syncope
  Issue Type: Bug
  Components: core
Affects Versions: 2.0.0-M1, 1.2.6
Reporter: Massimiliano Perrone
Assignee: Massimiliano Perrone
 Fix For: 1.2.7, 2.0.0


Updating an user with multivalue Virtual Attribute the old values are replaced 
by the new one also when we want to add the new values with the older.



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


Re: [VOTE] Apache Syncope 2.0.0-M1

2015-12-23 Thread Massimiliano Perrone



Il 23/12/2015 09:22, Francesco Chicchiriccò ha scritto:
I've created a 2.0.0-M1 release, with the following artifacts up for a 
vote:


GIT source tag (46840df380a855d8a0dd827e8cb2db992f18134c):
https://git-wip-us.apache.org/repos/asf?p=syncope.git;a=tag;h=syncope-2.0.0-M1 



List of changes:
https://git-wip-us.apache.org/repos/asf?p=syncope.git;a=blob;f=CHANGES;h=7d9964e5b820d37e929aafb2f45d7444920b4fea;hb=851fead536bd5cf14499376ba1c4aeff24c1dc1d 



Staging artifacts:
https://dist.apache.org/repos/dist/dev/syncope/2.0.0-M1

Maven staging repo:
https://repository.apache.org/content/repositories/orgapachesyncope-1017/

Staging site:
http://syncope.apache.org/2.0.0-M1/

PGP release keys (signed using 273DF287):
http://www.apache.org/dist/syncope/KEYS

Vote will be open for 72 hours.


+1



[ ] +1  approve
[ ] +0  no opinion
[ ] -1  disapprove (and reason why)



--
Massimiliano Perrone
Tel +39 393 9121310

Tirasa S.r.l.
Viale D'Annunzio 267 - 65127 Pescara
Tel +39 0859116307 / FAX +39 085973
http://www.tirasa.net

"L'apprendere molte cose non insegna l'intelligenza"
(Eraclito)



[jira] [Closed] (SYNCOPE-213) Fail to buid 1.0.2 tag

2015-12-16 Thread Massimiliano Perrone (JIRA)

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

Massimiliano Perrone closed SYNCOPE-213.


> Fail to buid 1.0.2 tag
> --
>
> Key: SYNCOPE-213
> URL: https://issues.apache.org/jira/browse/SYNCOPE-213
> Project: Syncope
>  Issue Type: Bug
>Affects Versions: 1.0.1-incubating, 1.0.2-incubating
>Reporter: Emmanuel Lecharny
> Attachments: cargo-output.log, cargo.log, core-connid.log, 
> core-persistence.log, core-rest.log, core-test.log, core.log
>
>
> The build fails on :
> Running org.apache.syncope.core.rest.NotificationTestITCase
> Tests run: 6, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.44 sec <<< 
> FAILURE!
> Tested on OSX with Java 7, and also on Ubuntu, Java 6



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


[jira] [Resolved] (SYNCOPE-213) Fail to buid 1.0.2 tag

2015-12-16 Thread Massimiliano Perrone (JIRA)

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

Massimiliano Perrone resolved SYNCOPE-213.
--
Resolution: Won't Fix

> Fail to buid 1.0.2 tag
> --
>
> Key: SYNCOPE-213
> URL: https://issues.apache.org/jira/browse/SYNCOPE-213
> Project: Syncope
>  Issue Type: Bug
>Affects Versions: 1.0.1-incubating, 1.0.2-incubating
>Reporter: Emmanuel Lecharny
> Attachments: cargo-output.log, cargo.log, core-connid.log, 
> core-persistence.log, core-rest.log, core-test.log, core.log
>
>
> The build fails on :
> Running org.apache.syncope.core.rest.NotificationTestITCase
> Tests run: 6, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.44 sec <<< 
> FAILURE!
> Tested on OSX with Java 7, and also on Ubuntu, Java 6



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


[jira] [Resolved] (SYNCOPE-637) Let user choose extensions

2015-12-16 Thread Massimiliano Perrone (JIRA)

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

Massimiliano Perrone resolved SYNCOPE-637.
--
Resolution: Fixed

> Let user choose extensions
> --
>
> Key: SYNCOPE-637
> URL: https://issues.apache.org/jira/browse/SYNCOPE-637
> Project: Syncope
>  Issue Type: Improvement
>  Components: installer
>Reporter: Francesco Chicchiriccò
>    Assignee: Massimiliano Perrone
> Fix For: 2.0.0
>
>
> After SYNCOPE-620, the project generated by installer does not include 
> neither Activiti workflow adapter nor Camel-based provisioning manager, but 
> their respective "plain Java" counterparts.
> It should be possible to let user choose which workflow adapter and 
> provisioning manager to include.
> Moreover, the optional Swagger component can be chosen to be included or not,



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


[jira] [Assigned] (SYNCOPE-637) Let user choose workflow and provisioning implementations

2015-12-14 Thread Massimiliano Perrone (JIRA)

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

Massimiliano Perrone reassigned SYNCOPE-637:


Assignee: Massimiliano Perrone

> Let user choose workflow and provisioning implementations
> -
>
> Key: SYNCOPE-637
> URL: https://issues.apache.org/jira/browse/SYNCOPE-637
> Project: Syncope
>  Issue Type: Improvement
>  Components: installer
>Reporter: Francesco Chicchiriccò
>    Assignee: Massimiliano Perrone
> Fix For: 2.0.0
>
>
> After SYNCOPE-620, the project generated by installer does not include 
> neither Activiti workflow adapter nor Camel-based provisioning manager, but 
> their respective "plain Java" counterparts.
> It should be possible to let user choose which workflow adapter and 
> provisioning manager to include.



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


[jira] [Resolved] (SYNCOPE-722) CLI documentation

2015-12-14 Thread Massimiliano Perrone (JIRA)

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

Massimiliano Perrone resolved SYNCOPE-722.
--
Resolution: Fixed

> CLI documentation
> -
>
> Key: SYNCOPE-722
> URL: https://issues.apache.org/jira/browse/SYNCOPE-722
> Project: Syncope
>  Issue Type: Sub-task
>  Components: cli, documentation
>    Reporter: Massimiliano Perrone
>    Assignee: Massimiliano Perrone
> Fix For: 2.0.0
>
>
> Provide documentation about CLI component



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


[jira] [Resolved] (SYNCOPE-158) CLI admin tool

2015-12-14 Thread Massimiliano Perrone (JIRA)

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

Massimiliano Perrone resolved SYNCOPE-158.
--
Resolution: Fixed

> CLI admin tool
> --
>
> Key: SYNCOPE-158
> URL: https://issues.apache.org/jira/browse/SYNCOPE-158
> Project: Syncope
>  Issue Type: New Feature
>  Components: cli
>Reporter: Francesco Chicchiriccò
>    Assignee: Massimiliano Perrone
> Fix For: 2.0.0
>
>
> It should not be hard to make a simple command-line tool to get and set 
> SyncopeConf items (and more).



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


[jira] [Resolved] (SYNCOPE-741) Tasks page unusable when a task has thousand executions

2015-12-11 Thread Massimiliano Perrone (JIRA)

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

Massimiliano Perrone resolved SYNCOPE-741.
--
Resolution: Fixed

> Tasks page unusable when a task has thousand executions
> ---
>
> Key: SYNCOPE-741
> URL: https://issues.apache.org/jira/browse/SYNCOPE-741
> Project: Syncope
>  Issue Type: Bug
>  Components: console, core
>Affects Versions: 1.2.6, 2.0.0
>    Reporter: Massimiliano Perrone
>        Assignee: Massimiliano Perrone
> Fix For: 1.2.7, 2.0.0
>
>
> With an extremely high number of executions, reading a task (or listing 
> tasks) requires the core to build an handful of JSON / XML package to be 
> transferred to console.



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


[jira] [Created] (SYNCOPE-741) Tasks page unusable when a task has thousand executions

2015-12-09 Thread Massimiliano Perrone (JIRA)
Massimiliano Perrone created SYNCOPE-741:


 Summary: Tasks page unusable when a task has thousand executions
 Key: SYNCOPE-741
 URL: https://issues.apache.org/jira/browse/SYNCOPE-741
 Project: Syncope
  Issue Type: Bug
  Components: console
Affects Versions: 1.2.6, 2.0.0
Reporter: Massimiliano Perrone
Assignee: Massimiliano Perrone
 Fix For: 1.2.7, 2.0.0






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


[jira] [Commented] (SYNCOPE-722) CLI documentation

2015-12-01 Thread Massimiliano Perrone (JIRA)

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

Massimiliano Perrone commented on SYNCOPE-722:
--

[~coheigea] I just committed the last .adoc file of the CLI client 
documentation.

I know I have a bad english so, please, can you check my work?
Thanks and I owe you a beer :)

Massi




> CLI documentation
> -
>
> Key: SYNCOPE-722
> URL: https://issues.apache.org/jira/browse/SYNCOPE-722
> Project: Syncope
>  Issue Type: Sub-task
>  Components: cli, documentation
>    Reporter: Massimiliano Perrone
>    Assignee: Massimiliano Perrone
> Fix For: 2.0.0
>
>
> Provide documentation about CLI component



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


[jira] [Resolved] (SYNCOPE-727) Integration test

2015-11-23 Thread Massimiliano Perrone (JIRA)

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

Massimiliano Perrone resolved SYNCOPE-727.
--
Resolution: Fixed

> Integration test
> 
>
> Key: SYNCOPE-727
> URL: https://issues.apache.org/jira/browse/SYNCOPE-727
> Project: Syncope
>  Issue Type: Sub-task
>  Components: cli
>Affects Versions: 2.0.0
>    Reporter: Massimiliano Perrone
>        Assignee: Massimiliano Perrone
> Fix For: 2.0.0
>
>
> Develop the integretin tests for this module.



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


[jira] [Commented] (SYNCOPE-728) Delete all users

2015-11-17 Thread Massimiliano Perrone (JIRA)

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

Massimiliano Perrone commented on SYNCOPE-728:
--

[~ilgrosso] I'm following your suggestions.
>From linked documentation:
Rather then deleting all users, a restricting search condition can be used by 
replacing line 10 with:
final String fiql = 
SyncopeClient.getUserSearchConditionBuilder().is("id").lessThan(150).query();

Why less than 150? What's the id 150?

> Delete all users
> 
>
> Key: SYNCOPE-728
> URL: https://issues.apache.org/jira/browse/SYNCOPE-728
> Project: Syncope
>  Issue Type: Sub-task
>  Components: cli
>    Reporter: Massimiliano Perrone
>Assignee: Massimiliano Perrone
> Fix For: 2.0.0
>
>
> Create a method to delete all users.
> This method, after a new authentication, will delete all users managed by 
> Syncope. This, for instance, will be very helpful during test phase.



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


Re: [DISCUSS] Next release(s)

2015-11-11 Thread Massimiliano Perrone



Il 11/11/2015 09:11, Francesco Chicchiriccò ha scritto:

Hi all,
this discussion is triggered by some request recently received on 
user@ [1] but also about the ongoing development effort towards 2.0.0.


AFAICT, the current status can be summarized as follows:

 1. feature-wise, core is currently in a quite self-consistent state, 
even tough relevant new feature are ATM set to be implemented in 2.0.0 
(mainly SYNCOPE-699 / SYNCOPE-129 / SYNCOPE-534); naturally, there 
might be bugs, especially considering the great amount of additions 
compared to 1.2.X


 2. console is still under active development to reach usable state 
(remember we started it from scratch in 2.0.0) - Fabio and Marco are 
on it


 3. enduser is more or less in the same situation of console, possibly 
a bit more close to the end - Andrea is on it


 4. cli should be almost complete - Massimiliano is on it

 5. documentation is less than half-way: getting started needs to be 
adjusted with latest additions and reference guide is simply yet to be 
written - I am on it, but seeking for contributions, especially by 
native speakers - read Colm :-)


Given this overall situation, I would propose to:

 (i) keep pushing on 2, 3, 4 and 5 above
 (ii) fix on (1) on request
 (iii) as soon as 2 and 3 are in a presentable state, start thinking 
of milestone releases (2.0.0-M1, 2.0.0-M2, etc)


As far as I can see it, it would be really nice to cut 2.0.0-M1 before 
the end of year.


WDYT?


+1


Regards.

[1] http://markmail.org/message/ibcz7jx53su73dld



--
Massimiliano Perrone
Tel +39 393 9121310

Tirasa S.r.l.
Viale D'Annunzio 267 - 65127 Pescara
Tel +39 0859116307 / FAX +39 085973
http://www.tirasa.net

"L'apprendere molte cose non insegna l'intelligenza"
(Eraclito)



[jira] [Created] (SYNCOPE-727) Integration test

2015-11-09 Thread Massimiliano Perrone (JIRA)
Massimiliano Perrone created SYNCOPE-727:


 Summary: Integration test
 Key: SYNCOPE-727
 URL: https://issues.apache.org/jira/browse/SYNCOPE-727
 Project: Syncope
  Issue Type: Sub-task
  Components: cli
Affects Versions: 2.0.0
Reporter: Massimiliano Perrone
Assignee: Massimiliano Perrone
 Fix For: 2.0.0


Develop the integretin tests for this module.



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


[jira] [Created] (SYNCOPE-728) Delete all users

2015-11-09 Thread Massimiliano Perrone (JIRA)
Massimiliano Perrone created SYNCOPE-728:


 Summary: Delete all users
 Key: SYNCOPE-728
 URL: https://issues.apache.org/jira/browse/SYNCOPE-728
 Project: Syncope
  Issue Type: Sub-task
  Components: cli
Reporter: Massimiliano Perrone
Assignee: Massimiliano Perrone
 Fix For: 2.0.0


Create a method to delete all users.
This method, after a new authentication, will delete all users managed by 
Syncope. This, for instance, will be very helpful during test phase.



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


[jira] [Resolved] (SYNCOPE-723) Create bash script file to wrap java command

2015-11-08 Thread Massimiliano Perrone (JIRA)

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

Massimiliano Perrone resolved SYNCOPE-723.
--
Resolution: Fixed

> Create bash script file to wrap java command
> 
>
> Key: SYNCOPE-723
> URL: https://issues.apache.org/jira/browse/SYNCOPE-723
> Project: Syncope
>  Issue Type: Sub-task
>  Components: cli
>    Reporter: Massimiliano Perrone
>    Assignee: Massimiliano Perrone
> Fix For: 2.0.0
>
>
> At the moment the way to run the CLI is through the java -jar command.
> We need to create a bash script (at least) to execute the commands like a 
> real bash script command.



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


[jira] [Resolved] (SYNCOPE-724) create properties file as help messages

2015-11-08 Thread Massimiliano Perrone (JIRA)

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

Massimiliano Perrone resolved SYNCOPE-724.
--
Resolution: Fixed

> create properties file as help messages
> ---
>
> Key: SYNCOPE-724
> URL: https://issues.apache.org/jira/browse/SYNCOPE-724
> Project: Syncope
>  Issue Type: Sub-task
>  Components: cli
>    Reporter: Massimiliano Perrone
>    Assignee: Massimiliano Perrone
> Fix For: 2.0.0
>
>
> Create a property file to print the help message instead of the actual String 
> class attribute.



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


[jira] [Created] (SYNCOPE-724) create properties file as help messages

2015-11-06 Thread Massimiliano Perrone (JIRA)
Massimiliano Perrone created SYNCOPE-724:


 Summary: create properties file as help messages
 Key: SYNCOPE-724
 URL: https://issues.apache.org/jira/browse/SYNCOPE-724
 Project: Syncope
  Issue Type: Sub-task
  Components: cli
Reporter: Massimiliano Perrone
Assignee: Massimiliano Perrone
 Fix For: 2.0.0


Create a property file to print the help message instead of the actual String 
class attribute.



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


[jira] [Updated] (SYNCOPE-636) Include proper LICENSE & NOTICE in the dist artifact

2015-11-06 Thread Massimiliano Perrone (JIRA)

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

Massimiliano Perrone updated SYNCOPE-636:
-
Assignee: Francesco Chicchiriccò  (was: Massimiliano Perrone)

> Include proper LICENSE & NOTICE in the dist artifact
> 
>
> Key: SYNCOPE-636
> URL: https://issues.apache.org/jira/browse/SYNCOPE-636
> Project: Syncope
>  Issue Type: Sub-task
>  Components: cli
>Reporter: Francesco Chicchiriccò
>Assignee: Francesco Chicchiriccò
> Fix For: 2.0.0
>
>
> Include LICENSE and NOTICE in the dist artifact with content according to 
> packaged dependencies.



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


[jira] [Commented] (SYNCOPE-636) Include proper LICENSE & NOTICE in the dist artifact

2015-11-06 Thread Massimiliano Perrone (JIRA)

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

Massimiliano Perrone commented on SYNCOPE-636:
--

[~ilgrosso] Can you have a check?

> Include proper LICENSE & NOTICE in the dist artifact
> 
>
> Key: SYNCOPE-636
> URL: https://issues.apache.org/jira/browse/SYNCOPE-636
> Project: Syncope
>  Issue Type: Sub-task
>  Components: cli
>Reporter: Francesco Chicchiriccò
>Assignee: Francesco Chicchiriccò
> Fix For: 2.0.0
>
>
> Include LICENSE and NOTICE in the dist artifact with content according to 
> packaged dependencies.



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


Re: [VOTE] Apache Syncope 1.2.6

2015-11-05 Thread Massimiliano Perrone



Il 05/11/2015 16:19, Marco Di Sabatino Di Diodoro ha scritto:

Hi All,
I've created a 1.2.6 release, with the following artifacts up for a vote:

GIT source tag (b701329aa):
https://git-wip-us.apache.org/repos/asf?p=syncope.git;a=tag;h=b701329aa

List of changes:
https://git-wip-us.apache.org/repos/asf?p=syncope.git;a=blob;f=CHANGES;h=2fcc8941552c9748195e7e91b68ba8f1c06572d5;hb=ffd510a464803de2604843e33d996dd582b7ba0f 



Staging artifacts:
https://dist.apache.org/repos/dist/dev/syncope/1.2.6

Maven staging repo:
https://repository.apache.org/content/repositories/orgapachesyncope-1016

Staging site:
http://syncope.apache.org/1.2.6/

PGP release keys (signed using 293412BA):
http://www.apache.org/dist/syncope/KEYS

Vote will be open for 72 hours.

Kind regards,
M.

[ ] +1  approve
[ ] +0  no opinion
[ ] -1  disapprove (and reason why)



+1

--
Massimiliano Perrone
Tel +39 393 9121310

Tirasa S.r.l.
Viale D'Annunzio 267 - 65127 Pescara
Tel +39 0859116307 / FAX +39 085973
http://www.tirasa.net

"L'apprendere molte cose non insegna l'intelligenza"
(Eraclito)



[jira] [Updated] (SYNCOPE-723) Create bash script file to wrap java command

2015-11-05 Thread Massimiliano Perrone (JIRA)

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

Massimiliano Perrone updated SYNCOPE-723:
-
Issue Type: Sub-task  (was: Improvement)
Parent: SYNCOPE-158

> Create bash script file to wrap java command
> 
>
> Key: SYNCOPE-723
> URL: https://issues.apache.org/jira/browse/SYNCOPE-723
> Project: Syncope
>  Issue Type: Sub-task
>  Components: cli
>    Reporter: Massimiliano Perrone
>    Assignee: Massimiliano Perrone
> Fix For: 2.0.0
>
>
> At the moment the way to run the CLI is through the java -jar command.
> We need to create a bash script (at least) to execute the commands like a 
> real bash script command.



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


[jira] [Created] (SYNCOPE-723) Create bash script file to wrap java command

2015-11-04 Thread Massimiliano Perrone (JIRA)
Massimiliano Perrone created SYNCOPE-723:


 Summary: Create bash script file to wrap java command
 Key: SYNCOPE-723
 URL: https://issues.apache.org/jira/browse/SYNCOPE-723
 Project: Syncope
  Issue Type: Improvement
  Components: cli
Reporter: Massimiliano Perrone
Assignee: Massimiliano Perrone
 Fix For: 2.0.0


At the moment the way to run the CLI is through the java -jar command.
We need to create a bash script (at least) to execute the commands like a real 
bash script command.



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


[jira] [Closed] (SYNCOPE-593) Add user self services to command line interface

2015-10-28 Thread Massimiliano Perrone (JIRA)

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

Massimiliano Perrone closed SYNCOPE-593.

Resolution: Invalid

> Add user self services to command line interface
> 
>
> Key: SYNCOPE-593
> URL: https://issues.apache.org/jira/browse/SYNCOPE-593
> Project: Syncope
>  Issue Type: Sub-task
>    Reporter: Massimiliano Perrone
>    Assignee: Massimiliano Perrone
> Fix For: 2.0.0
>
>
> Add user self services to command line interface



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


[jira] [Closed] (SYNCOPE-594) Add user workflow services to command line interface

2015-10-28 Thread Massimiliano Perrone (JIRA)

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

Massimiliano Perrone closed SYNCOPE-594.

Resolution: Won't Fix

> Add user workflow services to command line interface
> 
>
> Key: SYNCOPE-594
> URL: https://issues.apache.org/jira/browse/SYNCOPE-594
> Project: Syncope
>  Issue Type: Sub-task
>    Reporter: Massimiliano Perrone
>    Assignee: Massimiliano Perrone
> Fix For: 2.0.0
>
>
> Add user workflow services to command line interface



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


[jira] [Resolved] (SYNCOPE-580) Add user services to command line interface

2015-10-28 Thread Massimiliano Perrone (JIRA)

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

Massimiliano Perrone resolved SYNCOPE-580.
--
Resolution: Fixed

> Add user services to command line interface
> ---
>
> Key: SYNCOPE-580
> URL: https://issues.apache.org/jira/browse/SYNCOPE-580
> Project: Syncope
>  Issue Type: Sub-task
>  Components: cli
>    Reporter: Massimiliano Perrone
>    Assignee: Massimiliano Perrone
> Fix For: 2.0.0
>
>
> Add user services to command line interface



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


Re: wrong exception in SecurityQuestion service?

2015-10-28 Thread Massimiliano Perrone



Il 28/10/2015 15:01, Francesco Chicchiriccò ha scritto:

On 28/10/2015 11:38, Massimiliano Perrone wrote:

Hi Syncopers,
running securityQuestionService.readByUser(username) method from 
org.apache.syncope.common.rest.api.service.SecurityQuestionService I 
get a wrong exception, I'm supposing..


From the log header the URL called is, for instance, 
http://localhost:9080/syncope/rest/securityQuestions/byUser/rossini 
and, if I tried to run it from the web browser it works because the 
response is:


[jira] [Resolved] (SYNCOPE-595) Add workflow services to command line interface

2015-10-28 Thread Massimiliano Perrone (JIRA)

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

Massimiliano Perrone resolved SYNCOPE-595.
--
Resolution: Fixed

> Add workflow services to command line interface
> ---
>
> Key: SYNCOPE-595
> URL: https://issues.apache.org/jira/browse/SYNCOPE-595
> Project: Syncope
>  Issue Type: Sub-task
>    Reporter: Massimiliano Perrone
>    Assignee: Massimiliano Perrone
> Fix For: 2.0.0
>
>
> Add workflow services to command line interface



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


[jira] [Resolved] (SYNCOPE-591) Add security question services to command line interface

2015-10-28 Thread Massimiliano Perrone (JIRA)

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

Massimiliano Perrone resolved SYNCOPE-591.
--
Resolution: Fixed

> Add security question services to command line interface
> 
>
> Key: SYNCOPE-591
> URL: https://issues.apache.org/jira/browse/SYNCOPE-591
> Project: Syncope
>  Issue Type: Sub-task
>    Reporter: Massimiliano Perrone
>    Assignee: Massimiliano Perrone
> Fix For: 2.0.0
>
>
> Add security question services to command line interface



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


[jira] [Resolved] (SYNCOPE-583) Add entitlement services to command line interface

2015-10-28 Thread Massimiliano Perrone (JIRA)

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

Massimiliano Perrone resolved SYNCOPE-583.
--
Resolution: Fixed

> Add entitlement services to command line interface
> --
>
> Key: SYNCOPE-583
> URL: https://issues.apache.org/jira/browse/SYNCOPE-583
> Project: Syncope
>  Issue Type: Sub-task
>    Reporter: Massimiliano Perrone
>    Assignee: Massimiliano Perrone
> Fix For: 2.0.0
>
>




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


[jira] [Resolved] (SYNCOPE-589) Add role services to command line interface

2015-10-28 Thread Massimiliano Perrone (JIRA)

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

Massimiliano Perrone resolved SYNCOPE-589.
--
Resolution: Fixed

> Add role services to command line interface
> ---
>
> Key: SYNCOPE-589
> URL: https://issues.apache.org/jira/browse/SYNCOPE-589
> Project: Syncope
>  Issue Type: Sub-task
>    Reporter: Massimiliano Perrone
>    Assignee: Massimiliano Perrone
> Fix For: 2.0.0
>
>
> Add role services to command line interface



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


wrong exception in SecurityQuestion service

2015-10-28 Thread Massimiliano Perrone

Hi Syncopers,
running securityQuestionService.readByUser(username) method from 
org.apache.syncope.common.rest.api.service.SecurityQuestionService I get 
a wrong exception, I'm supposing..


From the log header the URL called is, for instance, 
http://localhost:9080/syncope/rest/securityQuestions/byUser/rossini and, 
if I tried to run it from the web browser it works because the response is:


Curiosity on UserService response

2015-10-26 Thread Massimiliano Perrone

Good morning Syncopers,
working with org.apache.syncope.common.rest.api.service.UserService 
interface I had a doubt about the response parameter of some methods.


For instance, the two methods [1] and [2] returns a Response object as 
response, why not the respective username or long id value?
Also because, to get the requested information, I need to take it from 
the header of the response (see [3] or [4]).


regards,
Massi

[1] Response getUsername(@NotNull @PathParam("key") Long key);
[2] Response getUserKey(@NotNull @PathParam("username") String username);

[3] 
userService.getUsername(Long.valueOf(input.firstParameter())).getHeaderString(RESTHeaders.USERNAME)
[4] 
userService.getUserKey(input.firstParameter()).getHeaderString(RESTHeaders.USER_KEY);


--
Massimiliano Perrone
Tel +39 393 9121310

Tirasa S.r.l.
Viale D'Annunzio 267 - 65127 Pescara
Tel +39 0859116307 / FAX +39 085973
http://www.tirasa.net

"L'apprendere molte cose non insegna l'intelligenza"
(Eraclito)



Re: Curiosity on UserService response

2015-10-26 Thread Massimiliano Perrone



Il 26/10/2015 14:02, Francesco Chicchiriccò ha scritto:

On 26/10/2015 13:20, Massimiliano Perrone wrote:

Good morning Syncopers,
working with org.apache.syncope.common.rest.api.service.UserService 
interface I had a doubt about the response parameter of some methods.


For instance, the two methods [1] and [2] returns a Response object 
as response, why not the respective username or long id value?
Also because, to get the requested information, I need to take it 
from the header of the response (see [3] or [4]).


There was a discussion about this specific point at the time that we 
migrated to CXF / JAX RS 2.0, you should be able to find it in the 
archives.


The technical point is that JAX RS methods cannot return plain values 
(long, string, ..) since JAXB always require some wrapping - and we 
need JAXB in order to deal with both JSON and XML payloads transparently.


The best-practice rationale is that the two operations mentioned above 
were more logically mapped to HTTP OPTIONS rather than complete GET.


Many thanks for the explanation.

Massi



Regards.


[1] Response getUsername(@NotNull @PathParam("key") Long key);
[2] Response getUserKey(@NotNull @PathParam("username") String 
username);
[3] 
userService.getUsername(Long.valueOf(input.firstParameter())).getHeaderString(RESTHeaders.USERNAME)
[4] 
userService.getUserKey(input.firstParameter()).getHeaderString(RESTHeaders.USER_KEY);




--
Massimiliano Perrone
Tel +39 393 9121310

Tirasa S.r.l.
Viale D'Annunzio 267 - 65127 Pescara
Tel +39 0859116307 / FAX +39 085973
http://www.tirasa.net

"L'apprendere molte cose non insegna l'intelligenza"
(Eraclito)



[jira] [Resolved] (SYNCOPE-582) Add connector services to command line interface

2015-10-23 Thread Massimiliano Perrone (JIRA)

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

Massimiliano Perrone resolved SYNCOPE-582.
--
Resolution: Fixed

> Add connector services to command line interface
> 
>
> Key: SYNCOPE-582
> URL: https://issues.apache.org/jira/browse/SYNCOPE-582
> Project: Syncope
>  Issue Type: Sub-task
>    Reporter: Massimiliano Perrone
>    Assignee: Massimiliano Perrone
> Fix For: 2.0.0
>
>
> Add connector services to command line interface



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


[jira] [Resolved] (SYNCOPE-588) Add resource services to command line interface

2015-10-23 Thread Massimiliano Perrone (JIRA)

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

Massimiliano Perrone resolved SYNCOPE-588.
--
Resolution: Fixed

> Add resource services to command line interface
> ---
>
> Key: SYNCOPE-588
> URL: https://issues.apache.org/jira/browse/SYNCOPE-588
> Project: Syncope
>  Issue Type: Sub-task
>    Reporter: Massimiliano Perrone
>    Assignee: Massimiliano Perrone
> Fix For: 2.0.0
>
>
> Add resource services to command line interface



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


[jira] [Created] (SYNCOPE-713) Remove ConfTO object from ConfigurationService

2015-10-21 Thread Massimiliano Perrone (JIRA)
Massimiliano Perrone created SYNCOPE-713:


 Summary: Remove ConfTO object from ConfigurationService
 Key: SYNCOPE-713
 URL: https://issues.apache.org/jira/browse/SYNCOPE-713
 Project: Syncope
  Issue Type: Improvement
  Components: common, core
Affects Versions: 2.0.0
Reporter: Massimiliano Perrone
Assignee: Massimiliano Perrone
 Fix For: 2.0.0


Remove ConfTO object in order to change
ConfTO list()
into
List list()
in ConfigurationService (and then in ConfigurationServiceImpl and 
ConfigurationLogic / ConfigurationDataBinder) accordingly. 



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


[jira] [Resolved] (SYNCOPE-713) Remove ConfTO object from ConfigurationService

2015-10-21 Thread Massimiliano Perrone (JIRA)

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

Massimiliano Perrone resolved SYNCOPE-713.
--
Resolution: Fixed

> Remove ConfTO object from ConfigurationService
> --
>
> Key: SYNCOPE-713
> URL: https://issues.apache.org/jira/browse/SYNCOPE-713
> Project: Syncope
>  Issue Type: Improvement
>  Components: common, core
>Affects Versions: 2.0.0
>    Reporter: Massimiliano Perrone
>        Assignee: Massimiliano Perrone
> Fix For: 2.0.0
>
>
> Remove ConfTO object in order to change
> ConfTO list()
> into
> List list()
> in ConfigurationService (and then in ConfigurationServiceImpl and 
> ConfigurationLogic / ConfigurationDataBinder) accordingly. 



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


[VOTE] Quick question about error message in CLI

2015-10-20 Thread Massimiliano Perrone

Ehi guys,
I need your help because I'm not convinced about the error message. I 
need to choice from:


1) attached file 1.png;
2) attached file 2.png;
3) a simple sentence: - Logger net.tirasa doesn't exist.

Remember that the "normal" output should be something like the content 
of the third attached file: list.png.


Massi

--
Massimiliano Perrone
Tel +39 393 9121310

Tirasa S.r.l.
Viale D'Annunzio 267 - 65127 Pescara
Tel +39 0859116307 / FAX +39 085973
http://www.tirasa.net

"L'apprendere molte cose non insegna l'intelligenza"
(Eraclito)



Re: [VOTE] Quick question about error message in CLI

2015-10-20 Thread Massimiliano Perrone



Il 20/10/2015 16:29, Francesco Chicchiriccò ha scritto:

On 20/10/2015 16:27, Massimiliano Perrone wrote:

Ehi guys,
I need your help because I'm not convinced about the error message. I 
need to choice from:


1) attached file 1.png;
2) attached file 2.png;
3) a simple sentence: - Logger net.tirasa doesn't exist.

Remember that the "normal" output should be something like the 
content of the third attached file: list.png.


Attachments are stripped out by ML: could you post them somewhere?



1) http://postimg.org/image/8h7o1afj5/
2) http://postimg.org/image/67sqi0lcx/
3) a simple sentence: - Logger net.tirasa doesn't exist.

info output: http://postimg.org/image/vr27fex61/

Massi

PS: sorry for the inconvenience

--
Massimiliano Perrone
Tel +39 393 9121310

Tirasa S.r.l.
Viale D'Annunzio 267 - 65127 Pescara
Tel +39 0859116307 / FAX +39 085973
http://www.tirasa.net

"L'apprendere molte cose non insegna l'intelligenza"
(Eraclito)



Re: [VOTE] Quick question about error message in CLI

2015-10-20 Thread Massimiliano Perrone



Il 20/10/2015 17:30, Marco Di Sabatino Di Diodoro ha scritto:



Il 20/10/2015 16:34, Massimiliano Perrone ha scritto:



Il 20/10/2015 16:29, Francesco Chicchiriccò ha scritto:

On 20/10/2015 16:27, Massimiliano Perrone wrote:

Ehi guys,
I need your help because I'm not convinced about the error message. 
I need to choice from:


1) attached file 1.png;
2) attached file 2.png;
3) a simple sentence: - Logger net.tirasa doesn't exist.

Remember that the "normal" output should be something like the 
content of the third attached file: list.png.


Attachments are stripped out by ML: could you post them somewhere?



1) http://postimg.org/image/8h7o1afj5/
2) http://postimg.org/image/67sqi0lcx/
3) a simple sentence: - Logger net.tirasa doesn't exist.

info output: http://postimg.org/image/vr27fex61/

Massi

PS: sorry for the inconvenience


The third option it's fine


Ok, third option implemented...



M



--
Massimiliano Perrone
Tel +39 393 9121310

Tirasa S.r.l.
Viale D'Annunzio 267 - 65127 Pescara
Tel +39 0859116307 / FAX +39 085973
http://www.tirasa.net

"L'apprendere molte cose non insegna l'intelligenza"
(Eraclito)



Prevent "merge commit"

2015-10-20 Thread Massimiliano Perrone

Hi Syncopers,
maybe this mail could be useful at all.

Few minutes ago Francesco committed just few seconds before my commit. 
In this way I got a merge commit. The latter means an empty commit in 
our "commits history".


To prevent this situation Francesco suggested me to config the Git 
repository running "git config branch.master.rebase true" from Syncope 
base directory. In this way the repository is configured to have an 
automatic rebase running the git pull command.


Massi

--
Massimiliano Perrone
Tel +39 393 9121310

Tirasa S.r.l.
Viale D'Annunzio 267 - 65127 Pescara
Tel +39 0859116307 / FAX +39 085973
http://www.tirasa.net

"L'apprendere molte cose non insegna l'intelligenza"
(Eraclito)



About configuration service

2015-10-19 Thread Massimiliano Perrone

Hi all,
some questions about 
org.apache.syncope.common.rest.api.service.ConfigurationService and the 
"configuration stack".


1) Why ConfigurationService has a method called list when this method 
return a ConfTO object?
   1.1) Why not a get() for list() and a read(String schema) for 
get(String schema)?


2) Why the "configuration stack" is like the others when JPAConf manage 
only CPlainAttr? The most of those methods are unnecessary and misleading.


This questions because I'm using the Syncope common library to develop 
and the configuration service doesn't seem to be intuitive.


I hope I was clear enough.

Massimliano

--
Massimiliano Perrone
Tel +39 393 9121310

Tirasa S.r.l.
Viale D'Annunzio 267 - 65127 Pescara
Tel +39 0859116307 / FAX +39 085973
http://www.tirasa.net

"L'apprendere molte cose non insegna l'intelligenza"
(Eraclito)



[jira] [Created] (SYNCOPE-711) Add domain services to command line interface

2015-10-15 Thread Massimiliano Perrone (JIRA)
Massimiliano Perrone created SYNCOPE-711:


 Summary: Add domain services to command line interface
 Key: SYNCOPE-711
 URL: https://issues.apache.org/jira/browse/SYNCOPE-711
 Project: Syncope
  Issue Type: Sub-task
  Components: cli
Reporter: Massimiliano Perrone
Assignee: Massimiliano Perrone
 Fix For: 2.0.0






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


[jira] [Resolved] (SYNCOPE-711) Add domain services to command line interface

2015-10-15 Thread Massimiliano Perrone (JIRA)

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

Massimiliano Perrone resolved SYNCOPE-711.
--
Resolution: Fixed

> Add domain services to command line interface
> -
>
> Key: SYNCOPE-711
> URL: https://issues.apache.org/jira/browse/SYNCOPE-711
> Project: Syncope
>  Issue Type: Sub-task
>  Components: cli
>    Reporter: Massimiliano Perrone
>    Assignee: Massimiliano Perrone
> Fix For: 2.0.0
>
>




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


[jira] [Resolved] (SYNCOPE-592) Add task services to command line interface

2015-10-15 Thread Massimiliano Perrone (JIRA)

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

Massimiliano Perrone resolved SYNCOPE-592.
--
Resolution: Fixed

> Add task services to command line interface
> ---
>
> Key: SYNCOPE-592
> URL: https://issues.apache.org/jira/browse/SYNCOPE-592
> Project: Syncope
>  Issue Type: Sub-task
>    Reporter: Massimiliano Perrone
>    Assignee: Massimiliano Perrone
> Fix For: 2.0.0
>
>
> Add task services to command line interface



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


[jira] [Resolved] (SYNCOPE-584) Add logger services to command line interface

2015-10-14 Thread Massimiliano Perrone (JIRA)

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

Massimiliano Perrone resolved SYNCOPE-584.
--
Resolution: Fixed

> Add logger services to command line interface
> -
>
> Key: SYNCOPE-584
> URL: https://issues.apache.org/jira/browse/SYNCOPE-584
> Project: Syncope
>  Issue Type: Sub-task
>    Reporter: Massimiliano Perrone
>    Assignee: Massimiliano Perrone
> Fix For: 2.0.0
>
>
> Add logger services to command line interface



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


[jira] [Resolved] (SYNCOPE-581) Add configuration services to command line interface

2015-10-14 Thread Massimiliano Perrone (JIRA)

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

Massimiliano Perrone resolved SYNCOPE-581.
--
Resolution: Fixed

> Add configuration services to command line interface
> 
>
> Key: SYNCOPE-581
> URL: https://issues.apache.org/jira/browse/SYNCOPE-581
> Project: Syncope
>  Issue Type: Sub-task
>    Reporter: Massimiliano Perrone
>    Assignee: Massimiliano Perrone
> Fix For: 2.0.0
>
>
> Add configuration services to command line interface



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


[jira] [Resolved] (SYNCOPE-590) Add schema services to command line interface

2015-10-14 Thread Massimiliano Perrone (JIRA)

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

Massimiliano Perrone resolved SYNCOPE-590.
--
Resolution: Fixed

> Add schema services to command line interface
> -
>
> Key: SYNCOPE-590
> URL: https://issues.apache.org/jira/browse/SYNCOPE-590
> Project: Syncope
>  Issue Type: Sub-task
>    Reporter: Massimiliano Perrone
>    Assignee: Massimiliano Perrone
> Fix For: 2.0.0
>
>
> Add schema services to command line interface



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


[jira] [Resolved] (SYNCOPE-587) Add report services to command line interface

2015-10-14 Thread Massimiliano Perrone (JIRA)

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

Massimiliano Perrone resolved SYNCOPE-587.
--
Resolution: Fixed

> Add report services to command line interface
> -
>
> Key: SYNCOPE-587
> URL: https://issues.apache.org/jira/browse/SYNCOPE-587
> Project: Syncope
>  Issue Type: Sub-task
>    Reporter: Massimiliano Perrone
>    Assignee: Massimiliano Perrone
> Fix For: 2.0.0
>
>
> Add report services to command line interface



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


[jira] [Resolved] (SYNCOPE-585) Add notification services to command line interface

2015-10-14 Thread Massimiliano Perrone (JIRA)

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

Massimiliano Perrone resolved SYNCOPE-585.
--
Resolution: Fixed

> Add notification services to command line interface
> ---
>
> Key: SYNCOPE-585
> URL: https://issues.apache.org/jira/browse/SYNCOPE-585
> Project: Syncope
>  Issue Type: Sub-task
>    Reporter: Massimiliano Perrone
>    Assignee: Massimiliano Perrone
> Fix For: 2.0.0
>
>
> Add notification services to command line interface



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


[jira] [Resolved] (SYNCOPE-586) Add policy services to command line interface

2015-10-14 Thread Massimiliano Perrone (JIRA)

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

Massimiliano Perrone resolved SYNCOPE-586.
--
Resolution: Fixed

> Add policy services to command line interface
> -
>
> Key: SYNCOPE-586
> URL: https://issues.apache.org/jira/browse/SYNCOPE-586
> Project: Syncope
>  Issue Type: Sub-task
>    Reporter: Massimiliano Perrone
>    Assignee: Massimiliano Perrone
> Fix For: 2.0.0
>
>
> Add policy services to command line interface



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


ConfigurationLogic behavior

2015-10-13 Thread Massimiliano Perrone

Hi all,
I found this "strange" behavior working with ConfigurationService class.

When I try to delete a configuration I get always a valid response also 
when the configuration key doesn't exist (while I was expecting a 
NotFound error).
Reading the code I found below difference from (1) ConfigurationLogic 
and, for instance, (2) SchemaLogic classes:


(1)
@PreAuthorize("hasRole('" + Entitlement.CONFIGURATION_DELETE + "')")
public void delete(final String schema) {
confDAO.delete(schema);
}

(2)
@PreAuthorize("hasRole('" + Entitlement.SCHEMA_DELETE + "')")
public void delete(final SchemaType schemaType, final String 
schemaName) {

if (!doesSchemaExist(schemaType, schemaName)) {
throw new NotFoundException(schemaType + "/" + schemaName);
}

switch (schemaType) {
case VIRTUAL:
virSchemaDAO.delete(schemaName);
break;

case DERIVED:
derSchemaDAO.delete(schemaName);
break;

case PLAIN:
default:
plainSchemaDAO.delete(schemaName);
}
}

As you can read the second class has a control on schema existence, the 
first one hasn't.

It is the right behavior?

Massi

--
Massimiliano Perrone
Tel +39 393 9121310

Tirasa S.r.l.
Viale D'Annunzio 267 - 65127 Pescara
Tel +39 0859116307 / FAX +39 085973
http://www.tirasa.net

"L'apprendere molte cose non insegna l'intelligenza"
(Eraclito)



  1   2   3   >