[jira] [Resolved] (SYNCOPE-1765) allow WA to decrypt properties during the configuration bootstrap phase
[
https://issues.apache.org/jira/browse/SYNCOPE-1765?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Misagh Moayyed resolved SYNCOPE-1765.
-
Resolution: Fixed
> allow WA to decrypt properties during the configuration bootstrap phase
> ---
>
> Key: SYNCOPE-1765
> URL: https://issues.apache.org/jira/browse/SYNCOPE-1765
> Project: Syncope
> Issue Type: Improvement
> Components: core, wa
>Affects Versions: 3.0.0, 3.0.1, 3.0.2, 3.0.3
>Reporter: Misagh Moayyed
>Assignee: Misagh Moayyed
>Priority: Major
> Fix For: 3.0.4, 4.0.0
>
>
> Configuration properties that are read during the bootstrapping phase should
> be optionally decoded, as they may have been stored in an encrypted format
> that follows "\{cas-cipher}"
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (SYNCOPE-1765) allow WA to decrypt properties during the configuration bootstrap phase
[
https://issues.apache.org/jira/browse/SYNCOPE-1765?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Misagh Moayyed updated SYNCOPE-1765:
Description: Configuration properties that are read during the
bootstrapping phase should be optionally decoded, as they may have been stored
in an encrypted format that follows "\{cas-cipher}" (was: Allow each
AuthModuleConf component to selectively encrypt/decrypt values/settings before
the final conf is stored in the syncope database.)
> allow WA to decrypt properties during the configuration bootstrap phase
> ---
>
> Key: SYNCOPE-1765
> URL: https://issues.apache.org/jira/browse/SYNCOPE-1765
> Project: Syncope
> Issue Type: Improvement
> Components: core, wa
>Affects Versions: 3.0.0, 3.0.1, 3.0.2, 3.0.3
>Reporter: Misagh Moayyed
>Assignee: Misagh Moayyed
>Priority: Major
> Fix For: 3.0.4, 4.0.0
>
>
> Configuration properties that are read during the bootstrapping phase should
> be optionally decoded, as they may have been stored in an encrypted format
> that follows "\{cas-cipher}"
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (SYNCOPE-1765) allow WA to decrypt properties during the configuration bootstrap phase
[ https://issues.apache.org/jira/browse/SYNCOPE-1765?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Misagh Moayyed updated SYNCOPE-1765: Summary: allow WA to decrypt properties during the configuration bootstrap phase (was: Encrypt/Decrypt auth module configurations selectively) > allow WA to decrypt properties during the configuration bootstrap phase > --- > > Key: SYNCOPE-1765 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1765 > Project: Syncope > Issue Type: Improvement > Components: core, wa >Affects Versions: 3.0.0, 3.0.1, 3.0.2, 3.0.3 >Reporter: Misagh Moayyed >Assignee: Misagh Moayyed >Priority: Major > Fix For: 3.0.4, 4.0.0 > > > Allow each AuthModuleConf component to selectively encrypt/decrypt > values/settings before the final conf is stored in the syncope database. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (SYNCOPE-1765) Encrypt/Decrypt auth module configurations selectively
Misagh Moayyed created SYNCOPE-1765: --- Summary: Encrypt/Decrypt auth module configurations selectively Key: SYNCOPE-1765 URL: https://issues.apache.org/jira/browse/SYNCOPE-1765 Project: Syncope Issue Type: Improvement Components: core, wa Affects Versions: 3.0.3, 3.0.2, 3.0.1, 3.0.0 Reporter: Misagh Moayyed Assignee: Misagh Moayyed Fix For: 3.0.4, 4.0.0 Allow each AuthModuleConf component to selectively encrypt/decrypt values/settings before the final conf is stored in the syncope database. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (SYNCOPE-1722) Allow password fields to reveal their value to the end-user
[ https://issues.apache.org/jira/browse/SYNCOPE-1722?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Misagh Moayyed updated SYNCOPE-1722: Fix Version/s: 2.1.14 3.0.2 > Allow password fields to reveal their value to the end-user > --- > > Key: SYNCOPE-1722 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1722 > Project: Syncope > Issue Type: Improvement > Components: console, enduser >Affects Versions: 2.1.13, 3.0.0 >Reporter: Misagh Moayyed >Assignee: Misagh Moayyed >Priority: Major > Fix For: 2.1.14, 3.0.2 > > > Provide an option so the password field can switch its type from password to > text and back, allowing the user to see the value. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (SYNCOPE-1722) Allow password fields to reveal their value to the end-user
[ https://issues.apache.org/jira/browse/SYNCOPE-1722?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Misagh Moayyed updated SYNCOPE-1722: Affects Version/s: 3.0.0 2.1.13 > Allow password fields to reveal their value to the end-user > --- > > Key: SYNCOPE-1722 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1722 > Project: Syncope > Issue Type: Improvement > Components: console, enduser >Affects Versions: 2.1.13, 3.0.0 >Reporter: Misagh Moayyed >Assignee: Misagh Moayyed >Priority: Major > > Provide an option so the password field can switch its type from password to > text and back, allowing the user to see the value. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (SYNCOPE-1722) Allow password fields to reveal their value to the end-user
[ https://issues.apache.org/jira/browse/SYNCOPE-1722?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Misagh Moayyed updated SYNCOPE-1722: Component/s: console > Allow password fields to reveal their value to the end-user > --- > > Key: SYNCOPE-1722 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1722 > Project: Syncope > Issue Type: Improvement > Components: console, enduser >Reporter: Misagh Moayyed >Assignee: Misagh Moayyed >Priority: Major > > Provide an option so the password field can switch its type from password to > text and back, allowing the user to see the value. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (SYNCOPE-1722) Allow password fields to reveal their value to the end-user
Misagh Moayyed created SYNCOPE-1722: --- Summary: Allow password fields to reveal their value to the end-user Key: SYNCOPE-1722 URL: https://issues.apache.org/jira/browse/SYNCOPE-1722 Project: Syncope Issue Type: Improvement Components: enduser Reporter: Misagh Moayyed Assignee: Misagh Moayyed Provide an option so the password field can switch its type from password to text and back, allowing the user to see the value. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (SYNCOPE-1709) Persist Jobs' current status in the database to support multi-node deployments
[ https://issues.apache.org/jira/browse/SYNCOPE-1709?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Misagh Moayyed resolved SYNCOPE-1709. - Resolution: Fixed > Persist Jobs' current status in the database to support multi-node > deployments > --- > > Key: SYNCOPE-1709 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1709 > Project: Syncope > Issue Type: Improvement >Affects Versions: 2.1.12, 3.0.0-M2 >Reporter: Misagh Moayyed >Assignee: Misagh Moayyed >Priority: Major > Fix For: 2.1.13, 3.0.1 > > > When jobs, particularly (long-running) reports, are scheduled/asked to run > and there are multiple Syncope core nodes available in the cluster, the > current method of obtaining the job status via Spring and Quartz fails to > report back the status accurately, specially when the job bean is scheduled > on one node and the status check query is performed on another. > To support this scenario, job status details would be persisted in the > backend database in a new table, and the job engine would be responsible to > add/update/delete details in this table. Status query checks would then look > into this table to report back current status instead of obtaining the status > from the Spring bean responsible for execution. > it was discussed that the initial changeset would go into master and be > targeted to Syncope v3, and then may be backported to 2.x pending feasibility > and complication. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (SYNCOPE-1709) Persist Jobs' current status in the database to support multi-node deployments
Misagh Moayyed created SYNCOPE-1709: --- Summary: Persist Jobs' current status in the database to support multi-node deployments Key: SYNCOPE-1709 URL: https://issues.apache.org/jira/browse/SYNCOPE-1709 Project: Syncope Issue Type: Improvement Affects Versions: 3.0.0-M2, 2.1.12 Reporter: Misagh Moayyed Assignee: Misagh Moayyed Fix For: 3.0.0, 2.1.12 When jobs, particularly (long-running) reports, are scheduled/asked to run and there are multiple Syncope core nodes available in the cluster, the current method of obtaining the job status via Spring and Quartz fails to report back the status accurately, specially when the job bean is scheduled on one node and the status check query is performed on another. To support this scenario, job status details would be persisted in the backend database in a new table, and the job engine would be responsible to add/update/delete details in this table. Status query checks would then look into this table to report back current status instead of obtaining the status from the Spring bean responsible for execution. it was discussed that the initial changeset would go into master and be targeted to Syncope v3, and then may be backported to 2.x pending feasibility and complication. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (SYNCOPE-1699) Extract key from path for UserUpdate ops if undefined in request body
[ https://issues.apache.org/jira/browse/SYNCOPE-1699?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Misagh Moayyed resolved SYNCOPE-1699. - Resolution: Fixed > Extract key from path for UserUpdate ops if undefined in request body > - > > Key: SYNCOPE-1699 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1699 > Project: Syncope > Issue Type: Improvement > Components: core >Affects Versions: 3.0.0-M0 >Reporter: Misagh Moayyed >Assignee: Misagh Moayyed >Priority: Minor > Fix For: 3.0.0-M1, 3.0.0 > > > If a user-update operations via a PATCH (i.e. PATCH /users/key) does not > specify a key in the request body, this key should be extracted from the > path. The extracted key in the body must always equal the key in the path. In > the event that a key does not match or cannot be found, a 400 BAD REQUEST > error should be returned. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (SYNCOPE-1699) Extract key from path for UserUpdate ops if undefined in request body
[ https://issues.apache.org/jira/browse/SYNCOPE-1699?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Misagh Moayyed updated SYNCOPE-1699: Summary: Extract key from path for UserUpdate ops if undefined in request body (was: Extract key from path for UserUpdate Ops if undefined in request body) > Extract key from path for UserUpdate ops if undefined in request body > - > > Key: SYNCOPE-1699 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1699 > Project: Syncope > Issue Type: Improvement > Components: core >Affects Versions: 3.0.0-M0 >Reporter: Misagh Moayyed >Assignee: Misagh Moayyed >Priority: Minor > Fix For: 3.0.0-M1, 3.0.0 > > > If a user-update operations via a PATCH (i.e. PATCH /users/key) does not > specify a key in the request body, this key should be extracted from the > path. The extracted key in the body must always equal the key in the path. In > the event that a key does not match or cannot be found, a 400 BAD REQUEST > error should be returned. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (SYNCOPE-1699) Extract key from path for UserUpdate Ops if undefined in request body
Misagh Moayyed created SYNCOPE-1699: --- Summary: Extract key from path for UserUpdate Ops if undefined in request body Key: SYNCOPE-1699 URL: https://issues.apache.org/jira/browse/SYNCOPE-1699 Project: Syncope Issue Type: Improvement Components: core Affects Versions: 3.0.0-M0 Reporter: Misagh Moayyed Assignee: Misagh Moayyed Fix For: 3.0.0-M1, 3.0.0 If a user-update operations via a PATCH (i.e. PATCH /users/key) does not specify a key in the request body, this key should be extracted from the path. The extracted key in the body must always equal the key in the path. In the event that a key does not match or cannot be found, a 400 BAD REQUEST error should be returned. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (SYNCOPE-1681) Support LDAP Google Auth Tokens/Accounts in WA
[ https://issues.apache.org/jira/browse/SYNCOPE-1681?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Misagh Moayyed resolved SYNCOPE-1681. - Resolution: Fixed > Support LDAP Google Auth Tokens/Accounts in WA > -- > > Key: SYNCOPE-1681 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1681 > Project: Syncope > Issue Type: New Feature > Components: wa >Affects Versions: 3.0.0 >Reporter: Misagh Moayyed >Assignee: Misagh Moayyed >Priority: Major > Fix For: 3.0.0 > > > Registration records, tokens, etc that are relevant for google authenticator > as an mfa provider should be optionally stored in an LDAP backend for Syncope > WA. > The LDAP support for GAuth already exists: > [https://apereo.github.io/cas/6.5.x/mfa/GoogleAuthenticator-Authentication-Registration-LDAP.html] > > The task here is to augment the google auth configuration to support > appropriate LDAP settings, and then conditionally activate the module when > settings specified. If settings are undefined, we defer to Syncope as the > backend service (which is the default today) -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Created] (SYNCOPE-1681) Support LDAP Google Auth Tokens/Accounts in WA
Misagh Moayyed created SYNCOPE-1681: --- Summary: Support LDAP Google Auth Tokens/Accounts in WA Key: SYNCOPE-1681 URL: https://issues.apache.org/jira/browse/SYNCOPE-1681 Project: Syncope Issue Type: New Feature Components: wa Affects Versions: 3.0.0 Reporter: Misagh Moayyed Assignee: Misagh Moayyed Fix For: 3.0.0 Registration records, tokens, etc that are relevant for google authenticator as an mfa provider should be optionally stored in an LDAP backend for Syncope WA. The LDAP support for GAuth already exists: [https://apereo.github.io/cas/6.5.x/mfa/GoogleAuthenticator-Authentication-Registration-LDAP.html] The task here is to augment the google auth configuration to support appropriate LDAP settings, and then conditionally activate the module when settings specified. If settings are undefined, we defer to Syncope as the backend service (which is the default today) -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Resolved] (SYNCOPE-1680) Support Simple MFA as an MFA Provider in WA
[ https://issues.apache.org/jira/browse/SYNCOPE-1680?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Misagh Moayyed resolved SYNCOPE-1680. - Resolution: Fixed > Support Simple MFA as an MFA Provider in WA > --- > > Key: SYNCOPE-1680 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1680 > Project: Syncope > Issue Type: New Feature > Components: wa >Affects Versions: 3.0.0 >Reporter: Misagh Moayyed >Assignee: Misagh Moayyed >Priority: Major > Fix For: 3.0.0 > > > Allow WA to act as a multifactor authentication provider on its own, issuing > tokens and sending them to end-users via pre-defined communication channels > such as email or text messages. Tokens issued by WA are tracked using the > [ticket > registry|https://apereo.github.io/cas/6.5.x/ticketing/Configuring-Ticketing-Components.html] > and are assigned a configurable expiration policy controlled via WA settings. > See: > https://apereo.github.io/cas/6.5.x/mfa/Simple-Multifactor-Authentication.html -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Created] (SYNCOPE-1680) Support Simple MFA as an MFA Provider in WA
Misagh Moayyed created SYNCOPE-1680: --- Summary: Support Simple MFA as an MFA Provider in WA Key: SYNCOPE-1680 URL: https://issues.apache.org/jira/browse/SYNCOPE-1680 Project: Syncope Issue Type: New Feature Components: wa Affects Versions: 3.0.0 Reporter: Misagh Moayyed Assignee: Misagh Moayyed Fix For: 3.0.0 Allow WA to act as a multifactor authentication provider on its own, issuing tokens and sending them to end-users via pre-defined communication channels such as email or text messages. Tokens issued by WA are tracked using the [ticket registry|https://apereo.github.io/cas/6.5.x/ticketing/Configuring-Ticketing-Components.html] and are assigned a configurable expiration policy controlled via WA settings. See: https://apereo.github.io/cas/6.5.x/mfa/Simple-Multifactor-Authentication.html -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Commented] (SYNCOPE-1626) rename package org.apache.syncope.common.keymaster.client.zookeper to zookeeper
[
https://issues.apache.org/jira/browse/SYNCOPE-1626?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17314704#comment-17314704
]
Misagh Moayyed commented on SYNCOPE-1626:
-
Great. Thanks for the clarification!
> rename package org.apache.syncope.common.keymaster.client.zookeper to
> zookeeper
> ---
>
> Key: SYNCOPE-1626
> URL: https://issues.apache.org/jira/browse/SYNCOPE-1626
> Project: Syncope
> Issue Type: Bug
> Components: keymaster
>Reporter: Josh Soref
>Assignee: Francesco Chicchiriccò
>Priority: Trivial
> Fix For: 3.0.0
>
>
> I understand that classes like to last forever, but,
> [https://zookeeper.apache.org/]
> {quote}Welcome to Apache ZooKeeper™
> Apache ZooKeeper is an effort to develop and maintain an open-source server
> which enables highly reliable distributed coordination.
> What is ZooKeeper?
> {quote}
> Wouldn't it be nice if the brand of another ASF project was spelled correctly?
> For reference:
> [https://github.com/search?q=org%3Aapache+ZOOKEPER=Code]
> 270 code results
>
> [https://github.com/search?q=org%3Aapache+ZOOKEEPER=Code]
> 39,245 code results
> I normally run project wide spelling fixes, but I'm currently trying to get
> Apache Hive fixed up, and that's not making fast progress
> (https://issues.apache.org/jira/browse/HIVE-24390), so I don't expect to
> visit this project anytime soon.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Closed] (SYNCOPE-1626) rename package org.apache.syncope.common.keymaster.client.zookeper to zookeeper
[
https://issues.apache.org/jira/browse/SYNCOPE-1626?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Misagh Moayyed closed SYNCOPE-1626.
---
Resolution: Invalid
If you have a specific example in Apache Syncope that misspells zookeeper,
please be specific.
> rename package org.apache.syncope.common.keymaster.client.zookeper to
> zookeeper
> ---
>
> Key: SYNCOPE-1626
> URL: https://issues.apache.org/jira/browse/SYNCOPE-1626
> Project: Syncope
> Issue Type: Bug
> Components: keymaster
>Reporter: Josh Soref
>Priority: Trivial
>
> I understand that classes like to last forever, but,
> [https://zookeeper.apache.org/]
> {quote}Welcome to Apache ZooKeeper™
> Apache ZooKeeper is an effort to develop and maintain an open-source server
> which enables highly reliable distributed coordination.
> What is ZooKeeper?
> {quote}
> Wouldn't it be nice if the brand of another ASF project was spelled correctly?
> For reference:
> [https://github.com/search?q=org%3Aapache+ZOOKEPER=Code]
> 270 code results
>
> [https://github.com/search?q=org%3Aapache+ZOOKEEPER=Code]
> 39,245 code results
> I normally run project wide spelling fixes, but I'm currently trying to get
> Apache Hive fixed up, and that's not making fast progress
> (https://issues.apache.org/jira/browse/HIVE-24390), so I don't expect to
> visit this project anytime soon.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Resolved] (SYNCOPE-1625) Support impersonation for Web Access
[ https://issues.apache.org/jira/browse/SYNCOPE-1625?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Misagh Moayyed resolved SYNCOPE-1625. - Resolution: Fixed > Support impersonation for Web Access > > > Key: SYNCOPE-1625 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1625 > Project: Syncope > Issue Type: Sub-task > Components: wa >Affects Versions: 3.0.0 >Reporter: Misagh Moayyed >Assignee: Misagh Moayyed >Priority: Major > Fix For: 3.0.0 > > > Allow Web Access to support impersonation of accounts for login. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (SYNCOPE-1625) Support impersonation for Web Access
Misagh Moayyed created SYNCOPE-1625: --- Summary: Support impersonation for Web Access Key: SYNCOPE-1625 URL: https://issues.apache.org/jira/browse/SYNCOPE-1625 Project: Syncope Issue Type: Sub-task Components: wa Affects Versions: 3.0.0 Reporter: Misagh Moayyed Assignee: Misagh Moayyed Fix For: 3.0.0 Allow Web Access to support impersonation of accounts for login. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (SYNCOPE-1618) Use Constructor-level dependency injections
[ https://issues.apache.org/jira/browse/SYNCOPE-1618?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Misagh Moayyed updated SYNCOPE-1618: Description: See [syncope-dev|http://example.com] discussion at [https://lists.apache.org/thread.html/r99530cad4c763eb8d97f52575be46ed74f088cd43271600b0b1d7ee2%40%3Cdev.syncope.apache.org%3E] In summary: * Avoid field-injections and use ctor-level injections (this is the general recommendation from Spring) * Do not use autowire/component/etc directly in business-level classes; do not rely as much (if ever) on classpath/context scanning and instead, create and instantiate the bean directory in @Configuration classes, conditionally and with direct control was: See syncope-dev discussion at [https://lists.apache.org/thread.html/r99530cad4c763eb8d97f52575be46ed74f088cd43271600b0b1d7ee2%40%3Cdev.syncope.apache.org%3E] In summary: * Avoid field-injections and use ctor-level injections (this is the general recommendation from Spring) * Do not use autowire/component/etc directly in business-level classes; do not rely as much (if ever) on classpath/context scanning and instead, create and instantiate the bean directory in @Configuration classes, conditionally and with direct control > Use Constructor-level dependency injections > --- > > Key: SYNCOPE-1618 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1618 > Project: Syncope > Issue Type: Task > Components: common, console, core, sra, wa >Affects Versions: 2.1.8 >Reporter: Misagh Moayyed >Priority: Major > Fix For: 3.0.0 > > > See [syncope-dev|http://example.com] discussion at > [https://lists.apache.org/thread.html/r99530cad4c763eb8d97f52575be46ed74f088cd43271600b0b1d7ee2%40%3Cdev.syncope.apache.org%3E] > In summary: > * Avoid field-injections and use ctor-level injections (this is the general > recommendation from Spring) > * Do not use autowire/component/etc directly in business-level classes; do > not rely as much (if ever) on classpath/context scanning and instead, create > and instantiate the bean directory in @Configuration classes, conditionally > and with direct control > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (SYNCOPE-1618) Use Constructor-level dependency injections
[ https://issues.apache.org/jira/browse/SYNCOPE-1618?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Misagh Moayyed updated SYNCOPE-1618: Description: See [syncope-dev|https://lists.apache.org/thread.html/r99530cad4c763eb8d97f52575be46ed74f088cd43271600b0b1d7ee2%40%3Cdev.syncope.apache.org%3E] discussion. In summary: * Avoid field-injections and use ctor-level injections (this is the general recommendation from Spring) * Do not use autowire/component/etc directly in business-level classes; do not rely as much (if ever) on classpath/context scanning and instead, create and instantiate the bean directory in @Configuration classes, conditionally and with direct control was: See [syncope-dev|http://example.com] discussion at [https://lists.apache.org/thread.html/r99530cad4c763eb8d97f52575be46ed74f088cd43271600b0b1d7ee2%40%3Cdev.syncope.apache.org%3E] In summary: * Avoid field-injections and use ctor-level injections (this is the general recommendation from Spring) * Do not use autowire/component/etc directly in business-level classes; do not rely as much (if ever) on classpath/context scanning and instead, create and instantiate the bean directory in @Configuration classes, conditionally and with direct control > Use Constructor-level dependency injections > --- > > Key: SYNCOPE-1618 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1618 > Project: Syncope > Issue Type: Task > Components: common, console, core, sra, wa >Affects Versions: 2.1.8 >Reporter: Misagh Moayyed >Priority: Major > Fix For: 3.0.0 > > > See > [syncope-dev|https://lists.apache.org/thread.html/r99530cad4c763eb8d97f52575be46ed74f088cd43271600b0b1d7ee2%40%3Cdev.syncope.apache.org%3E] > discussion. > In summary: > * Avoid field-injections and use ctor-level injections (this is the general > recommendation from Spring) > * Do not use autowire/component/etc directly in business-level classes; do > not rely as much (if ever) on classpath/context scanning and instead, create > and instantiate the bean directory in @Configuration classes, conditionally > and with direct control > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (SYNCOPE-1618) Use Constructor-level dependency injections
[ https://issues.apache.org/jira/browse/SYNCOPE-1618?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Misagh Moayyed updated SYNCOPE-1618: Description: See syncope-dev discussion at [https://lists.apache.org/thread.html/r99530cad4c763eb8d97f52575be46ed74f088cd43271600b0b1d7ee2%40%3Cdev.syncope.apache.org%3E] In summary: * Avoid field-injections and use ctor-level injections (this is the general recommendation from Spring) * Do not use autowire/component/etc directly in business-level classes; do not rely as much (if ever) on classpath/context scanning and instead, create and instantiate the bean directory in @Configuration classes, conditionally and with direct control was: See [syncope-dev discussion at [https://lists.apache.org/thread.html/r99530cad4c763eb8d97f52575be46ed74f088cd43271600b0b1d7ee2%40%3Cdev.syncope.apache.org%3E] In summary: * Avoid field-injections and use ctor-level injections (this is the general recommendation from Spring) * Do not use autowire/component/etc directly in business-level classes; do not rely as much (if ever) on classpath/context scanning and instead, create and instantiate the bean directory in @Configuration classes, conditionally and with direct control > Use Constructor-level dependency injections > --- > > Key: SYNCOPE-1618 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1618 > Project: Syncope > Issue Type: Task > Components: common, console, core, sra, wa >Affects Versions: 2.1.8 >Reporter: Misagh Moayyed >Priority: Major > Fix For: 3.0.0 > > > See syncope-dev discussion at > [https://lists.apache.org/thread.html/r99530cad4c763eb8d97f52575be46ed74f088cd43271600b0b1d7ee2%40%3Cdev.syncope.apache.org%3E] > In summary: > * Avoid field-injections and use ctor-level injections (this is the general > recommendation from Spring) > * Do not use autowire/component/etc directly in business-level classes; do > not rely as much (if ever) on classpath/context scanning and instead, create > and instantiate the bean directory in @Configuration classes, conditionally > and with direct control > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (SYNCOPE-1618) Use Constructor-level dependency injections
[ https://issues.apache.org/jira/browse/SYNCOPE-1618?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Misagh Moayyed updated SYNCOPE-1618: Issue Type: Task (was: Improvement) > Use Constructor-level dependency injections > --- > > Key: SYNCOPE-1618 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1618 > Project: Syncope > Issue Type: Task > Components: common, console, core, sra, wa >Affects Versions: 2.1.8 >Reporter: Misagh Moayyed >Priority: Major > Fix For: 3.0.0 > > > See [syncope-dev discussion at > [https://lists.apache.org/thread.html/r99530cad4c763eb8d97f52575be46ed74f088cd43271600b0b1d7ee2%40%3Cdev.syncope.apache.org%3E] > In summary: > * Avoid field-injections and use ctor-level injections (this is the general > recommendation from Spring) > * Do not use autowire/component/etc directly in business-level classes; do > not rely as much (if ever) on classpath/context scanning and instead, create > and instantiate the bean directory in @Configuration classes, conditionally > and with direct control > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (SYNCOPE-1618) Use Constructor-level dependency injections
Misagh Moayyed created SYNCOPE-1618: --- Summary: Use Constructor-level dependency injections Key: SYNCOPE-1618 URL: https://issues.apache.org/jira/browse/SYNCOPE-1618 Project: Syncope Issue Type: Improvement Components: common, console, core, sra, wa Affects Versions: 2.1.8 Reporter: Misagh Moayyed Fix For: 3.0.0 See [syncope-dev discussion|[https://lists.apache.org/thread.html/r99530cad4c763eb8d97f52575be46ed74f088cd43271600b0b1d7ee2%40%3Cdev.syncope.apache.org%3E].] In summary: * Avoid field-injections and use ctor-level injections (this is the general recommendation from Spring) * Do not use autowire/component/etc directly in business-level classes; do not rely as much (if ever) on classpath/context scanning and instead, create and instantiate the bean directory in @Configuration classes, conditionally and with direct control -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (SYNCOPE-1618) Use Constructor-level dependency injections
[ https://issues.apache.org/jira/browse/SYNCOPE-1618?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Misagh Moayyed updated SYNCOPE-1618: Description: See [syncope-dev discussion at [https://lists.apache.org/thread.html/r99530cad4c763eb8d97f52575be46ed74f088cd43271600b0b1d7ee2%40%3Cdev.syncope.apache.org%3E] In summary: * Avoid field-injections and use ctor-level injections (this is the general recommendation from Spring) * Do not use autowire/component/etc directly in business-level classes; do not rely as much (if ever) on classpath/context scanning and instead, create and instantiate the bean directory in @Configuration classes, conditionally and with direct control was: See [syncope-dev discussion|[https://lists.apache.org/thread.html/r99530cad4c763eb8d97f52575be46ed74f088cd43271600b0b1d7ee2%40%3Cdev.syncope.apache.org%3E].] In summary: * Avoid field-injections and use ctor-level injections (this is the general recommendation from Spring) * Do not use autowire/component/etc directly in business-level classes; do not rely as much (if ever) on classpath/context scanning and instead, create and instantiate the bean directory in @Configuration classes, conditionally and with direct control > Use Constructor-level dependency injections > --- > > Key: SYNCOPE-1618 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1618 > Project: Syncope > Issue Type: Improvement > Components: common, console, core, sra, wa >Affects Versions: 2.1.8 >Reporter: Misagh Moayyed >Priority: Major > Fix For: 3.0.0 > > > See [syncope-dev discussion at > [https://lists.apache.org/thread.html/r99530cad4c763eb8d97f52575be46ed74f088cd43271600b0b1d7ee2%40%3Cdev.syncope.apache.org%3E] > In summary: > * Avoid field-injections and use ctor-level injections (this is the general > recommendation from Spring) > * Do not use autowire/component/etc directly in business-level classes; do > not rely as much (if ever) on classpath/context scanning and instead, create > and instantiate the bean directory in @Configuration classes, conditionally > and with direct control > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (SYNCOPE-1599) Support Duo Security for MFA
[ https://issues.apache.org/jira/browse/SYNCOPE-1599?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Misagh Moayyed resolved SYNCOPE-1599. - Resolution: Fixed > Support Duo Security for MFA > > > Key: SYNCOPE-1599 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1599 > Project: Syncope > Issue Type: Sub-task > Components: wa >Affects Versions: 3.0.0 >Reporter: Misagh Moayyed >Assignee: Misagh Moayyed >Priority: Major > Fix For: 3.0.0 > > > DuoSecurity is a very popular MFA provider specially in higher education and > K12 markets. Integration requires an active duo subscription, which allows > CAS/WA to provide MFA in form of webauthn, one-time codes, push notifications > and phone calls. Device registration and management is handled by Duo itself > and there is a built-in mechanism provided by Duo as part of the MFA flow to > handle account registrations. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (SYNCOPE-1599) Support Duo Security for MFA
Misagh Moayyed created SYNCOPE-1599: --- Summary: Support Duo Security for MFA Key: SYNCOPE-1599 URL: https://issues.apache.org/jira/browse/SYNCOPE-1599 Project: Syncope Issue Type: Sub-task Components: wa Affects Versions: 3.0.0 Reporter: Misagh Moayyed Assignee: Misagh Moayyed Fix For: 3.0.0 DuoSecurity is a very popular MFA provider specially in higher education and K12 markets. Integration requires an active duo subscription, which allows CAS/WA to provide MFA in form of webauthn, one-time codes, push notifications and phone calls. Device registration and management is handled by Duo itself and there is a built-in mechanism provided by Duo as part of the MFA flow to handle account registrations. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (SYNCOPE-1595) Support themes per client application
[ https://issues.apache.org/jira/browse/SYNCOPE-1595?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Misagh Moayyed resolved SYNCOPE-1595. - Resolution: Fixed > Support themes per client application > - > > Key: SYNCOPE-1595 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1595 > Project: Syncope > Issue Type: Sub-task > Components: wa >Affects Versions: 3.0.0 >Reporter: Misagh Moayyed >Assignee: Misagh Moayyed >Priority: Major > Fix For: 3.0.0 > > > Allow theme names to be defined for each client app, and possibly put > together a sample theme perhaps for WA to demonstrate functionality. > Furthermore, consider designing REST APIs that can allow CAS to fetch a full > view/page instead of relying on static predefined themes and css/html. A WA > user should be able to modify the contents of a given page/view, store that > page somewhere and let the Syncope REST API fetch that view if the client > application requires it. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (SYNCOPE-1595) Support themes per client application
Misagh Moayyed created SYNCOPE-1595: --- Summary: Support themes per client application Key: SYNCOPE-1595 URL: https://issues.apache.org/jira/browse/SYNCOPE-1595 Project: Syncope Issue Type: Sub-task Components: wa Affects Versions: 3.0.0 Reporter: Misagh Moayyed Assignee: Misagh Moayyed Fix For: 3.0.0 Allow theme names to be defined for each client app, and possibly put together a sample theme perhaps for WA to demonstrate functionality. Furthermore, consider designing REST APIs that can allow CAS to fetch a full view/page instead of relying on static predefined themes and css/html. A WA user should be able to modify the contents of a given page/view, store that page somewhere and let the Syncope REST API fetch that view if the client application requires it. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (SYNCOPE-1593) Allow SAML2 SPs to override signing/encryption algorithms
[ https://issues.apache.org/jira/browse/SYNCOPE-1593?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Misagh Moayyed resolved SYNCOPE-1593. - Resolution: Fixed > Allow SAML2 SPs to override signing/encryption algorithms > - > > Key: SYNCOPE-1593 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1593 > Project: Syncope > Issue Type: Sub-task > Components: wa >Affects Versions: 3.0.0 >Reporter: Misagh Moayyed >Assignee: Misagh Moayyed >Priority: Major > > Make sure SAML2 SPs in WA can have the ability to present their own > requirements for signing algos, or blocking algos, etc. (i.e. an SP might > require SHA-1 as the signing algorithm, or may want to block it) > > > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (SYNCOPE-1593) Allow SAML2 SPs to override signing/encryption algorithms
Misagh Moayyed created SYNCOPE-1593: --- Summary: Allow SAML2 SPs to override signing/encryption algorithms Key: SYNCOPE-1593 URL: https://issues.apache.org/jira/browse/SYNCOPE-1593 Project: Syncope Issue Type: Sub-task Components: wa Affects Versions: 3.0.0 Reporter: Misagh Moayyed Assignee: Misagh Moayyed Make sure SAML2 SPs in WA can have the ability to present their own requirements for signing algos, or blocking algos, etc. (i.e. an SP might require SHA-1 as the signing algorithm, or may want to block it) -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (SYNCOPE-1589) REST APIs to support WebAuthN device registration
[ https://issues.apache.org/jira/browse/SYNCOPE-1589?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Misagh Moayyed resolved SYNCOPE-1589. - Resolution: Fixed > REST APIs to support WebAuthN device registration > - > > Key: SYNCOPE-1589 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1589 > Project: Syncope > Issue Type: Sub-task > Components: wa >Affects Versions: 3.0.0 >Reporter: Misagh Moayyed >Assignee: Misagh Moayyed >Priority: Major > > Design REST APIs, etc to allow device registration requests via WebAuthN MFA. > This would be, in concept, similar to how GAUTH works. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (SYNCOPE-1589) REST APIs to support WebAuthN device registration
Misagh Moayyed created SYNCOPE-1589: --- Summary: REST APIs to support WebAuthN device registration Key: SYNCOPE-1589 URL: https://issues.apache.org/jira/browse/SYNCOPE-1589 Project: Syncope Issue Type: Sub-task Components: wa Affects Versions: 3.0.0 Reporter: Misagh Moayyed Assignee: Misagh Moayyed Design REST APIs, etc to allow device registration requests via WebAuthN MFA. This would be, in concept, similar to how GAUTH works. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (SYNCOPE-1587) Enable Web AuthN support for WA
[ https://issues.apache.org/jira/browse/SYNCOPE-1587?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Misagh Moayyed resolved SYNCOPE-1587. - Resolution: Fixed > Enable Web AuthN support for WA > --- > > Key: SYNCOPE-1587 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1587 > Project: Syncope > Issue Type: Sub-task > Components: wa >Affects Versions: 3.0.0 >Reporter: Misagh Moayyed >Assignee: Misagh Moayyed >Priority: Major > Fix For: 3.0.0 > > > Modify the Syncope WA build to turn on basic support for FIDO2/web-authn. > Doing so allows the WA module to enable Web AuthN support for MFA requests, > depending on available MFA triggers. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (SYNCOPE-1587) Enable Web AuthN support for WA
[ https://issues.apache.org/jira/browse/SYNCOPE-1587?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Misagh Moayyed updated SYNCOPE-1587: Description: Modify the Syncope WA build to turn on basic support for FIDO2/web-authn. Doing so allows the WA module to enable Web AuthN support for MFA requests, depending on available MFA triggers. (was: Modify the build to turn on basic support for FIDO2/web-authn) > Enable Web AuthN support for WA > --- > > Key: SYNCOPE-1587 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1587 > Project: Syncope > Issue Type: Sub-task > Components: wa >Affects Versions: 3.0.0 >Reporter: Misagh Moayyed >Assignee: Misagh Moayyed >Priority: Major > Fix For: 3.0.0 > > > Modify the Syncope WA build to turn on basic support for FIDO2/web-authn. > Doing so allows the WA module to enable Web AuthN support for MFA requests, > depending on available MFA triggers. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (SYNCOPE-1587) Enable webauthn support for WA
Misagh Moayyed created SYNCOPE-1587: --- Summary: Enable webauthn support for WA Key: SYNCOPE-1587 URL: https://issues.apache.org/jira/browse/SYNCOPE-1587 Project: Syncope Issue Type: Sub-task Components: wa Affects Versions: 3.0.0 Reporter: Misagh Moayyed Assignee: Misagh Moayyed Fix For: 3.0.0 Modify the build to turn on basic support for FIDO2/web-authn -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (SYNCOPE-1587) Enable Web AuthN support for WA
[ https://issues.apache.org/jira/browse/SYNCOPE-1587?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Misagh Moayyed updated SYNCOPE-1587: Summary: Enable Web AuthN support for WA (was: Enable webauthn support for WA) > Enable Web AuthN support for WA > --- > > Key: SYNCOPE-1587 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1587 > Project: Syncope > Issue Type: Sub-task > Components: wa >Affects Versions: 3.0.0 >Reporter: Misagh Moayyed >Assignee: Misagh Moayyed >Priority: Major > Fix For: 3.0.0 > > > Modify the build to turn on basic support for FIDO2/web-authn -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (SYNCOPE-1580) Design WA REST APIs to configure configuration properties
[ https://issues.apache.org/jira/browse/SYNCOPE-1580?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Misagh Moayyed resolved SYNCOPE-1580. - Resolution: Fixed > Design WA REST APIs to configure configuration properties > - > > Key: SYNCOPE-1580 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1580 > Project: Syncope > Issue Type: Sub-task > Components: wa >Affects Versions: 3.0.0 >Reporter: Misagh Moayyed >Assignee: Misagh Moayyed >Priority: Major > Fix For: 3.0.0 > > > Define REST endpoints and relevant data structures allowing WA to set and > configure properties such as the OIDC issuer, etc. The endpoints should be > sufficiently protected so they can be called from the command-line or the > admin-UI once UI support is built. Once a property value is stored, WA should > be asked to refresh its context to fetch the setting and resume without > having to rebuild or restart the container, etc. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (SYNCOPE-1580) Design WA REST APIs to configure configuration properties
Misagh Moayyed created SYNCOPE-1580: --- Summary: Design WA REST APIs to configure configuration properties Key: SYNCOPE-1580 URL: https://issues.apache.org/jira/browse/SYNCOPE-1580 Project: Syncope Issue Type: Sub-task Components: wa Affects Versions: 3.0.0 Reporter: Misagh Moayyed Assignee: Misagh Moayyed Fix For: 3.0.0 Define REST endpoints and relevant data structures allowing WA to set and configure properties such as the OIDC issuer, etc. The endpoints should be sufficiently protected so they can be called from the command-line or the admin-UI once UI support is built. Once a property value is stored, WA should be asked to refresh its context to fetch the setting and resume without having to rebuild or restart the container, etc. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (SYNCOPE-1577) Support CAS-enabled client applications
[ https://issues.apache.org/jira/browse/SYNCOPE-1577?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Misagh Moayyed resolved SYNCOPE-1577. - Resolution: Fixed > Support CAS-enabled client applications > --- > > Key: SYNCOPE-1577 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1577 > Project: Syncope > Issue Type: Sub-task > Components: wa >Affects Versions: 3.0.0 >Reporter: Misagh Moayyed >Assignee: Misagh Moayyed >Priority: Major > Fix For: 3.0.0 > > > Allow WA to act as a CAS-enabled identity provider for CAS-enabled client > applications using the CAS protocol -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (SYNCOPE-1577) Support CAS-enabled client applications
Misagh Moayyed created SYNCOPE-1577: --- Summary: Support CAS-enabled client applications Key: SYNCOPE-1577 URL: https://issues.apache.org/jira/browse/SYNCOPE-1577 Project: Syncope Issue Type: Sub-task Components: wa Affects Versions: 3.0.0 Reporter: Misagh Moayyed Assignee: Misagh Moayyed Fix For: 3.0.0 Allow WA to act as a CAS-enabled identity provider for CAS-enabled client applications using the CAS protocol -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (SYNCOPE-1571) Support U2F MFA tokens/requests via REST APIs
[ https://issues.apache.org/jira/browse/SYNCOPE-1571?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Misagh Moayyed resolved SYNCOPE-1571. - Resolution: Fixed > Support U2F MFA tokens/requests via REST APIs > - > > Key: SYNCOPE-1571 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1571 > Project: Syncope > Issue Type: Sub-task > Components: wa >Affects Versions: 3.0.0 >Reporter: Misagh Moayyed >Assignee: Misagh Moayyed >Priority: Major > Fix For: 3.0.0 > > > U2F mfa authentication requests/responses should be managed via dedicated > endpoints and REST APIs, similar to how GoogleAuth functionality works in WA. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (SYNCOPE-1570) Support U2F device registration via REST APIs
[ https://issues.apache.org/jira/browse/SYNCOPE-1570?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Misagh Moayyed resolved SYNCOPE-1570. - Resolution: Fixed > Support U2F device registration via REST APIs > - > > Key: SYNCOPE-1570 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1570 > Project: Syncope > Issue Type: Sub-task > Components: wa >Affects Versions: 3.0.0 >Reporter: Misagh Moayyed >Assignee: Misagh Moayyed >Priority: Major > Fix For: 3.0.0 > > > Allow the WA module to handle device registrations for U2F MFA via dedicated > APIs and REST endpoints. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (SYNCOPE-1571) Support U2F MFA tokens/requests via REST APIs
Misagh Moayyed created SYNCOPE-1571: --- Summary: Support U2F MFA tokens/requests via REST APIs Key: SYNCOPE-1571 URL: https://issues.apache.org/jira/browse/SYNCOPE-1571 Project: Syncope Issue Type: Sub-task Components: wa Affects Versions: 3.0.0 Reporter: Misagh Moayyed Assignee: Misagh Moayyed Fix For: 3.0.0 U2F mfa authentication requests/responses should be managed via dedicated endpoints and REST APIs, similar to how GoogleAuth functionality works in WA. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (SYNCOPE-1570) Support U2F device registration via REST APIs
Misagh Moayyed created SYNCOPE-1570: --- Summary: Support U2F device registration via REST APIs Key: SYNCOPE-1570 URL: https://issues.apache.org/jira/browse/SYNCOPE-1570 Project: Syncope Issue Type: Sub-task Components: wa Affects Versions: 3.0.0 Reporter: Misagh Moayyed Assignee: Misagh Moayyed Fix For: 3.0.0 Allow the WA module to handle device registrations for U2F MFA via dedicated APIs and REST endpoints. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (SYNCOPE-1556) Allow WA as OIDC OP to fetch JWKS over REST
[ https://issues.apache.org/jira/browse/SYNCOPE-1556?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Misagh Moayyed resolved SYNCOPE-1556. - Resolution: Fixed > Allow WA as OIDC OP to fetch JWKS over REST > --- > > Key: SYNCOPE-1556 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1556 > Project: Syncope > Issue Type: Sub-task > Components: core, wa >Affects Versions: 3.0.0 >Reporter: Matteo Alessandroni >Assignee: Misagh Moayyed >Priority: Major > Fix For: 3.0.0 > > > WA when running as an OIDC OP must be able to fetch its JWKS from a rest > endpoint -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (SYNCOPE-1556) Allow WA as OIDC OP to fetch JWKS over REST
[ https://issues.apache.org/jira/browse/SYNCOPE-1556?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Misagh Moayyed reassigned SYNCOPE-1556: --- Assignee: Misagh Moayyed (was: Matteo Alessandroni) > Allow WA as OIDC OP to fetch JWKS over REST > --- > > Key: SYNCOPE-1556 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1556 > Project: Syncope > Issue Type: Sub-task > Components: core, wa >Affects Versions: 3.0.0 >Reporter: Matteo Alessandroni >Assignee: Misagh Moayyed >Priority: Major > Fix For: 3.0.0 > > > WA when running as an OIDC OP must be able to fetch its JWKS from a rest > endpoint -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (SYNCOPE-1566) Manage device registration records for GoogleAuthMFA
[ https://issues.apache.org/jira/browse/SYNCOPE-1566?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Misagh Moayyed resolved SYNCOPE-1566. - Resolution: Fixed > Manage device registration records for GoogleAuthMFA > > > Key: SYNCOPE-1566 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1566 > Project: Syncope > Issue Type: Sub-task > Components: wa >Affects Versions: 3.0.0 >Reporter: Misagh Moayyed >Assignee: Misagh Moayyed >Priority: Major > Fix For: 3.0.0 > > > The Google Authenticator MFA functionality allows users to register/onboard > devices to then begin with MFA and TOTP codes, etc. These device records > should be stored in Syncope managed via dedicated endpoints and APIs. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (SYNCOPE-1562) Handle OTP records for GoogleAuthN MFA
[ https://issues.apache.org/jira/browse/SYNCOPE-1562?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Misagh Moayyed resolved SYNCOPE-1562. - Resolution: Fixed > Handle OTP records for GoogleAuthN MFA > -- > > Key: SYNCOPE-1562 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1562 > Project: Syncope > Issue Type: Sub-task > Components: wa >Affects Versions: 3.0.0 >Reporter: Misagh Moayyed >Assignee: Misagh Moayyed >Priority: Major > Fix For: 3.0.0 > > > The Google Authenticator MFA functionality allows users to register/onboard > devices to then begin with MFA and TOTP codes, etc. These tokens/codes should > be stored in Syncope managed via dedicated endpoints and APIs. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (SYNCOPE-1566) Manage device registration records for GoogleAuthMFA
Misagh Moayyed created SYNCOPE-1566: --- Summary: Manage device registration records for GoogleAuthMFA Key: SYNCOPE-1566 URL: https://issues.apache.org/jira/browse/SYNCOPE-1566 Project: Syncope Issue Type: Sub-task Components: wa Affects Versions: 3.0.0 Reporter: Misagh Moayyed Assignee: Misagh Moayyed Fix For: 3.0.0 The Google Authenticator MFA functionality allows users to register/onboard devices to then begin with MFA and TOTP codes, etc. These device records should be stored in Syncope managed via dedicated endpoints and APIs. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (SYNCOPE-1562) Handle OTP records for GoogleAuthN MFA
[ https://issues.apache.org/jira/browse/SYNCOPE-1562?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Misagh Moayyed updated SYNCOPE-1562: Description: The Google Authenticator MFA functionality allows users to register/onboard devices to then begin with MFA and TOTP codes, etc. These tokens/codes should be stored in Syncope managed via dedicated endpoints and APIs. (was: The Google Authenticator MFA functionality allows users to register/onboard devices to then begin with MFA and TOTP codes, etc. These registration records should be stored in Syncope managed via dedicated endpoints and APIs.) Summary: Handle OTP records for GoogleAuthN MFA (was: Handle device registration records for GoogleAuthN MFA) > Handle OTP records for GoogleAuthN MFA > -- > > Key: SYNCOPE-1562 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1562 > Project: Syncope > Issue Type: Sub-task > Components: wa >Affects Versions: 3.0.0 >Reporter: Misagh Moayyed >Assignee: Misagh Moayyed >Priority: Major > Fix For: 3.0.0 > > > The Google Authenticator MFA functionality allows users to register/onboard > devices to then begin with MFA and TOTP codes, etc. These tokens/codes should > be stored in Syncope managed via dedicated endpoints and APIs. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (SYNCOPE-1562) Handle device registration records for GoogleAuthN MFA
Misagh Moayyed created SYNCOPE-1562: --- Summary: Handle device registration records for GoogleAuthN MFA Key: SYNCOPE-1562 URL: https://issues.apache.org/jira/browse/SYNCOPE-1562 Project: Syncope Issue Type: Sub-task Components: wa Affects Versions: 3.0.0 Reporter: Misagh Moayyed Assignee: Misagh Moayyed Fix For: 3.0.0 The Google Authenticator MFA functionality allows users to register/onboard devices to then begin with MFA and TOTP codes, etc. These registration records should be stored in Syncope managed via dedicated endpoints and APIs. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (SYNCOPE-1559) Allow WA Google Auth MFA settings to become reloadable
[ https://issues.apache.org/jira/browse/SYNCOPE-1559?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Misagh Moayyed resolved SYNCOPE-1559. - Resolution: Fixed > Allow WA Google Auth MFA settings to become reloadable > -- > > Key: SYNCOPE-1559 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1559 > Project: Syncope > Issue Type: Sub-task > Components: wa >Affects Versions: 3.0.0 >Reporter: Misagh Moayyed >Assignee: Misagh Moayyed >Priority: Major > Fix For: 3.0.0 > > > The configuration of google authentication module for MFA in WA cannot be > refreshed today when settings change such as window-size, time-step, etc. > This is because the bean definition in WA/CAS that is built based on such > settings is not marked as RefreshScope, because the implementation class for > the GoogleAuthenticator component in WA/CAS belongs to a 3rd party library > that has marked the class as final. Final classes cannot be proxied via > RefreshScope. > Changes mainly will be done in CAS to find a workaround to mark the > GoogleAuthenticator bean with RefreshScope. When done, WA will receive the > fix for free automatically. > Also other beans in the same module should be reviewed to make sure all > required beans can be reloadable. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (SYNCOPE-1558) Configure WA delegated authn module to SAML IdPs via REST
[ https://issues.apache.org/jira/browse/SYNCOPE-1558?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Misagh Moayyed resolved SYNCOPE-1558. - Resolution: Fixed > Configure WA delegated authn module to SAML IdPs via REST > - > > Key: SYNCOPE-1558 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1558 > Project: Syncope > Issue Type: Sub-task > Components: wa >Affects Versions: 3.0.0 >Reporter: Misagh Moayyed >Assignee: Misagh Moayyed >Priority: Major > Fix For: 3.0.0 > > > When WA is configured to hand off authentication to an external SAML2 > identity provider via pac4j, pac4j expects a java keystore to be > created/present on disk that will be used by WA as a SAML SP to interact with > the IDP and to generate metadata, sign responses, etc. This keystore is > expected to be found on disk, and pac4j does not allow other options for > producing/fetching the keystore via REST. > Also, a number of other artifacts such as generation of SP metadata, etc > should be configurable over rest. > > Task is: > * Allow pac4j to open up its api/configuration to allow for keystore > fetching over rest > * Modify WA to use this configuration and produce keystore data over rest. > > Note that a similar and separate task may be created to handle the same > matter with delegated authn to OIDC OPs. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (SYNCOPE-1559) Allow WA Google Auth MFA settings to become reloadable
Misagh Moayyed created SYNCOPE-1559: --- Summary: Allow WA Google Auth MFA settings to become reloadable Key: SYNCOPE-1559 URL: https://issues.apache.org/jira/browse/SYNCOPE-1559 Project: Syncope Issue Type: Sub-task Components: wa Affects Versions: 3.0.0 Reporter: Misagh Moayyed Assignee: Misagh Moayyed Fix For: 3.0.0 The configuration of google authentication module for MFA in WA cannot be refreshed today when settings change such as window-size, time-step, etc. This is because the bean definition in WA/CAS that is built based on such settings is not marked as RefreshScope, because the implementation class for the GoogleAuthenticator component in WA/CAS belongs to a 3rd party library that has marked the class as final. Final classes cannot be proxied via RefreshScope. Changes mainly will be done in CAS to find a workaround to mark the GoogleAuthenticator bean with RefreshScope. When done, WA will receive the fix for free automatically. Also other beans in the same module should be reviewed to make sure all required beans can be reloadable. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (SYNCOPE-1496) Add integration tests for DBMSes via Docker
[ https://issues.apache.org/jira/browse/SYNCOPE-1496?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Misagh Moayyed reassigned SYNCOPE-1496: --- Assignee: Francesco Chicchiriccò (was: Misagh Moayyed) > Add integration tests for DBMSes via Docker > --- > > Key: SYNCOPE-1496 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1496 > Project: Syncope > Issue Type: Sub-task > Components: build-tools >Affects Versions: 3.0.0 >Reporter: Misagh Moayyed >Assignee: Francesco Chicchiriccò >Priority: Minor > Fix For: 3.0.0 > > > Integration tests for DBMSes should be turned on and added to Travis CI as an > independant job: > [https://syncope.apache.org/building#DBMSes] > This will of course require pulling down relevant docker images for each > build, and each DBMS may require to be its own job to avoid timeouts. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (SYNCOPE-1558) Configure WA delegated authn module to SAML IdPs via REST
[ https://issues.apache.org/jira/browse/SYNCOPE-1558?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17095519#comment-17095519 ] Misagh Moayyed commented on SYNCOPE-1558: - PR finalized and ready. 4.0.1 SNAPSHOT of pac4j should contain the change, and the change is pushed into the next snapshot release of CAS. Next, will fine-tune the WA configuration with the next CAS snapshot to take advantage of latest pac4j changes for SAML IDP config. > Configure WA delegated authn module to SAML IdPs via REST > - > > Key: SYNCOPE-1558 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1558 > Project: Syncope > Issue Type: Sub-task > Components: wa >Affects Versions: 3.0.0 >Reporter: Misagh Moayyed >Assignee: Misagh Moayyed >Priority: Major > Fix For: 3.0.0 > > > When WA is configured to hand off authentication to an external SAML2 > identity provider via pac4j, pac4j expects a java keystore to be > created/present on disk that will be used by WA as a SAML SP to interact with > the IDP and to generate metadata, sign responses, etc. This keystore is > expected to be found on disk, and pac4j does not allow other options for > producing/fetching the keystore via REST. > Also, a number of other artifacts such as generation of SP metadata, etc > should be configurable over rest. > > Task is: > * Allow pac4j to open up its api/configuration to allow for keystore > fetching over rest > * Modify WA to use this configuration and produce keystore data over rest. > > Note that a similar and separate task may be created to handle the same > matter with delegated authn to OIDC OPs. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (SYNCOPE-1558) Configure WA delegated authn module to SAML IdPs via REST
[ https://issues.apache.org/jira/browse/SYNCOPE-1558?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17091597#comment-17091597 ] Misagh Moayyed commented on SYNCOPE-1558: - Initial pull request to pac4j: [https://github.com/pac4j/pac4j/pull/1577] > Configure WA delegated authn module to SAML IdPs via REST > - > > Key: SYNCOPE-1558 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1558 > Project: Syncope > Issue Type: Sub-task > Components: wa >Affects Versions: 3.0.0 >Reporter: Misagh Moayyed >Assignee: Misagh Moayyed >Priority: Major > Fix For: 3.0.0 > > > When WA is configured to hand off authentication to an external SAML2 > identity provider via pac4j, pac4j expects a java keystore to be > created/present on disk that will be used by WA as a SAML SP to interact with > the IDP and to generate metadata, sign responses, etc. This keystore is > expected to be found on disk, and pac4j does not allow other options for > producing/fetching the keystore via REST. > Also, a number of other artifacts such as generation of SP metadata, etc > should be configurable over rest. > > Task is: > * Allow pac4j to open up its api/configuration to allow for keystore > fetching over rest > * Modify WA to use this configuration and produce keystore data over rest. > > Note that a similar and separate task may be created to handle the same > matter with delegated authn to OIDC OPs. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (SYNCOPE-1558) Configure WA delegated authn module to SAML IdPs via REST
Misagh Moayyed created SYNCOPE-1558: --- Summary: Configure WA delegated authn module to SAML IdPs via REST Key: SYNCOPE-1558 URL: https://issues.apache.org/jira/browse/SYNCOPE-1558 Project: Syncope Issue Type: Sub-task Components: wa Affects Versions: 3.0.0 Reporter: Misagh Moayyed Assignee: Misagh Moayyed Fix For: 3.0.0 When WA is configured to hand off authentication to an external SAML2 identity provider via pac4j, pac4j expects a java keystore to be created/present on disk that will be used by WA as a SAML SP to interact with the IDP and to generate metadata, sign responses, etc. This keystore is expected to be found on disk, and pac4j does not allow other options for producing/fetching the keystore via REST. Also, a number of other artifacts such as generation of SP metadata, etc should be configurable over rest. Task is: * Allow pac4j to open up its api/configuration to allow for keystore fetching over rest * Modify WA to use this configuration and produce keystore data over rest. Note that a similar and separate task may be created to handle the same matter with delegated authn to OIDC OPs. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (SYNCOPE-1553) Fetch WA auth modules & map to properties during bootstrap
[ https://issues.apache.org/jira/browse/SYNCOPE-1553?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Misagh Moayyed resolved SYNCOPE-1553. - Resolution: Fixed > Fetch WA auth modules & map to properties during bootstrap > -- > > Key: SYNCOPE-1553 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1553 > Project: Syncope > Issue Type: Sub-task > Components: wa >Affects Versions: 3.0.0 >Reporter: Misagh Moayyed >Assignee: Misagh Moayyed >Priority: Major > Fix For: 3.0.0 > > > Authentication modules, etc need to be fetched via WA bootstrap using the new > REST APIs and translated into WA configuration properties. This should allow > context-refresh events to successfully activate those authentication modules > for login. > Example use case would be: > * define LDAP authentication module > * fetch module settings in WA on startup/bootstrap > * refresh context > * login using sample LDAP credentials -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (SYNCOPE-1553) Fetch WA auth modules & map to properties during bootstrap
Misagh Moayyed created SYNCOPE-1553: --- Summary: Fetch WA auth modules & map to properties during bootstrap Key: SYNCOPE-1553 URL: https://issues.apache.org/jira/browse/SYNCOPE-1553 Project: Syncope Issue Type: Sub-task Components: wa Affects Versions: 3.0.0 Reporter: Misagh Moayyed Assignee: Misagh Moayyed Fix For: 3.0.0 Authentication modules, etc need to be fetched via WA bootstrap using the new REST APIs and translated into WA configuration properties. This should allow context-refresh events to successfully activate those authentication modules for login. Example use case would be: * define LDAP authentication module * fetch module settings in WA on startup/bootstrap * refresh context * login using sample LDAP credentials -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (SYNCOPE-1552) Allow WA audits to be stored in Syncope
[ https://issues.apache.org/jira/browse/SYNCOPE-1552?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Misagh Moayyed resolved SYNCOPE-1552. - Resolution: Fixed [https://github.com/apache/syncope/pull/174] > Allow WA audits to be stored in Syncope > --- > > Key: SYNCOPE-1552 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1552 > Project: Syncope > Issue Type: Sub-task > Components: wa >Affects Versions: 3.0.0 >Reporter: Misagh Moayyed >Assignee: Misagh Moayyed >Priority: Major > Fix For: 3.0.0 > > Time Spent: 0.5h > Remaining Estimate: 0h > > Web Access Audits are presently handled by default via Sl4fj and written to > log files. Audit events should be handled and managed by Syncope itself. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (SYNCOPE-1552) Allow WA audits to be stored in Syncope
Misagh Moayyed created SYNCOPE-1552: --- Summary: Allow WA audits to be stored in Syncope Key: SYNCOPE-1552 URL: https://issues.apache.org/jira/browse/SYNCOPE-1552 Project: Syncope Issue Type: Sub-task Components: wa Affects Versions: 3.0.0 Reporter: Misagh Moayyed Assignee: Misagh Moayyed Fix For: 3.0.0 Web Access Audits are presently handled by default via Sl4fj and written to log files. Audit events should be handled and managed by Syncope itself. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (SYNCOPE-1497) Upgrade to Wicket 9
[ https://issues.apache.org/jira/browse/SYNCOPE-1497?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Misagh Moayyed reassigned SYNCOPE-1497: --- Assignee: Francesco Chicchiriccò (was: Misagh Moayyed) > Upgrade to Wicket 9 > --- > > Key: SYNCOPE-1497 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1497 > Project: Syncope > Issue Type: Task > Components: console, enduser >Reporter: Francesco Chicchiriccò >Assignee: Francesco Chicchiriccò >Priority: Major > Fix For: 3.0.0 > > Time Spent: 20m > Remaining Estimate: 0h > > See https://cwiki.apache.org/confluence/display/WICKET/Migration+to+Wicket+9.0 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (SYNCOPE-1506) Merge Users
[ https://issues.apache.org/jira/browse/SYNCOPE-1506?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Misagh Moayyed resolved SYNCOPE-1506. - Resolution: Fixed Feature is (and will be) available in 2.1 and the 3.0 release lines. > Merge Users > --- > > Key: SYNCOPE-1506 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1506 > Project: Syncope > Issue Type: New Feature > Components: console, core >Reporter: Francesco Chicchiriccò >Assignee: Misagh Moayyed >Priority: Major > Fix For: 2.1.6, 3.0.0 > > Time Spent: 20m > Remaining Estimate: 0h > > Following SYNCOPE-957, this issue is to provide ability to take two distinct > Users as input and to produce an User with a Linked Account as output. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (SYNCOPE-1511) Configure audit events create/update/etc of users, groups, etc
[ https://issues.apache.org/jira/browse/SYNCOPE-1511?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17026722#comment-17026722 ] Misagh Moayyed commented on SYNCOPE-1511: - new PR to ensure manage history is displayed or hidden in the right panels. > Configure audit events create/update/etc of users, groups, etc > -- > > Key: SYNCOPE-1511 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1511 > Project: Syncope > Issue Type: New Feature > Components: console, core >Affects Versions: 2.1.5 >Reporter: Misagh Moayyed >Assignee: Misagh Moayyed >Priority: Major > Fix For: 2.1.6, 3.0.0 > > Time Spent: 1.5h > Remaining Estimate: 0h > > Extract and export audit events for user create / update / etc (and extend > support to groups and "any object"s), expose them via dedicated REST > interfaces/ops. Also, make sure data can be reviewed in the admin console via > a new history tool. > This feature shall be cherry-picked into master for 3.0, when ready. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (SYNCOPE-1506) Merge Users
[ https://issues.apache.org/jira/browse/SYNCOPE-1506?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Misagh Moayyed reassigned SYNCOPE-1506: --- Assignee: Misagh Moayyed > Merge Users > --- > > Key: SYNCOPE-1506 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1506 > Project: Syncope > Issue Type: New Feature > Components: console, core >Reporter: Francesco Chicchiriccò >Assignee: Misagh Moayyed >Priority: Major > Fix For: 2.1.6, 3.0.0 > > > Following SYNCOPE-957, this issue is to provide ability to take two distinct > Users as input and to produce an User with a Linked Account as output. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (SYNCOPE-1523) JPAConnInstanceDAO should be marked as Transactional
[ https://issues.apache.org/jira/browse/SYNCOPE-1523?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Misagh Moayyed resolved SYNCOPE-1523. - Resolution: Fixed > JPAConnInstanceDAO should be marked as Transactional > > > Key: SYNCOPE-1523 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1523 > Project: Syncope > Issue Type: Improvement > Components: core >Affects Versions: 2.1.5 >Reporter: Misagh Moayyed >Assignee: Misagh Moayyed >Priority: Minor > Fix For: 2.1.6, 3.0.0 > > Time Spent: 40m > Remaining Estimate: 0h > > Allow the JPAConnInstanceDAO to be marked as Transactional, specifically for > find and findAuth methods (readOnly) to allow for persistence operations and > calls from components that already may be marked as such. > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (SYNCOPE-1523) JPAConnInstanceDAO should be marked as Transactional
Misagh Moayyed created SYNCOPE-1523: --- Summary: JPAConnInstanceDAO should be marked as Transactional Key: SYNCOPE-1523 URL: https://issues.apache.org/jira/browse/SYNCOPE-1523 Project: Syncope Issue Type: Improvement Components: core Affects Versions: 2.1.5 Reporter: Misagh Moayyed Assignee: Misagh Moayyed Fix For: 2.1.6, 3.0.0 Allow the JPAConnInstanceDAO to be marked as Transactional, specifically for find and findAuth methods (readOnly) to allow for persistence operations and calls from components that already may be marked as such. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (SYNCOPE-1511) Configure audit events create/update/etc of users, groups, etc
[ https://issues.apache.org/jira/browse/SYNCOPE-1511?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Misagh Moayyed resolved SYNCOPE-1511. - Resolution: Fixed > Configure audit events create/update/etc of users, groups, etc > -- > > Key: SYNCOPE-1511 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1511 > Project: Syncope > Issue Type: New Feature > Components: console, core >Affects Versions: 2.1.5 >Reporter: Misagh Moayyed >Assignee: Misagh Moayyed >Priority: Major > Fix For: 2.1.6, 3.0.0 > > Time Spent: 1h 20m > Remaining Estimate: 0h > > Extract and export audit events for user create / update / etc (and extend > support to groups and "any object"s), expose them via dedicated REST > interfaces/ops. Also, make sure data can be reviewed in the admin console via > a new history tool. > This feature shall be cherry-picked into master for 3.0, when ready. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (SYNCOPE-1511) Configure audit events create/update/etc of users, groups, etc
[ https://issues.apache.org/jira/browse/SYNCOPE-1511?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16988813#comment-16988813 ] Misagh Moayyed commented on SYNCOPE-1511: - Small note FTR that the changes will also be cherry-picked into the 3.0/master branch as well. > Configure audit events create/update/etc of users, groups, etc > -- > > Key: SYNCOPE-1511 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1511 > Project: Syncope > Issue Type: New Feature > Components: console, core >Affects Versions: 2.1.5 >Reporter: Misagh Moayyed >Assignee: Misagh Moayyed >Priority: Major > Fix For: 2.1.6, 3.0.0 > > Time Spent: 1h > Remaining Estimate: 0h > > Extract and export audit events for user create / update / etc (and extend > support to groups and "any object"s), expose them via dedicated REST > interfaces/ops. Also, make sure data can be reviewed in the admin console via > a new history tool. > This feature shall be cherry-picked into master for 3.0, when ready. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (SYNCOPE-1511) Configure audit events create/update/etc of users, groups, etc
[ https://issues.apache.org/jira/browse/SYNCOPE-1511?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Misagh Moayyed resolved SYNCOPE-1511. - Resolution: Fixed > Configure audit events create/update/etc of users, groups, etc > -- > > Key: SYNCOPE-1511 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1511 > Project: Syncope > Issue Type: New Feature > Components: console, core >Affects Versions: 2.1.5 >Reporter: Misagh Moayyed >Assignee: Misagh Moayyed >Priority: Major > Fix For: 2.1.6, 3.0.0 > > Time Spent: 1h > Remaining Estimate: 0h > > Extract and export audit events for user create / update / etc (and extend > support to groups and "any object"s), expose them via dedicated REST > interfaces/ops. Also, make sure data can be reviewed in the admin console via > a new history tool. > This feature shall be cherry-picked into master for 3.0, when ready. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (SYNCOPE-1511) Configure audit events create/update/etc of users, groups, etc
[ https://issues.apache.org/jira/browse/SYNCOPE-1511?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Misagh Moayyed updated SYNCOPE-1511: Description: Extract and export audit events for user create / update / etc (and extend support to groups and "any object"s), expose them via dedicated REST interfaces/ops. Also, make sure data can be reviewed in the admin console via a new history tool. This feature shall be cherry-picked into master for 3.0, when ready. was: Configure audit events for user create / update / etc and extend support to groups and "any object"s. Payloads will be stored in the dedicated audit table. This feature shall be cherry-picked into master for 3.0, when ready. > Configure audit events create/update/etc of users, groups, etc > -- > > Key: SYNCOPE-1511 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1511 > Project: Syncope > Issue Type: New Feature > Components: core >Affects Versions: 2.1.5 >Reporter: Misagh Moayyed >Assignee: Misagh Moayyed >Priority: Major > Fix For: 2.1.6, 3.0.0 > > > Extract and export audit events for user create / update / etc (and extend > support to groups and "any object"s), expose them via dedicated REST > interfaces/ops. Also, make sure data can be reviewed in the admin console via > a new history tool. > This feature shall be cherry-picked into master for 3.0, when ready. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (SYNCOPE-1511) Configure audit events create/update/etc of users, groups, etc
[ https://issues.apache.org/jira/browse/SYNCOPE-1511?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Misagh Moayyed updated SYNCOPE-1511: Component/s: console > Configure audit events create/update/etc of users, groups, etc > -- > > Key: SYNCOPE-1511 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1511 > Project: Syncope > Issue Type: New Feature > Components: console, core >Affects Versions: 2.1.5 >Reporter: Misagh Moayyed >Assignee: Misagh Moayyed >Priority: Major > Fix For: 2.1.6, 3.0.0 > > > Extract and export audit events for user create / update / etc (and extend > support to groups and "any object"s), expose them via dedicated REST > interfaces/ops. Also, make sure data can be reviewed in the admin console via > a new history tool. > This feature shall be cherry-picked into master for 3.0, when ready. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (SYNCOPE-1511) Configure audit events create/update/etc of users, groups, etc
[ https://issues.apache.org/jira/browse/SYNCOPE-1511?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Misagh Moayyed updated SYNCOPE-1511: External issue URL: (was: https://jira.gfs.com/jira/browse/IDAAS-59) > Configure audit events create/update/etc of users, groups, etc > -- > > Key: SYNCOPE-1511 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1511 > Project: Syncope > Issue Type: New Feature > Components: core >Affects Versions: 2.1.5 >Reporter: Misagh Moayyed >Assignee: Misagh Moayyed >Priority: Major > Fix For: 2.1.6, 3.0.0 > > > Configure audit events for user create / update / etc and extend support to > groups and "any object"s. Payloads will be stored in the dedicated audit > table. > > This feature shall be cherry-picked into master for 3.0, when ready. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (SYNCOPE-1511) Configure audit events create/update/etc of users, groups, etc
Misagh Moayyed created SYNCOPE-1511: --- Summary: Configure audit events create/update/etc of users, groups, etc Key: SYNCOPE-1511 URL: https://issues.apache.org/jira/browse/SYNCOPE-1511 Project: Syncope Issue Type: New Feature Components: core Affects Versions: 2.1.5 Reporter: Misagh Moayyed Assignee: Misagh Moayyed Fix For: 2.1.6, 3.0.0 Configure audit events for user create / update / etc and extend support to groups and "any object"s. Payloads will be stored in the dedicated audit table. This feature shall be cherry-picked into master for 3.0, when ready. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Reopened] (SYNCOPE-1465) Add executor information to Task and Report executions
[
https://issues.apache.org/jira/browse/SYNCOPE-1465?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Misagh Moayyed reopened SYNCOPE-1465:
-
Following up with a separate PR to complete work on TaskTO objects and family.
> Add executor information to Task and Report executions
> --
>
> Key: SYNCOPE-1465
> URL: https://issues.apache.org/jira/browse/SYNCOPE-1465
> Project: Syncope
> Issue Type: Improvement
> Components: core
>Reporter: Francesco Chicchiriccò
>Assignee: Misagh Moayyed
>Priority: Major
> Fix For: 3.0.0
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> It is currently not possible to know which user started a given Task or
> Report.
> This cannot apply to scheduled executions, naturally, as they will be always
> run by {{admin}}.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Resolved] (SYNCOPE-1465) Add executor information to Task and Report executions
[
https://issues.apache.org/jira/browse/SYNCOPE-1465?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Misagh Moayyed resolved SYNCOPE-1465.
-
Resolution: Fixed
> Add executor information to Task and Report executions
> --
>
> Key: SYNCOPE-1465
> URL: https://issues.apache.org/jira/browse/SYNCOPE-1465
> Project: Syncope
> Issue Type: Improvement
> Components: core
>Reporter: Francesco Chicchiriccò
>Assignee: Misagh Moayyed
>Priority: Major
> Fix For: 3.0.0
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> It is currently not possible to know which user started a given Task or
> Report.
> This cannot apply to scheduled executions, naturally, as they will be always
> run by {{admin}}.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (SYNCOPE-1218) Store layout Topology
[ https://issues.apache.org/jira/browse/SYNCOPE-1218?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16947162#comment-16947162 ] Misagh Moayyed commented on SYNCOPE-1218: - The import/export functionality for Topology seems like a good idea to me. I imagine folks tend to organize the screen in any number of ways to make sense of the relationships and so allowing folks to import a pre-defined layout and save it or export it out would be valuable. > Store layout Topology > - > > Key: SYNCOPE-1218 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1218 > Project: Syncope > Issue Type: Improvement > Components: console >Reporter: Filipe Silva >Priority: Minor > > At this point the topology layout is stored in browser cookies. > I would like to suggest as future features: > - the store of the layout topology to be done to the database (user based). > Automatically or as an option. > - a way to store/share a default layout to be used on the first interaction > with topology or when using an option to reset the layout. > In some complex topology (maybe even some simple ones) I think that would be > very useful, specially when using distinct browsers/computers (and at least > to improve a first impression of the tool for the users that have access to > the topology section ;-)). -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (SYNCOPE-1496) Add integration tests for DBMSes via Docker
[ https://issues.apache.org/jira/browse/SYNCOPE-1496?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Misagh Moayyed reassigned SYNCOPE-1496: --- Assignee: Misagh Moayyed (was: Francesco Chicchiriccò) > Add integration tests for DBMSes via Docker > --- > > Key: SYNCOPE-1496 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1496 > Project: Syncope > Issue Type: Sub-task > Components: build-tools >Affects Versions: 3.0.0 >Reporter: Misagh Moayyed >Assignee: Misagh Moayyed >Priority: Minor > Fix For: 3.0.0 > > > Integration tests for DBMSes should be turned on and added to Travis CI as an > independant job: > [https://syncope.apache.org/building#DBMSes] > This will of course require pulling down relevant docker images for each > build, and each DBMS may require to be its own job to avoid timeouts. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (SYNCOPE-1497) Upgrade to Wicket 9
[ https://issues.apache.org/jira/browse/SYNCOPE-1497?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Misagh Moayyed reassigned SYNCOPE-1497: --- Assignee: Misagh Moayyed > Upgrade to Wicket 9 > --- > > Key: SYNCOPE-1497 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1497 > Project: Syncope > Issue Type: Task > Components: console, enduser >Reporter: Francesco Chicchiriccò >Assignee: Misagh Moayyed >Priority: Major > Fix For: 3.0.0 > > Time Spent: 10m > Remaining Estimate: 0h > > See https://cwiki.apache.org/confluence/display/WICKET/Migration+to+Wicket+9.0 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (SYNCOPE-1465) Add executor information to Task and Report executions
[
https://issues.apache.org/jira/browse/SYNCOPE-1465?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Misagh Moayyed reassigned SYNCOPE-1465:
---
Assignee: Misagh Moayyed (was: Francesco Chicchiriccò)
> Add executor information to Task and Report executions
> --
>
> Key: SYNCOPE-1465
> URL: https://issues.apache.org/jira/browse/SYNCOPE-1465
> Project: Syncope
> Issue Type: Improvement
> Components: core
>Reporter: Francesco Chicchiriccò
>Assignee: Misagh Moayyed
>Priority: Major
> Fix For: 3.0.0
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> It is currently not possible to know which user started a given Task or
> Report.
> This cannot apply to scheduled executions, naturally, as they will be always
> run by {{admin}}.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Comment Edited] (SYNCOPE-1497) Upgrade to Wicket 9
[ https://issues.apache.org/jira/browse/SYNCOPE-1497?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16941539#comment-16941539 ] Misagh Moayyed edited comment on SYNCOPE-1497 at 10/1/19 5:36 AM: -- Related: [https://github.com/MarcGiffing/wicket-spring-boot/pull/160] I have tested the master branch with the above pull request and everything so far looks good. There are a few minor issues with webjars that I will sort out later, and at this point need to wait until the above PR is reviewed and merged and released before Syncope can pick up the change with other required changes. was (Author: mmoayyed): Related: [https://github.com/MarcGiffing/wicket-spring-boot/pull/160] > Upgrade to Wicket 9 > --- > > Key: SYNCOPE-1497 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1497 > Project: Syncope > Issue Type: Task > Components: console, enduser >Reporter: Francesco Chicchiriccò >Priority: Major > Fix For: 3.0.0 > > > See https://cwiki.apache.org/confluence/display/WICKET/Migration+to+Wicket+9.0 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (SYNCOPE-1497) Upgrade to Wicket 9
[ https://issues.apache.org/jira/browse/SYNCOPE-1497?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16941539#comment-16941539 ] Misagh Moayyed commented on SYNCOPE-1497: - Related: [https://github.com/MarcGiffing/wicket-spring-boot/pull/160] > Upgrade to Wicket 9 > --- > > Key: SYNCOPE-1497 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1497 > Project: Syncope > Issue Type: Task > Components: console, enduser >Reporter: Francesco Chicchiriccò >Priority: Major > Fix For: 3.0.0 > > > See https://cwiki.apache.org/confluence/display/WICKET/Migration+to+Wicket+9.0 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (SYNCOPE-1497) Upgrade to Wicket 9
[ https://issues.apache.org/jira/browse/SYNCOPE-1497?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16938359#comment-16938359 ] Misagh Moayyed commented on SYNCOPE-1497: - Related: [https://github.com/MarcGiffing/wicket-spring-boot/issues/159] > Upgrade to Wicket 9 > --- > > Key: SYNCOPE-1497 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1497 > Project: Syncope > Issue Type: Task > Components: console, enduser >Reporter: Francesco Chicchiriccò >Priority: Major > Fix For: 3.0.0 > > > See https://cwiki.apache.org/confluence/display/WICKET/Migration+to+Wicket+9.0 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (SYNCOPE-1332) Java 11 language features
[ https://issues.apache.org/jira/browse/SYNCOPE-1332?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16933280#comment-16933280 ] Misagh Moayyed commented on SYNCOPE-1332: - I think this can now be closed. We are at a good-enough state where all other clean-up etc would have to be ad-hoc and sort of ongoing. > Java 11 language features > - > > Key: SYNCOPE-1332 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1332 > Project: Syncope > Issue Type: Task >Reporter: Francesco Chicchiriccò >Assignee: Francesco Chicchiriccò >Priority: Major > Fix For: 3.0.0 > > Time Spent: 1h 40m > Remaining Estimate: 0h > > SYNCOPE-1327 allowed the code to be built with JDK 9/10. > As agreed in [mailing > list|https://lists.apache.org/thread.html/8c5f03cb5f0304c215bc05fa6e61da808433e09359d749cdf2dec9b2@%3Cdev.syncope.apache.org%3E], > 3.0.0 will require JDK 11, and should also use the new language features as > much as possible. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (SYNCOPE-1496) Add integration tests for DBMSes via Docker
[ https://issues.apache.org/jira/browse/SYNCOPE-1496?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16933276#comment-16933276 ] Misagh Moayyed commented on SYNCOPE-1496: - This continues to be ongoing. Unfortunately, tests seem very very brittle and break at random for a variety of reasons; some in fact take quite a long time to run, longer than 50 minutes. Initial stab at this is at https://travis-ci.org/mmoayyed/syncope > Add integration tests for DBMSes via Docker > --- > > Key: SYNCOPE-1496 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1496 > Project: Syncope > Issue Type: Sub-task > Components: build-tools >Affects Versions: 3.0.0 >Reporter: Misagh Moayyed >Priority: Minor > Fix For: 3.0.0 > > > Integration tests for DBMSes should be turned on and added to Travis CI as an > independant job: > [https://syncope.apache.org/building#DBMSes] > This will of course require pulling down relevant docker images for each > build, and each DBMS may require to be its own job to avoid timeouts. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (SYNCOPE-1494) Basic maven build to verify compilation correctness
[ https://issues.apache.org/jira/browse/SYNCOPE-1494?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Misagh Moayyed resolved SYNCOPE-1494. - Resolution: Fixed > Basic maven build to verify compilation correctness > --- > > Key: SYNCOPE-1494 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1494 > Project: Syncope > Issue Type: Sub-task > Components: build-tools >Affects Versions: 3.0.0 >Reporter: Misagh Moayyed >Priority: Minor > Fix For: 3.0.0 > > -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Commented] (SYNCOPE-1494) Basic maven build to verify compilation correctness
[ https://issues.apache.org/jira/browse/SYNCOPE-1494?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16931161#comment-16931161 ] Misagh Moayyed commented on SYNCOPE-1494: - This should be resolved/closed. Additional sub-tasks for the parent Jira will carry on the work. > Basic maven build to verify compilation correctness > --- > > Key: SYNCOPE-1494 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1494 > Project: Syncope > Issue Type: Sub-task > Components: build-tools >Affects Versions: 3.0.0 >Reporter: Misagh Moayyed >Priority: Minor > Fix For: 3.0.0 > > -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Created] (SYNCOPE-1496) Add integration tests for DBMSes via Docker
Misagh Moayyed created SYNCOPE-1496: --- Summary: Add integration tests for DBMSes via Docker Key: SYNCOPE-1496 URL: https://issues.apache.org/jira/browse/SYNCOPE-1496 Project: Syncope Issue Type: Sub-task Components: build-tools Affects Versions: 3.0.0 Reporter: Misagh Moayyed Fix For: 3.0.0 Integration tests for DBMSes should be turned on and added to Travis CI as an independant job: [https://syncope.apache.org/building#DBMSes] This will of course require pulling down relevant docker images for each build, and each DBMS may require to be its own job to avoid timeouts. -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Commented] (SYNCOPE-1332) Java 11 language features
[ https://issues.apache.org/jira/browse/SYNCOPE-1332?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16927306#comment-16927306 ] Misagh Moayyed commented on SYNCOPE-1332: - There is some minor cleanup left and a few more rounds of fixes for stuff reported by static analysis tools. I think we should be able to finalize and close this out by next Monday. Probably 1-2 more PRs should do it. How about var support? Are we sure tp skip adopting? (Nothing to do with type safety per se; just makes it simpler to read and write less code) Don't plan to do modules; I see no benefit in complicating the codebase with the use of modules and we get nothing out of it. Seems way more useful for library authors; not folks who work on platforms/products. > Java 11 language features > - > > Key: SYNCOPE-1332 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1332 > Project: Syncope > Issue Type: Task >Reporter: Francesco Chicchiriccò >Assignee: Francesco Chicchiriccò >Priority: Major > Fix For: 3.0.0 > > Time Spent: 1h 40m > Remaining Estimate: 0h > > SYNCOPE-1327 allowed the code to be built with JDK 9/10. > As agreed in [mailing > list|https://lists.apache.org/thread.html/8c5f03cb5f0304c215bc05fa6e61da808433e09359d749cdf2dec9b2@%3Cdev.syncope.apache.org%3E], > 3.0.0 will require JDK 11, and should also use the new language features as > much as possible. -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Created] (SYNCOPE-1494) Basic maven build to verify compilation correctness
Misagh Moayyed created SYNCOPE-1494: --- Summary: Basic maven build to verify compilation correctness Key: SYNCOPE-1494 URL: https://issues.apache.org/jira/browse/SYNCOPE-1494 Project: Syncope Issue Type: Sub-task Components: build-tools Affects Versions: 3.0.0 Reporter: Misagh Moayyed Fix For: 3.0.0 -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Created] (SYNCOPE-1489) Reorganize Travis CI to run the build suite in stages
Misagh Moayyed created SYNCOPE-1489: --- Summary: Reorganize Travis CI to run the build suite in stages Key: SYNCOPE-1489 URL: https://issues.apache.org/jira/browse/SYNCOPE-1489 Project: Syncope Issue Type: Task Components: build-tools Affects Versions: 3.0.0 Reporter: Misagh Moayyed Fix For: 3.0.0 Per discussions on the dev mailing list, this Jira tracks improvements to the Travis CI process to split the build into multiple stages and jobs. The overall task list would include: # run the straight "mvn clean install" one normally performs on his / her laptop, which involves RAT checks, Checkstyle, modernizer, etc, all unit and integration tests # run integration tests with different content types [5] # run the Admin UI tests [4], currently not run by default under fit/core-reference # run the Enduser UI tests ([4] for master), currently not run by default under fit/core-reference # run integration tests under the other supported Java EE containers (besides Tomcat) [6] # run integration tests with the other supported DBMSes (besides H2) # run integration tests with Elasticsearch - not documented but available # run SAML 2.0 / OpenID Connect 1.0 login tests - not documented but available (only master) Individual sub-tasks will be created to track the progress for the above list. > [4] [http://syncope.apache.org/building#All_integration_tests] > [5] [http://syncope.apache.org/building#Other_Content-Type_values] > [6] [http://syncope.apache.org/building#Java_EE_containers] > [7] [http://syncope.apache.org/building#DBMSes] -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Commented] (SYNCOPE-175) End-user JSR-286 portlet
[ https://issues.apache.org/jira/browse/SYNCOPE-175?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16925512#comment-16925512 ] Misagh Moayyed commented on SYNCOPE-175: I'd suggest that we close out this one as WONT-FIX. Portlets are quite largely deprecated and disputed as viable options in today's portals. Portals seem to prefer web content that is not shackled by the boundaries of the JSR-186/286 specifications. The uPortal project, [https://github.com/Jasig/uPortal], while itself does support portlets, has opted into using alternative strategies that are more REST friendly than portlets, and I suspect others such as Liferay have begun to take on similar approach. A full page refresh, as I think is required by the portlet spec is generally not something a portal adopter might want to deploy. I admit that I have not reviewed the 3rd version of the spec quite thoroughly, but it might be a case of too little/too late at the moment. > End-user JSR-286 portlet > > > Key: SYNCOPE-175 > URL: https://issues.apache.org/jira/browse/SYNCOPE-175 > Project: Syncope > Issue Type: Wish >Reporter: Francesco Chicchiriccò >Priority: Minor > Fix For: 4.0.0 > > > Provide a portlet for end-user interface in portal environments. -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Commented] (SYNCOPE-168) Allow more notification mechanisms besides e-mail
[ https://issues.apache.org/jira/browse/SYNCOPE-168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16925507#comment-16925507 ] Misagh Moayyed commented on SYNCOPE-168: This might be something I can take on. What other mechanisms are being considered here? Shall we opt for SMS messages, based on providers with available Java APIs? I have done some work in the past based on Twilio, Amazon SNS, Clickatell and Nexmo. Of course, all require paid subscriptions. Shall we choose one, or are there better alternatives? > Allow more notification mechanisms besides e-mail > - > > Key: SYNCOPE-168 > URL: https://issues.apache.org/jira/browse/SYNCOPE-168 > Project: Syncope > Issue Type: Sub-task >Reporter: Francesco Chicchiriccò >Priority: Major > Fix For: 4.0.0 > > -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Updated] (SYNCOPE-1486) Upgrade maven-checkstyle-plugin to checkstyle 8.24
[ https://issues.apache.org/jira/browse/SYNCOPE-1486?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Misagh Moayyed updated SYNCOPE-1486: Description: At the moment, the maven-checkstyle-plugin is at version 3.1.0, which ships with checkstyle version 8.19. Checkstyle 8.24 is out and due to changes in configuration syntax, one cannot easily switch to the more recent checkstyle version. Specifically, the "TreeWalker" module contains a few breaking changes and moved/removed elements such as LineLength that need to be reorganized slightly before checkstyle can be used with more recent versions. This task proposes to upgrade the checkstyle version to 8.24 (or whatever might most recent at the time work begins) and then fix all configuration issues related to syntax of the new version: [https://maven.apache.org/plugins/maven-checkstyle-plugin/examples/upgrading-checkstyle.html] was: At the moment, the maven-checkstyle-plugin is at version 3.1.0, which ships with checkstyle version 8.19. Checkstyle 8.24 is out and due to changes in configuration syntax, one cannot easily switch to the more recent checkstyle version. Specifically, the "TreeWalker" module contains a few breaking changes and moved/removed elements such as LineLength that need to be reorganized slightly before checkstyle can be used with more recent versions. This task proposes to upgrade the checkstyle version to 8.24 (or whatever might most recent at the time work begins) and then fix all configuration issues related to syntax of the new version. > Upgrade maven-checkstyle-plugin to checkstyle 8.24 > -- > > Key: SYNCOPE-1486 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1486 > Project: Syncope > Issue Type: Task > Components: build-tools >Affects Versions: 3.0.0 >Reporter: Misagh Moayyed >Priority: Trivial > Fix For: 3.0.0 > > > At the moment, the maven-checkstyle-plugin is at version 3.1.0, which ships > with checkstyle version 8.19. > Checkstyle 8.24 is out and due to changes in configuration syntax, one cannot > easily switch to the more recent checkstyle version. Specifically, the > "TreeWalker" module contains a few breaking changes and moved/removed > elements such as LineLength that need to be reorganized slightly before > checkstyle can be used with more recent versions. > > This task proposes to upgrade the checkstyle version to 8.24 (or whatever > might most recent at the time work begins) and then fix all configuration > issues related to syntax of the new version: > [https://maven.apache.org/plugins/maven-checkstyle-plugin/examples/upgrading-checkstyle.html] -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Created] (SYNCOPE-1486) Upgrade maven-checkstyle-plugin to checkstyle 8.24
Misagh Moayyed created SYNCOPE-1486: --- Summary: Upgrade maven-checkstyle-plugin to checkstyle 8.24 Key: SYNCOPE-1486 URL: https://issues.apache.org/jira/browse/SYNCOPE-1486 Project: Syncope Issue Type: Task Components: build-tools Affects Versions: 3.0.0 Reporter: Misagh Moayyed Fix For: 3.0.0 At the moment, the maven-checkstyle-plugin is at version 3.1.0, which ships with checkstyle version 8.19. Checkstyle 8.24 is out and due to changes in configuration syntax, one cannot easily switch to the more recent checkstyle version. Specifically, the "TreeWalker" module contains a few breaking changes and moved/removed elements such as LineLength that need to be reorganized slightly before checkstyle can be used with more recent versions. This task proposes to upgrade the checkstyle version to 8.24 (or whatever might most recent at the time work begins) and then fix all configuration issues related to syntax of the new version. -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Commented] (SYNCOPE-1484) syncope-ide-netbeans submodule fails to find netbeans dependency
[
https://issues.apache.org/jira/browse/SYNCOPE-1484?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16921246#comment-16921246
]
Misagh Moayyed commented on SYNCOPE-1484:
-
Pull request [https://github.com/apache/syncope/pull/106]
> syncope-ide-netbeans submodule fails to find netbeans dependency
>
>
> Key: SYNCOPE-1484
> URL: https://issues.apache.org/jira/browse/SYNCOPE-1484
> Project: Syncope
> Issue Type: Bug
> Components: build-tools
>Affects Versions: 3.0.0
>Reporter: Misagh Moayyed
>Priority: Minor
> Fix For: 2.0.14, 2.1.5, 3.0.0
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> - Fresh clone of the master branch
> - Switch to JDK 11
>
> {code:java}
> java version "11" 2018-09-25
> Java(TM) SE Runtime Environment 18.9 (build 11+28)
> Java HotSpot(TM) 64-Bit Server VM 18.9 (build 11+28, mixed mode){code}
>
> Use Apache Maven 3.6.1
> {code:java}
> Apache Maven 3.6.1 (d66c9c0b3152b2e69ee9bac180bb8fcc8e6af555;
> 2019-04-04T23:30:29+04:30){code}
> Run:
> {code:java}
> mvn clean install{code}
> See below:
> {code:java}
> [ERROR] Failed to execute goal on project syncope-ide-netbeans: Could not
> resolve dependencies for project
> org.apache.syncope.ide:syncope-ide-netbeans:nbm:3.0.0-SNAPSHOT: Failed to
> collect dependencies at
> org.netbeans.api:org-netbeans-api-annotations-common:jar:RELEASE82: Failed to
> read artifact descriptor for
> org.netbeans.api:org-netbeans-api-annotations-common:jar:RELEASE82: Could not
> transfer artifact
> org.netbeans.api:org-netbeans-api-annotations-common:pom:RELEASE82 from/to
> netbeans (http://bits.netbeans.org/maven2/): Failed to transfer file
> http://bits.netbeans.org/maven2/org/netbeans/api/org-netbeans-api-annotations-common/RELEASE82/org-netbeans-api-annotations-common-RELEASE82.pom
> with status code 502
> {code}
> Maven Central has no dependency for version RELEASE82; possibility outdated
> or removed.
> Coordinates here show that the current available release version is
> RELEASE111, which does allow for a full and successful build:
> [https://search.maven.org/search?q=g:org.netbeans.api%20AND%20a:org-netbeans-api-annotations-common=gav]
>
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
