[jira] [Resolved] (SYNCOPE-1322) Get available tasks from workflow definition
[ https://issues.apache.org/jira/browse/SYNCOPE-1322?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Francesco Chicchiriccò resolved SYNCOPE-1322. - Resolution: Fixed > Get available tasks from workflow definition > > > Key: SYNCOPE-1322 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1322 > Project: Syncope > Issue Type: Improvement > Components: core >Reporter: Francesco Chicchiriccò >Assignee: Francesco Chicchiriccò >Priority: Major > Fix For: 1.2.12, 2.0.9, 2.1.0 > > > Given a certain user, provide all the tasks that can be requested for > execution, according to the workflow definition. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (SYNCOPE-1322) Get available tasks from workflow definition
[ https://issues.apache.org/jira/browse/SYNCOPE-1322?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16508152#comment-16508152 ] Francesco Chicchiriccò commented on SYNCOPE-1322: - 1_2_X: https://github.com/apache/syncope/commit/43852c90327c9e61a474aa9b601b9e324d293827 > Get available tasks from workflow definition > > > Key: SYNCOPE-1322 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1322 > Project: Syncope > Issue Type: Improvement > Components: core >Reporter: Francesco Chicchiriccò >Assignee: Francesco Chicchiriccò >Priority: Major > Fix For: 1.2.12, 2.0.9, 2.1.0 > > > Given a certain user, provide all the tasks that can be requested for > execution, according to the workflow definition. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (SYNCOPE-1321) Search doesn't work for date attributes with conversion pattern with time zone
[
https://issues.apache.org/jira/browse/SYNCOPE-1321?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16508138#comment-16508138
]
Alexey commented on SYNCOPE-1321:
-
Ok, I will provide PR as soon as I have some spare time.
> Search doesn't work for date attributes with conversion pattern with time zone
> --
>
> Key: SYNCOPE-1321
> URL: https://issues.apache.org/jira/browse/SYNCOPE-1321
> Project: Syncope
> Issue Type: Bug
> Components: core
>Affects Versions: 2.0.8
>Reporter: Alexey
>Priority: Major
> Labels: date, format, formatDate, schema, time_zone
> Fix For: 2.0.9, 2.1.0
>
> Attachments: after.PNG, before.PNG
>
>
> 1.) I have _date type_ *PlainSchemaTO* configured with conversion pattern
> {{org.apache.cxf.jaxrs.ext.search.SearchUtils.TIMESTAMP_WITH_TIMEZONE_Z =
> }}{{"-MM-dd\'T\'HH:mm:ssZ"}}
> 2.) For instance, I built a new query using
> {{org.apache.cxf.jaxrs.ext.search.client.FiqlSearchConditionBuilder with an
> appropriate settings for date format.}}
> 3.) Query is built successfully, for instance
> "date_att=lt=2018-06-12T15:21:00+0300"
> but after its value being processed by *URLDecoder* in
> {{org.apache.syncope.core.persistence.api.search.SearchCondVisitor, see line
> 79:}}
> {{value =
> SearchUtils.toSqlWildcardString(*URLDecoder*.*decode*(sc.getStatement().getValue().toString(),
> StandardCharsets.UTF_8.name()), false).replaceAll("_", "_");}}
> plus sign ('*+*') is replacing with space (' ') which leads to incorrect
> query processing in further Syncope code.
> I assume *URLDecoder.decode* should be removed, it should be already done by
> a servlet container.
> Currently, I'm using a quite ugly fix by double encoding date schema value on
> a client side and dealing with date values as string ones...
> Kind Regards,
> Alexey
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
RE: Regarding GSOC 2018
Hi Andrea , Currently I have done this for the Netbeans Plugin in Apache Syncope I have updated the my fork of the syncope repo . Best Regards , Rohan Julka From: Andrea Patricelli Sent: 11 June 2018 15:58 To: rohan julka Subject: Re: Regarding GSOC 2018 Please frequently commit your developments in order to let me check how they are going. Otherwise I cannot evaluate your work. Thanks and regards, Andrea Il 11/06/2018 11:33, rohan julka ha scritto: My GitHub fork of syncope https://github.com/rohanjulka19/syncope and are you sure it is a good idea to attach the mailing list as I am quite a rookie you know , sometimes the questions I ask does not make sense :p From: Andrea Patricelli Sent: 11 June 2018 14:03 To: rohan julka Subject: Re: Regarding GSOC 2018 Please could you send to me the link of your fork of Syncope on Github? Best regards, Andrea
[jira] [Commented] (SYNCOPE-1322) Get available tasks from workflow definition
[ https://issues.apache.org/jira/browse/SYNCOPE-1322?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16508076#comment-16508076 ] Francesco Chicchiriccò commented on SYNCOPE-1322: - Commits: * master: [http://git-wip-us.apache.org/repos/asf/syncope/commit/8db75d21] * 2_0_X: [http://git-wip-us.apache.org/repos/asf/syncope/commit/b10beb88] > Get available tasks from workflow definition > > > Key: SYNCOPE-1322 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1322 > Project: Syncope > Issue Type: Improvement > Components: core >Reporter: Francesco Chicchiriccò >Assignee: Francesco Chicchiriccò >Priority: Major > Fix For: 1.2.12, 2.0.9, 2.1.0 > > > Given a certain user, provide all the tasks that can be requested for > execution, according to the workflow definition. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Comment Edited] (SYNCOPE-1321) Search doesn't work for date attributes with conversion pattern with time zone
[
https://issues.apache.org/jira/browse/SYNCOPE-1321?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16508036#comment-16508036
]
Francesco Chicchiriccò edited comment on SYNCOPE-1321 at 6/11/18 1:21 PM:
--
Mind proposing an implementation for such a change? You can do that also by
forking [https://github.com/apache/syncope] and sending a PR (branch {{2_0_X}}).
In case, please ensure to have a look at
* [https://cwiki.apache.org/confluence/display/SYNCOPE/Git+workflow]
*
[http://syncope.apache.org/contributing.html#How_do_I_become_a_contributor_or_a_committer]
was (Author: ilgrosso):
Mind proposing an implementation for such a change? You can do that also by
forking [https://github.com/apache/syncope] and sending a PR (branch {{2_0_X]]).
In case, please ensure to have a look at
* [https://cwiki.apache.org/confluence/display/SYNCOPE/Git+workflow]
*
[http://syncope.apache.org/contributing.html#How_do_I_become_a_contributor_or_a_committer]
> Search doesn't work for date attributes with conversion pattern with time zone
> --
>
> Key: SYNCOPE-1321
> URL: https://issues.apache.org/jira/browse/SYNCOPE-1321
> Project: Syncope
> Issue Type: Bug
> Components: core
>Affects Versions: 2.0.8
>Reporter: Alexey
>Priority: Major
> Labels: date, format, formatDate, schema, time_zone
> Fix For: 2.0.9, 2.1.0
>
> Attachments: after.PNG, before.PNG
>
>
> 1.) I have _date type_ *PlainSchemaTO* configured with conversion pattern
> {{org.apache.cxf.jaxrs.ext.search.SearchUtils.TIMESTAMP_WITH_TIMEZONE_Z =
> }}{{"-MM-dd\'T\'HH:mm:ssZ"}}
> 2.) For instance, I built a new query using
> {{org.apache.cxf.jaxrs.ext.search.client.FiqlSearchConditionBuilder with an
> appropriate settings for date format.}}
> 3.) Query is built successfully, for instance
> "date_att=lt=2018-06-12T15:21:00+0300"
> but after its value being processed by *URLDecoder* in
> {{org.apache.syncope.core.persistence.api.search.SearchCondVisitor, see line
> 79:}}
> {{value =
> SearchUtils.toSqlWildcardString(*URLDecoder*.*decode*(sc.getStatement().getValue().toString(),
> StandardCharsets.UTF_8.name()), false).replaceAll("_", "_");}}
> plus sign ('*+*') is replacing with space (' ') which leads to incorrect
> query processing in further Syncope code.
> I assume *URLDecoder.decode* should be removed, it should be already done by
> a servlet container.
> Currently, I'm using a quite ugly fix by double encoding date schema value on
> a client side and dealing with date values as string ones...
> Kind Regards,
> Alexey
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (SYNCOPE-1321) Search doesn't work for date attributes with conversion pattern with time zone
[
https://issues.apache.org/jira/browse/SYNCOPE-1321?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16508036#comment-16508036
]
Francesco Chicchiriccò commented on SYNCOPE-1321:
-
Mind proposing an implementation for such a change? You can do that also by
forking [https://github.com/apache/syncope] and sending a PR (branch {{2_0_X]]).
In case, please ensure to have a look at
* [https://cwiki.apache.org/confluence/display/SYNCOPE/Git+workflow]
*
[http://syncope.apache.org/contributing.html#How_do_I_become_a_contributor_or_a_committer]
> Search doesn't work for date attributes with conversion pattern with time zone
> --
>
> Key: SYNCOPE-1321
> URL: https://issues.apache.org/jira/browse/SYNCOPE-1321
> Project: Syncope
> Issue Type: Bug
> Components: core
>Affects Versions: 2.0.8
>Reporter: Alexey
>Priority: Major
> Labels: date, format, formatDate, schema, time_zone
> Fix For: 2.0.9, 2.1.0
>
> Attachments: after.PNG, before.PNG
>
>
> 1.) I have _date type_ *PlainSchemaTO* configured with conversion pattern
> {{org.apache.cxf.jaxrs.ext.search.SearchUtils.TIMESTAMP_WITH_TIMEZONE_Z =
> }}{{"-MM-dd\'T\'HH:mm:ssZ"}}
> 2.) For instance, I built a new query using
> {{org.apache.cxf.jaxrs.ext.search.client.FiqlSearchConditionBuilder with an
> appropriate settings for date format.}}
> 3.) Query is built successfully, for instance
> "date_att=lt=2018-06-12T15:21:00+0300"
> but after its value being processed by *URLDecoder* in
> {{org.apache.syncope.core.persistence.api.search.SearchCondVisitor, see line
> 79:}}
> {{value =
> SearchUtils.toSqlWildcardString(*URLDecoder*.*decode*(sc.getStatement().getValue().toString(),
> StandardCharsets.UTF_8.name()), false).replaceAll("_", "_");}}
> plus sign ('*+*') is replacing with space (' ') which leads to incorrect
> query processing in further Syncope code.
> I assume *URLDecoder.decode* should be removed, it should be already done by
> a servlet container.
> Currently, I'm using a quite ugly fix by double encoding date schema value on
> a client side and dealing with date values as string ones...
> Kind Regards,
> Alexey
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (SYNCOPE-1321) Search doesn't work for date attributes with conversion pattern with time zone
[
https://issues.apache.org/jira/browse/SYNCOPE-1321?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16508030#comment-16508030
]
Alexey commented on SYNCOPE-1321:
-
It would be a solution too. Thanks for the quick reply!
> Search doesn't work for date attributes with conversion pattern with time zone
> --
>
> Key: SYNCOPE-1321
> URL: https://issues.apache.org/jira/browse/SYNCOPE-1321
> Project: Syncope
> Issue Type: Bug
> Components: core
>Affects Versions: 2.0.8
>Reporter: Alexey
>Priority: Major
> Labels: date, format, formatDate, schema, time_zone
> Fix For: 2.0.9, 2.1.0
>
> Attachments: after.PNG, before.PNG
>
>
> 1.) I have _date type_ *PlainSchemaTO* configured with conversion pattern
> {{org.apache.cxf.jaxrs.ext.search.SearchUtils.TIMESTAMP_WITH_TIMEZONE_Z =
> }}{{"-MM-dd\'T\'HH:mm:ssZ"}}
> 2.) For instance, I built a new query using
> {{org.apache.cxf.jaxrs.ext.search.client.FiqlSearchConditionBuilder with an
> appropriate settings for date format.}}
> 3.) Query is built successfully, for instance
> "date_att=lt=2018-06-12T15:21:00+0300"
> but after its value being processed by *URLDecoder* in
> {{org.apache.syncope.core.persistence.api.search.SearchCondVisitor, see line
> 79:}}
> {{value =
> SearchUtils.toSqlWildcardString(*URLDecoder*.*decode*(sc.getStatement().getValue().toString(),
> StandardCharsets.UTF_8.name()), false).replaceAll("_", "_");}}
> plus sign ('*+*') is replacing with space (' ') which leads to incorrect
> query processing in further Syncope code.
> I assume *URLDecoder.decode* should be removed, it should be already done by
> a servlet container.
> Currently, I'm using a quite ugly fix by double encoding date schema value on
> a client side and dealing with date values as string ones...
> Kind Regards,
> Alexey
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Comment Edited] (SYNCOPE-1321) Search doesn't work for date attributes with conversion pattern with time zone
[
https://issues.apache.org/jira/browse/SYNCOPE-1321?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16508021#comment-16508021
]
Francesco Chicchiriccò edited comment on SYNCOPE-1321 at 6/11/18 1:15 PM:
--
URL decoding was introduced as part of SYNCOPE-1223, by [this
commit|https://github.com/apache/syncope/commit/a1e9c04fa1edd4812876fb8c943b0c2e37c3d80b],
hence it cannot be simply removed.
We might reserve a special treatment for the '+' sign, if found right before
the last 4 characters, and if such characters are all digits: what do you think?
was (Author: ilgrosso):
URL decoding was introduced as part of SYNCOPE-1223, by [this
commit|https://github.com/apache/syncope/commit/a1e9c04fa1edd4812876fb8c943b0c2e37c3d80b],
hence it cannot simply removed.
We might reserve a special treatment for the '+' sign, if found right before
the last 4 characters, and if such characters are all digits: what do you think?
> Search doesn't work for date attributes with conversion pattern with time zone
> --
>
> Key: SYNCOPE-1321
> URL: https://issues.apache.org/jira/browse/SYNCOPE-1321
> Project: Syncope
> Issue Type: Bug
> Components: core
>Affects Versions: 2.0.8
>Reporter: Alexey
>Priority: Major
> Labels: date, format, formatDate, schema, time_zone
> Fix For: 2.0.9, 2.1.0
>
> Attachments: after.PNG, before.PNG
>
>
> 1.) I have _date type_ *PlainSchemaTO* configured with conversion pattern
> {{org.apache.cxf.jaxrs.ext.search.SearchUtils.TIMESTAMP_WITH_TIMEZONE_Z =
> }}{{"-MM-dd\'T\'HH:mm:ssZ"}}
> 2.) For instance, I built a new query using
> {{org.apache.cxf.jaxrs.ext.search.client.FiqlSearchConditionBuilder with an
> appropriate settings for date format.}}
> 3.) Query is built successfully, for instance
> "date_att=lt=2018-06-12T15:21:00+0300"
> but after its value being processed by *URLDecoder* in
> {{org.apache.syncope.core.persistence.api.search.SearchCondVisitor, see line
> 79:}}
> {{value =
> SearchUtils.toSqlWildcardString(*URLDecoder*.*decode*(sc.getStatement().getValue().toString(),
> StandardCharsets.UTF_8.name()), false).replaceAll("_", "_");}}
> plus sign ('*+*') is replacing with space (' ') which leads to incorrect
> query processing in further Syncope code.
> I assume *URLDecoder.decode* should be removed, it should be already done by
> a servlet container.
> Currently, I'm using a quite ugly fix by double encoding date schema value on
> a client side and dealing with date values as string ones...
> Kind Regards,
> Alexey
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (SYNCOPE-1321) Search doesn't work for date attributes with conversion pattern with time zone
[
https://issues.apache.org/jira/browse/SYNCOPE-1321?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16508021#comment-16508021
]
Francesco Chicchiriccò commented on SYNCOPE-1321:
-
URL decoding was introduced as part of SYNCOPE-1223, by [this
commit|https://github.com/apache/syncope/commit/a1e9c04fa1edd4812876fb8c943b0c2e37c3d80b],
hence it cannot simply removed.
We might reserve a special treatment for the '+' sign, if found right before
the last 4 characters, and if such characters are all digits: what do you think?
> Search doesn't work for date attributes with conversion pattern with time zone
> --
>
> Key: SYNCOPE-1321
> URL: https://issues.apache.org/jira/browse/SYNCOPE-1321
> Project: Syncope
> Issue Type: Bug
> Components: core
>Affects Versions: 2.0.8
>Reporter: Alexey
>Priority: Major
> Labels: date, format, formatDate, schema, time_zone
> Fix For: 2.0.9, 2.1.0
>
> Attachments: after.PNG, before.PNG
>
>
> 1.) I have _date type_ *PlainSchemaTO* configured with conversion pattern
> {{org.apache.cxf.jaxrs.ext.search.SearchUtils.TIMESTAMP_WITH_TIMEZONE_Z =
> }}{{"-MM-dd\'T\'HH:mm:ssZ"}}
> 2.) For instance, I built a new query using
> {{org.apache.cxf.jaxrs.ext.search.client.FiqlSearchConditionBuilder with an
> appropriate settings for date format.}}
> 3.) Query is built successfully, for instance
> "date_att=lt=2018-06-12T15:21:00+0300"
> but after its value being processed by *URLDecoder* in
> {{org.apache.syncope.core.persistence.api.search.SearchCondVisitor, see line
> 79:}}
> {{value =
> SearchUtils.toSqlWildcardString(*URLDecoder*.*decode*(sc.getStatement().getValue().toString(),
> StandardCharsets.UTF_8.name()), false).replaceAll("_", "_");}}
> plus sign ('*+*') is replacing with space (' ') which leads to incorrect
> query processing in further Syncope code.
> I assume *URLDecoder.decode* should be removed, it should be already done by
> a servlet container.
> Currently, I'm using a quite ugly fix by double encoding date schema value on
> a client side and dealing with date values as string ones...
> Kind Regards,
> Alexey
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (SYNCOPE-1321) Search doesn't work for date attributes with conversion pattern with time zone
[
https://issues.apache.org/jira/browse/SYNCOPE-1321?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Francesco Chicchiriccò updated SYNCOPE-1321:
Fix Version/s: 2.1.0
2.0.9
> Search doesn't work for date attributes with conversion pattern with time zone
> --
>
> Key: SYNCOPE-1321
> URL: https://issues.apache.org/jira/browse/SYNCOPE-1321
> Project: Syncope
> Issue Type: Bug
> Components: core
>Affects Versions: 2.0.8
>Reporter: Alexey
>Priority: Major
> Labels: date, format, formatDate, schema, time_zone
> Fix For: 2.0.9, 2.1.0
>
> Attachments: after.PNG, before.PNG
>
>
> 1.) I have _date type_ *PlainSchemaTO* configured with conversion pattern
> {{org.apache.cxf.jaxrs.ext.search.SearchUtils.TIMESTAMP_WITH_TIMEZONE_Z =
> }}{{"-MM-dd\'T\'HH:mm:ssZ"}}
> 2.) For instance, I built a new query using
> {{org.apache.cxf.jaxrs.ext.search.client.FiqlSearchConditionBuilder with an
> appropriate settings for date format.}}
> 3.) Query is built successfully, for instance
> "date_att=lt=2018-06-12T15:21:00+0300"
> but after its value being processed by *URLDecoder* in
> {{org.apache.syncope.core.persistence.api.search.SearchCondVisitor, see line
> 79:}}
> {{value =
> SearchUtils.toSqlWildcardString(*URLDecoder*.*decode*(sc.getStatement().getValue().toString(),
> StandardCharsets.UTF_8.name()), false).replaceAll("_", "_");}}
> plus sign ('*+*') is replacing with space (' ') which leads to incorrect
> query processing in further Syncope code.
> I assume *URLDecoder.decode* should be removed, it should be already done by
> a servlet container.
> Currently, I'm using a quite ugly fix by double encoding date schema value on
> a client side and dealing with date values as string ones...
> Kind Regards,
> Alexey
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (SYNCOPE-1322) Get available tasks from workflow definition
Francesco Chicchiriccò created SYNCOPE-1322: --- Summary: Get available tasks from workflow definition Key: SYNCOPE-1322 URL: https://issues.apache.org/jira/browse/SYNCOPE-1322 Project: Syncope Issue Type: Improvement Components: core Reporter: Francesco Chicchiriccò Assignee: Francesco Chicchiriccò Fix For: 1.2.12, 2.0.9, 2.1.0 Given a certain user, provide all the tasks that can be requested for execution, according to the workflow definition. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (SYNCOPE-1321) Search doesn't work for date attributes with conversion pattern with time zone
Alexey created SYNCOPE-1321:
---
Summary: Search doesn't work for date attributes with conversion
pattern with time zone
Key: SYNCOPE-1321
URL: https://issues.apache.org/jira/browse/SYNCOPE-1321
Project: Syncope
Issue Type: Bug
Components: core
Affects Versions: 2.0.8
Reporter: Alexey
Attachments: after.PNG, before.PNG
1.) I have _date type_ *PlainSchemaTO* configured with conversion pattern
{{org.apache.cxf.jaxrs.ext.search.SearchUtils.TIMESTAMP_WITH_TIMEZONE_Z =
}}{{"-MM-dd\'T\'HH:mm:ssZ"}}
2.) For instance, I built a new query using
{{org.apache.cxf.jaxrs.ext.search.client.FiqlSearchConditionBuilder with an
appropriate settings for date format.}}
3.) Query is built successfully, for instance
"date_att=lt=2018-06-12T15:21:00+0300"
but after its value being processed by *URLDecoder* in
{{org.apache.syncope.core.persistence.api.search.SearchCondVisitor, see line
79:}}
{{value =
SearchUtils.toSqlWildcardString(*URLDecoder*.*decode*(sc.getStatement().getValue().toString(),
StandardCharsets.UTF_8.name()), false).replaceAll("_", "_");}}
plus sign ('*+*') is replacing with space (' ') which leads to incorrect query
processing in further Syncope code.
I assume *URLDecoder.decode* should be removed, it should be already done by a
servlet container.
Currently, I'm using a quite ugly fix by double encoding date schema value on a
client side and dealing with date values as string ones...
Kind Regards,
Alexey
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (SYNCOPE-1256) Docker plugin and profile distributed with archetype
[ https://issues.apache.org/jira/browse/SYNCOPE-1256?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Patricelli reassigned SYNCOPE-1256: -- Assignee: (was: Andrea Patricelli) > Docker plugin and profile distributed with archetype > > > Key: SYNCOPE-1256 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1256 > Project: Syncope > Issue Type: Improvement > Components: archetype >Affects Versions: 2.0.7 >Reporter: Andrea Patricelli >Priority: Major > Fix For: 2.0.9, 2.1.0 > > > Add docker profile to archetype. Profile will contain docker maven plugin > definition and system properties used to configure core, console and enduser > docker containers. > Provide a sample docker-compose.yml file taht puts together all modules. > Parametrize (if possible) the choice of the docker image for containers > Add documentation about this new way to install syncope in real environment > through docker. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (SYNCOPE-1256) Docker plugin and profile distributed with archetype
[ https://issues.apache.org/jira/browse/SYNCOPE-1256?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Francesco Chicchiriccò reassigned SYNCOPE-1256: --- Assignee: Francesco Chicchiriccò > Docker plugin and profile distributed with archetype > > > Key: SYNCOPE-1256 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1256 > Project: Syncope > Issue Type: Improvement > Components: archetype >Affects Versions: 2.0.7 >Reporter: Andrea Patricelli >Assignee: Francesco Chicchiriccò >Priority: Major > Fix For: 2.0.9, 2.1.0 > > > Add docker profile to archetype. Profile will contain docker maven plugin > definition and system properties used to configure core, console and enduser > docker containers. > Provide a sample docker-compose.yml file taht puts together all modules. > Parametrize (if possible) the choice of the docker image for containers > Add documentation about this new way to install syncope in real environment > through docker. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (SYNCOPE-1270) OpenID Connect client feature
[ https://issues.apache.org/jira/browse/SYNCOPE-1270?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16507748#comment-16507748 ] Francesco Chicchiriccò commented on SYNCOPE-1270: - More commits: * master ** https://git-wip-us.apache.org/repos/asf?p=syncope.git;a=commit;h=f57cb310537d9a907c4aa55484938e02c9361733 ** https://git-wip-us.apache.org/repos/asf?p=syncope.git;a=commit;h=ff597a7d53a7a7e602a71db0a2a70f9c074aaf40 * 2_0_X ** https://git-wip-us.apache.org/repos/asf?p=syncope.git;a=commit;h=413963f993ea4e5676c696bec75f5c1ea6154acf ** https://git-wip-us.apache.org/repos/asf?p=syncope.git;a=commit;h=49a88b121653aebd2d8a9b5a16a6f285c6243bf5 > OpenID Connect client feature > - > > Key: SYNCOPE-1270 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1270 > Project: Syncope > Issue Type: New Feature > Components: extensions >Reporter: Dima Ayash >Assignee: Francesco Chicchiriccò >Priority: Major > Fix For: 2.0.9, 2.1.0 > > > This feature implements an SSO access to the Enduser UI and Admin Console by > using [OpenID Connect 1.0|http://openid.net/connect/] which is a simple > identity layer on top of the OAuth 2.0 protocol. It allows Clients to verify > the identity of the End-User based on the authentication performed by an > Authorization Server, as well as to obtain basic profile information about > the End-User in an interoperable and REST-like manner. > The flow for this feature will be possibly as follow (using Google as an > example of OpenID Connect Provider): > # From Enduser or Admin login UI, the user can choose to be authenticated > using Google account. > # Check if the user has a valid session, otherwise prompts the user to login > by redirecting him to the Google Login UI. > # After the user login successfully to his Google account, grant him an > access to Enduser UI or Admin console. > This will be achieved by following the OpenId Connect required flow, > leveraging possibly from CXF features. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (SYNCOPE-1318) Future task rejected from ScheduledThreadPoolExecutor
[
https://issues.apache.org/jira/browse/SYNCOPE-1318?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16507745#comment-16507745
]
Francesco Chicchiriccò commented on SYNCOPE-1318:
-
More commits:
* master:
https://git-wip-us.apache.org/repos/asf?p=syncope.git;h=26e2b9dd3c7f01eb0572883ae0877d29fbdf53fa
* 2_0_X:
https://git-wip-us.apache.org/repos/asf?p=syncope.git;h=df5c7fe4df54e40b33ab252370d578d9b99dfcb5
> Future task rejected from ScheduledThreadPoolExecutor
> -
>
> Key: SYNCOPE-1318
> URL: https://issues.apache.org/jira/browse/SYNCOPE-1318
> Project: Syncope
> Issue Type: Bug
> Components: console
>Affects Versions: 2.0.8
>Reporter: Marco Di Sabatino Di Diodoro
>Assignee: Francesco Chicchiriccò
>Priority: Major
> Fix For: 2.0.9, 2.1.0
>
>
> After several operations on the console, the connection pool to the core ends
> and doesn't allows to perform other operations
> {code}
> ERROR org.apache.syncope.client.console.wizards.AjaxWizard - Wizard error on
> finish
> java.util.concurrent.RejectedExecutionException: Task
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask@561b0d9e
> rejected from
> java.util.concurrent.ScheduledThreadPoolExecutor@73c6df51[Terminated, pool
> size = 0, active threads = 0, queued tasks = 0, completed tasks = 1]
> at
> java.util.concurrent.ThreadPoolExecutor$AbortPolicy.rejectedExecution(ThreadPoolExecutor.java:2063)
> ~[?:1.8.0_151]
> at
> java.util.concurrent.ThreadPoolExecutor.reject(ThreadPoolExecutor.java:830)
> ~[?:1.8.0_151]
> at
> java.util.concurrent.ScheduledThreadPoolExecutor.delayedExecute(ScheduledThreadPoolExecutor.java:326)
> ~[?:1.8.0_151]
> at
> java.util.concurrent.ScheduledThreadPoolExecutor.schedule(ScheduledThreadPoolExecutor.java:549)
> ~[?:1.8.0_151]
> at
> java.util.concurrent.ScheduledThreadPoolExecutor.submit(ScheduledThreadPoolExecutor.java:648)
> ~[?:1.8.0_151]
> at
> org.apache.syncope.client.console.SyncopeConsoleSession.execute(SyncopeConsoleSession.java:128)
> ~[classes/:2.0.8]
> at
> org.apache.syncope.client.console.wizards.AjaxWizard.onApply(AjaxWizard.java:383)
> ~[syncope-client-console-2.0.8.jar:2.0.8]
> at
> org.apache.syncope.client.console.wizards.AjaxWizard.onFinish(AjaxWizard.java:198)
> ~[syncope-client-console-2.0.8.jar:2.0.8]
> at
> org.apache.wicket.extensions.wizard.AbstractWizardModel.fireWizardFinished(AbstractWizardModel.java:182)
> ~[wicket-extensions-7.10.0.jar:7.10.0]
> at
> org.apache.wicket.extensions.wizard.AbstractWizardModel.finish(AbstractWizardModel.java:88)
> ~[wicket-extensions-7.10.0.jar:7.10.0]
> at
> org.apache.wicket.extensions.wizard.FinishButton.onClick(FinishButton.java:68)
> ~[wicket-extensions-7.10.0.jar:7.10.0]
> at
> org.apache.wicket.extensions.wizard.WizardButton.onSubmit(WizardButton.java:88)
> ~[wicket-extensions-7.10.0.jar:7.10.0]
> at
> org.apache.syncope.client.console.wizards.AjaxWizardMgtButtonBar$1.onSubmit(AjaxWizardMgtButtonBar.java:80)
> ~[syncope-client-console-2.0.8.jar:2.0.8]
> at
> org.apache.wicket.ajax.form.AjaxFormSubmitBehavior$AjaxFormSubmitter.onSubmit(AjaxFormSubmitBehavior.java:218)
> ~[wicket-core-7.10.0.jar:7.10.0]
> at
> org.apache.wicket.markup.html.form.Form.delegateSubmit(Form.java:1311)
> ~[wicket-core-7.10.0.jar:7.10.0]
> at org.apache.wicket.markup.html.form.Form.process(Form.java:977)
> ~[wicket-core-7.10.0.jar:7.10.0]
> at
> org.apache.wicket.markup.html.form.Form.onFormSubmitted(Form.java:798)
> ~[wicket-core-7.10.0.jar:7.10.0]
> at
> org.apache.wicket.ajax.form.AjaxFormSubmitBehavior.onEvent(AjaxFormSubmitBehavior.java:174)
> ~[wicket-core-7.10.0.jar:7.10.0]
> at
> org.apache.wicket.ajax.AjaxEventBehavior.respond(AjaxEventBehavior.java:155)
> ~[wicket-core-7.10.0.jar:7.10.0]
> at
> org.apache.wicket.ajax.AbstractDefaultAjaxBehavior.onRequest(AbstractDefaultAjaxBehavior.java:601)
> ~[wicket-core-7.10.0.jar:7.10.0]
> at sun.reflect.GeneratedMethodAccessor343.invoke(Unknown Source)
> ~[?:?]
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> ~[?:1.8.0_151]
> at java.lang.reflect.Method.invoke(Method.java:498) ~[?:1.8.0_151]
> at
> org.apache.wicket.RequestListenerInterface.internalInvoke(RequestListenerInterface.java:258)
> ~[wicket-core-7.10.0.jar:7.10.0]
> at
> org.apache.wicket.RequestListenerInterface.invoke(RequestListenerInterface.java:241)
> ~[wicket-core-7.10.0.jar:7.10.0]
> at
> org.apache.wicket.core.request.handler.ListenerInterfaceRequestHandler.invokeListener(ListenerInterfaceReques
