[jira] [Commented] (SYNCOPE-700) Documentation artifacts
[
https://issues.apache.org/jira/browse/SYNCOPE-700?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15435054#comment-15435054
]
ASF subversion and git services commented on SYNCOPE-700:
-
Commit c4587cfdffecd88e7da3449192f47b8e457e61c5 in syncope's branch
refs/heads/master from [~ilgrosso]
[ https://git-wip-us.apache.org/repos/asf?p=syncope.git;h=c4587cf ]
[SYNCOPE-700] Working with admin console
> Documentation artifacts
> ---
>
> Key: SYNCOPE-700
> URL: https://issues.apache.org/jira/browse/SYNCOPE-700
> Project: Syncope
> Issue Type: Improvement
> Components: documentation
>Reporter: Francesco Chicchiriccò
>Assignee: Francesco Chicchiriccò
> Fix For: 2.0.0-M5
>
>
> As [discussed|http://markmail.org/message/dpleneuzrfcsmq2r] in mailing list,
> setup the {{asciidoctor-maven-plugin}} in order to generate, alongside with
> the build, the project documentation in HTML and PDF.
> The generated documentation will then be part of release artifacts and always
> up-to-date with current release.
> Preliminary results available at
> http://syncope.apache.org/2.0.0-SNAPSHOT/docs/
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (SYNCOPE-700) Documentation artifacts
[
https://issues.apache.org/jira/browse/SYNCOPE-700?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15435053#comment-15435053
]
ASF subversion and git services commented on SYNCOPE-700:
-
Commit dcfbf6f0efaf06f74e063f2d0007c747c50c129f in syncope's branch
refs/heads/master from [~ilgrosso]
[ https://git-wip-us.apache.org/repos/asf?p=syncope.git;h=dcfbf6f ]
[SYNCOPE-700] Extensions
> Documentation artifacts
> ---
>
> Key: SYNCOPE-700
> URL: https://issues.apache.org/jira/browse/SYNCOPE-700
> Project: Syncope
> Issue Type: Improvement
> Components: documentation
>Reporter: Francesco Chicchiriccò
>Assignee: Francesco Chicchiriccò
> Fix For: 2.0.0-M5
>
>
> As [discussed|http://markmail.org/message/dpleneuzrfcsmq2r] in mailing list,
> setup the {{asciidoctor-maven-plugin}} in order to generate, alongside with
> the build, the project documentation in HTML and PDF.
> The generated documentation will then be part of release artifacts and always
> up-to-date with current release.
> Preliminary results available at
> http://syncope.apache.org/2.0.0-SNAPSHOT/docs/
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
Re: [DISCUSS] Next releases
Sounds good to me, I'll restart looking at the documentation. Colm. On Wed, Aug 24, 2016 at 9:03 AM, Massimiliano Perrone < massimiliano.perr...@tirasa.net> wrote: > > + 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/ > > > -- Colm O hEigeartaigh Talend Community Coder http://coders.talend.com
[jira] [Resolved] (SYNCOPE-925) Allow domain selection from Swagger UI
[
https://issues.apache.org/jira/browse/SYNCOPE-925?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Francesco Chicchiriccò resolved SYNCOPE-925.
Resolution: Fixed
> Allow domain selection from Swagger UI
> --
>
> Key: SYNCOPE-925
> URL: https://issues.apache.org/jira/browse/SYNCOPE-925
> Project: Syncope
> Issue Type: Improvement
> Components: extensions
>Reporter: Francesco Chicchiriccò
>Assignee: Francesco Chicchiriccò
> Fix For: 2.0.0
>
>
> Currently it is not possible to select one of defined domains (hence
> {{Master}} is assumed) when performing any of the REST calls via Swagger UI.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (SYNCOPE-925) Allow domain selection from Swagger UI
[
https://issues.apache.org/jira/browse/SYNCOPE-925?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15434720#comment-15434720
]
ASF subversion and git services commented on SYNCOPE-925:
-
Commit 39f7f7ebff132173d5ca6ff6ec5e7692327524dc in syncope's branch
refs/heads/master from [~ilgrosso]
[ https://git-wip-us.apache.org/repos/asf?p=syncope.git;h=39f7f7e ]
[SYNCOPE-925] Extending CXF's Swagger2Feature on purpose
> Allow domain selection from Swagger UI
> --
>
> Key: SYNCOPE-925
> URL: https://issues.apache.org/jira/browse/SYNCOPE-925
> Project: Syncope
> Issue Type: Improvement
> Components: extensions
>Reporter: Francesco Chicchiriccò
>Assignee: Francesco Chicchiriccò
> Fix For: 2.0.0
>
>
> Currently it is not possible to select one of defined domains (hence
> {{Master}} is assumed) when performing any of the REST calls via Swagger UI.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (SYNCOPE-925) Allow domain selection from Swagger UI
Francesco Chicchiriccò created SYNCOPE-925:
--
Summary: Allow domain selection from Swagger UI
Key: SYNCOPE-925
URL: https://issues.apache.org/jira/browse/SYNCOPE-925
Project: Syncope
Issue Type: Improvement
Components: extensions
Reporter: Francesco Chicchiriccò
Assignee: Francesco Chicchiriccò
Fix For: 2.0.0
Currently it is not possible to select one of defined domains (hence {{Master}}
is assumed) when performing any of the REST calls via Swagger UI.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
Re: [DISCUSS] Next releases
+ 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/ >
[DISCUSS] Next releases
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/
[jira] [Commented] (SYNCOPE-880) Identity Recertification
[ https://issues.apache.org/jira/browse/SYNCOPE-880?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15434392#comment-15434392 ] ASF GitHub Bot commented on SYNCOPE-880: Github user ilgrosso commented on a diff in the pull request: https://github.com/apache/syncope/pull/26#discussion_r76007411 --- Diff: pom.xml --- @@ -197,6 +197,16 @@ under the License. http://people.apache.org/~anzelld/ + anzelld + Nicola Scendoni + The Apache Software Foundation + http://www.apache.org/ + +committer + + http://people.apache.org/~anzelld/ --- End diff -- ...guess you'll need to change `anzelld` with your own ASF id, right? > Identity Recertification > > > Key: SYNCOPE-880 > URL: https://issues.apache.org/jira/browse/SYNCOPE-880 > Project: Syncope > Issue Type: New Feature > Components: core >Reporter: Nicola Scendoni >Assignee: Nicola Scendoni >Priority: Minor > Fix For: 2.0.0 > > > Identify Re-certification is required for many national and international > standards like SOX, GxP, etc. > The idea is to implement one scheduled task that filter users basing on some > attributes (example: last recertification date, role,...) and move then on > one state "to be certified" and assign one task to some group that has the > responsibility to recertified the user, or delete it from the system. > Some report should report evidence about when the users have been recertified > and who was the certifier. > > This feature would be also the starting point to create account, role and > groups re-certifications. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (SYNCOPE-880) Identity Recertification
[ https://issues.apache.org/jira/browse/SYNCOPE-880?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15434391#comment-15434391 ] ASF GitHub Bot commented on SYNCOPE-880: Github user ilgrosso commented on a diff in the pull request: https://github.com/apache/syncope/pull/26#discussion_r76007392 --- Diff: pom.xml --- @@ -197,6 +197,16 @@ under the License. http://people.apache.org/~anzelld/ + anzelld --- End diff -- ...guess you'll need to change `anzelld` with your own ASF id, right? > Identity Recertification > > > Key: SYNCOPE-880 > URL: https://issues.apache.org/jira/browse/SYNCOPE-880 > Project: Syncope > Issue Type: New Feature > Components: core >Reporter: Nicola Scendoni >Assignee: Nicola Scendoni >Priority: Minor > Fix For: 2.0.0 > > > Identify Re-certification is required for many national and international > standards like SOX, GxP, etc. > The idea is to implement one scheduled task that filter users basing on some > attributes (example: last recertification date, role,...) and move then on > one state "to be certified" and assign one task to some group that has the > responsibility to recertified the user, or delete it from the system. > Some report should report evidence about when the users have been recertified > and who was the certifier. > > This feature would be also the starting point to create account, role and > groups re-certifications. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[GitHub] syncope pull request #26: [SYNCOPE-880] Identity Recertification
Github user ilgrosso commented on a diff in the pull request: https://github.com/apache/syncope/pull/26#discussion_r76007392 --- Diff: pom.xml --- @@ -197,6 +197,16 @@ under the License. http://people.apache.org/~anzelld/ + anzelld --- End diff -- ...guess you'll need to change `anzelld` with your own ASF id, right? --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] syncope pull request #26: [SYNCOPE-880] Identity Recertification
Github user ilgrosso commented on a diff in the pull request: https://github.com/apache/syncope/pull/26#discussion_r76007411 --- Diff: pom.xml --- @@ -197,6 +197,16 @@ under the License. http://people.apache.org/~anzelld/ + anzelld + Nicola Scendoni + The Apache Software Foundation + http://www.apache.org/ + +committer + + http://people.apache.org/~anzelld/ --- End diff -- ...guess you'll need to change `anzelld` with your own ASF id, right? --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[jira] [Commented] (SYNCOPE-880) Identity Recertification
[
https://issues.apache.org/jira/browse/SYNCOPE-880?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15434372#comment-15434372
]
ASF GitHub Bot commented on SYNCOPE-880:
Github user ilgrosso commented on a diff in the pull request:
https://github.com/apache/syncope/pull/26#discussion_r76006998
--- Diff:
core/provisioning-java/src/main/java/org/apache/syncope/core/provisioning/java/job/IdentityRecertification.java
---
@@ -81,11 +88,11 @@ public void init() {
public boolean toBeRecertified(final User user) {
-UPlainAttr lastUserRecertification =
user.getPlainAttr(Recertify.LAST_RECERTIFICATION_ATTR);
+UPlainAttr lastUserRecertification =
user.getPlainAttr(LAST_RECERTIFICATION_ATTR);
--- End diff --
You should not need this anymore, right?
> Identity Recertification
>
>
> Key: SYNCOPE-880
> URL: https://issues.apache.org/jira/browse/SYNCOPE-880
> Project: Syncope
> Issue Type: New Feature
> Components: core
>Reporter: Nicola Scendoni
>Assignee: Nicola Scendoni
>Priority: Minor
> Fix For: 2.0.0
>
>
> Identify Re-certification is required for many national and international
> standards like SOX, GxP, etc.
> The idea is to implement one scheduled task that filter users basing on some
> attributes (example: last recertification date, role,...) and move then on
> one state "to be certified" and assign one task to some group that has the
> responsibility to recertified the user, or delete it from the system.
> Some report should report evidence about when the users have been recertified
> and who was the certifier.
>
> This feature would be also the starting point to create account, role and
> groups re-certifications.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (SYNCOPE-880) Identity Recertification
[ https://issues.apache.org/jira/browse/SYNCOPE-880?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15434371#comment-15434371 ] ASF GitHub Bot commented on SYNCOPE-880: Github user ilgrosso commented on a diff in the pull request: https://github.com/apache/syncope/pull/26#discussion_r76006988 --- Diff: core/provisioning-java/src/main/java/org/apache/syncope/core/provisioning/java/job/IdentityRecertification.java --- @@ -41,6 +42,12 @@ private long recertificationTimeLong = -1; +public static final String LAST_RECERTIFICATOR_ATTR = "lastRecertificator"; + +public static final String LAST_RECERTIFICATION_ATTR = "lastRecertification"; --- End diff -- You should not need this anymore, right? > Identity Recertification > > > Key: SYNCOPE-880 > URL: https://issues.apache.org/jira/browse/SYNCOPE-880 > Project: Syncope > Issue Type: New Feature > Components: core >Reporter: Nicola Scendoni >Assignee: Nicola Scendoni >Priority: Minor > Fix For: 2.0.0 > > > Identify Re-certification is required for many national and international > standards like SOX, GxP, etc. > The idea is to implement one scheduled task that filter users basing on some > attributes (example: last recertification date, role,...) and move then on > one state "to be certified" and assign one task to some group that has the > responsibility to recertified the user, or delete it from the system. > Some report should report evidence about when the users have been recertified > and who was the certifier. > > This feature would be also the starting point to create account, role and > groups re-certifications. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[GitHub] syncope pull request #26: [SYNCOPE-880] Identity Recertification
Github user ilgrosso commented on a diff in the pull request:
https://github.com/apache/syncope/pull/26#discussion_r76006998
--- Diff:
core/provisioning-java/src/main/java/org/apache/syncope/core/provisioning/java/job/IdentityRecertification.java
---
@@ -81,11 +88,11 @@ public void init() {
public boolean toBeRecertified(final User user) {
-UPlainAttr lastUserRecertification =
user.getPlainAttr(Recertify.LAST_RECERTIFICATION_ATTR);
+UPlainAttr lastUserRecertification =
user.getPlainAttr(LAST_RECERTIFICATION_ATTR);
--- End diff --
You should not need this anymore, right?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
[jira] [Commented] (SYNCOPE-880) Identity Recertification
[ https://issues.apache.org/jira/browse/SYNCOPE-880?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15434369#comment-15434369 ] ASF GitHub Bot commented on SYNCOPE-880: Github user ilgrosso commented on a diff in the pull request: https://github.com/apache/syncope/pull/26#discussion_r76006983 --- Diff: core/provisioning-java/src/main/java/org/apache/syncope/core/provisioning/java/job/IdentityRecertification.java --- @@ -41,6 +42,12 @@ private long recertificationTimeLong = -1; +public static final String LAST_RECERTIFICATOR_ATTR = "lastRecertificator"; --- End diff -- You should not need this anymore, right? > Identity Recertification > > > Key: SYNCOPE-880 > URL: https://issues.apache.org/jira/browse/SYNCOPE-880 > Project: Syncope > Issue Type: New Feature > Components: core >Reporter: Nicola Scendoni >Assignee: Nicola Scendoni >Priority: Minor > Fix For: 2.0.0 > > > Identify Re-certification is required for many national and international > standards like SOX, GxP, etc. > The idea is to implement one scheduled task that filter users basing on some > attributes (example: last recertification date, role,...) and move then on > one state "to be certified" and assign one task to some group that has the > responsibility to recertified the user, or delete it from the system. > Some report should report evidence about when the users have been recertified > and who was the certifier. > > This feature would be also the starting point to create account, role and > groups re-certifications. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[GitHub] syncope pull request #26: [SYNCOPE-880] Identity Recertification
Github user ilgrosso commented on a diff in the pull request: https://github.com/apache/syncope/pull/26#discussion_r76006988 --- Diff: core/provisioning-java/src/main/java/org/apache/syncope/core/provisioning/java/job/IdentityRecertification.java --- @@ -41,6 +42,12 @@ private long recertificationTimeLong = -1; +public static final String LAST_RECERTIFICATOR_ATTR = "lastRecertificator"; + +public static final String LAST_RECERTIFICATION_ATTR = "lastRecertification"; --- End diff -- You should not need this anymore, right? --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] syncope pull request #26: [SYNCOPE-880] Identity Recertification
Github user ilgrosso commented on a diff in the pull request: https://github.com/apache/syncope/pull/26#discussion_r76006983 --- Diff: core/provisioning-java/src/main/java/org/apache/syncope/core/provisioning/java/job/IdentityRecertification.java --- @@ -41,6 +42,12 @@ private long recertificationTimeLong = -1; +public static final String LAST_RECERTIFICATOR_ATTR = "lastRecertificator"; --- End diff -- You should not need this anymore, right? --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[jira] [Commented] (SYNCOPE-880) Identity Recertification
[ https://issues.apache.org/jira/browse/SYNCOPE-880?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15434362#comment-15434362 ] ASF GitHub Bot commented on SYNCOPE-880: Github user ilgrosso commented on a diff in the pull request: https://github.com/apache/syncope/pull/26#discussion_r76006872 --- Diff: core/persistence-jpa/src/main/resources/domains/MasterContent.xml --- @@ -1,4 +1,4 @@ - +t --- End diff -- Guess you would undo this modification, right? :-) > Identity Recertification > > > Key: SYNCOPE-880 > URL: https://issues.apache.org/jira/browse/SYNCOPE-880 > Project: Syncope > Issue Type: New Feature > Components: core >Reporter: Nicola Scendoni >Assignee: Nicola Scendoni >Priority: Minor > Fix For: 2.0.0 > > > Identify Re-certification is required for many national and international > standards like SOX, GxP, etc. > The idea is to implement one scheduled task that filter users basing on some > attributes (example: last recertification date, role,...) and move then on > one state "to be certified" and assign one task to some group that has the > responsibility to recertified the user, or delete it from the system. > Some report should report evidence about when the users have been recertified > and who was the certifier. > > This feature would be also the starting point to create account, role and > groups re-certifications. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[GitHub] syncope pull request #26: [SYNCOPE-880] Identity Recertification
Github user ilgrosso commented on a diff in the pull request: https://github.com/apache/syncope/pull/26#discussion_r76006872 --- Diff: core/persistence-jpa/src/main/resources/domains/MasterContent.xml --- @@ -1,4 +1,4 @@ - +t --- End diff -- Guess you would undo this modification, right? :-) --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[jira] [Closed] (SYNCOPE-924) Can I search on User derived schema items via the rest/users/search api?
[ https://issues.apache.org/jira/browse/SYNCOPE-924?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Francesco Chicchiriccò closed SYNCOPE-924. -- Resolution: Information Provided Assignee: Francesco Chicchiriccò Dear Steve, it is not currently possible to use derived (or virtual) attributes as parameters when searching for users: the way how the search feature is implemented does not allow efficient queries by derived values. For follow-up, and other questions you might have, I invite you to join the user@ mailing list or our IRC channel: http://syncope.apache.org/mailing-lists.html Regards. > Can I search on User derived schema items via the rest/users/search api? > > > Key: SYNCOPE-924 > URL: https://issues.apache.org/jira/browse/SYNCOPE-924 > Project: Syncope > Issue Type: Wish >Affects Versions: 1.2.6 > Environment: linux >Reporter: Steve Yonkaitis >Assignee: Francesco Chicchiriccò > > I want to search on a derived schema item created under the User schema via > the rest api. When I access the rest api for example: > rest/users/search?fiql=lowerCaseEmail==someu...@bogus.com. I get a warning in > the log file Ignorning invalid schema: lowerCaseEmail. > Is there anyway to use the rest api for users to search on a User's derived > schema item? -- This message was sent by Atlassian JIRA (v6.3.4#6332)
