[jira] [Resolved] (SYNCOPE-1249) Support for mustChangePassword mapping
[
https://issues.apache.org/jira/browse/SYNCOPE-1249?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Francesco Chicchiriccò resolved SYNCOPE-1249.
-
Resolution: Fixed
> Support for mustChangePassword mapping
> --
>
> Key: SYNCOPE-1249
> URL: https://issues.apache.org/jira/browse/SYNCOPE-1249
> Project: Syncope
> Issue Type: New Feature
> Components: core
>Affects Versions: 2.0.5, 2.0.7
> Environment: Ubuntu LINUX
>Reporter: Philip Lloyd Feliprada
>Assignee: Francesco Chicchiriccò
>Priority: Minor
> Labels: features
> Fix For: 2.0.7, 2.1.0
>
>
> Here is my concern:
> I've been trying to map mustChangePassword with a created
> attribute(mustChangePass) from my LDAP.
> I tried to set the created attribute to ("true") but the value does not
> reflect with mustChangePassword after I pulled the user.
> Expected result must be a check under must change password column.
> Hoping you'll accept this request(support for mustChangePassword mapping) for
> your release on Apache Syncope 2.0.7 Thank you!
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (SYNCOPE-1249) Support for mustChangePassword mapping
[
https://issues.apache.org/jira/browse/SYNCOPE-1249?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16292151#comment-16292151
]
ASF subversion and git services commented on SYNCOPE-1249:
--
Commit 4193ab370b05d266d36ea37656d923cd7b040951 in syncope's branch
refs/heads/2_0_X from [~ilgrosso]
[ https://git-wip-us.apache.org/repos/asf?p=syncope.git;h=4193ab3 ]
[SYNCOPE-1249] Better management of User, Group and AnyObject field mapping -
including mustChangePassword
> Support for mustChangePassword mapping
> --
>
> Key: SYNCOPE-1249
> URL: https://issues.apache.org/jira/browse/SYNCOPE-1249
> Project: Syncope
> Issue Type: New Feature
> Components: core
>Affects Versions: 2.0.5, 2.0.7
> Environment: Ubuntu LINUX
>Reporter: Philip Lloyd Feliprada
>Assignee: Francesco Chicchiriccò
>Priority: Minor
> Labels: features
> Fix For: 2.0.7, 2.1.0
>
>
> Here is my concern:
> I've been trying to map mustChangePassword with a created
> attribute(mustChangePass) from my LDAP.
> I tried to set the created attribute to ("true") but the value does not
> reflect with mustChangePassword after I pulled the user.
> Expected result must be a check under must change password column.
> Hoping you'll accept this request(support for mustChangePassword mapping) for
> your release on Apache Syncope 2.0.7 Thank you!
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (SYNCOPE-1249) Support for mustChangePassword mapping
[
https://issues.apache.org/jira/browse/SYNCOPE-1249?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16292152#comment-16292152
]
ASF subversion and git services commented on SYNCOPE-1249:
--
Commit 471c0fa67b68c37e8fe974b408079bc4e3c7c250 in syncope's branch
refs/heads/master from [~ilgrosso]
[ https://git-wip-us.apache.org/repos/asf?p=syncope.git;h=471c0fa ]
[SYNCOPE-1249] Better management of User, Group and AnyObject field mapping -
including mustChangePassword
> Support for mustChangePassword mapping
> --
>
> Key: SYNCOPE-1249
> URL: https://issues.apache.org/jira/browse/SYNCOPE-1249
> Project: Syncope
> Issue Type: New Feature
> Components: core
>Affects Versions: 2.0.5, 2.0.7
> Environment: Ubuntu LINUX
>Reporter: Philip Lloyd Feliprada
>Assignee: Francesco Chicchiriccò
>Priority: Minor
> Labels: features
> Fix For: 2.0.7, 2.1.0
>
>
> Here is my concern:
> I've been trying to map mustChangePassword with a created
> attribute(mustChangePass) from my LDAP.
> I tried to set the created attribute to ("true") but the value does not
> reflect with mustChangePassword after I pulled the user.
> Expected result must be a check under must change password column.
> Hoping you'll accept this request(support for mustChangePassword mapping) for
> your release on Apache Syncope 2.0.7 Thank you!
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Assigned] (SYNCOPE-1249) Support for mustChangePassword mapping
[
https://issues.apache.org/jira/browse/SYNCOPE-1249?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Francesco Chicchiriccò reassigned SYNCOPE-1249:
---
Assignee: Francesco Chicchiriccò
> Support for mustChangePassword mapping
> --
>
> Key: SYNCOPE-1249
> URL: https://issues.apache.org/jira/browse/SYNCOPE-1249
> Project: Syncope
> Issue Type: New Feature
> Components: core
>Affects Versions: 2.0.5, 2.0.7
> Environment: Ubuntu LINUX
>Reporter: Philip Lloyd Feliprada
>Assignee: Francesco Chicchiriccò
>Priority: Minor
> Labels: features
> Fix For: 2.0.7, 2.1.0
>
>
> Here is my concern:
> I've been trying to map mustChangePassword with a created
> attribute(mustChangePass) from my LDAP.
> I tried to set the created attribute to ("true") but the value does not
> reflect with mustChangePassword after I pulled the user.
> Expected result must be a check under must change password column.
> Hoping you'll accept this request(support for mustChangePassword mapping) for
> your release on Apache Syncope 2.0.7 Thank you!
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Closed] (SYNCOPE-1245) Timeout when retrieving members of a group
[ https://issues.apache.org/jira/browse/SYNCOPE-1245?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matteo Alessandroni closed SYNCOPE-1245. > Timeout when retrieving members of a group > --- > > Key: SYNCOPE-1245 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1245 > Project: Syncope > Issue Type: Bug > Components: console >Affects Versions: 2.0.6 > Environment: Syncope installation with several thousdands of groups. > Real test case counts ~15k groups and 160k users >Reporter: Andrea Patricelli > > Pre--requisite: on Syncope there are several thousands of groups and users > assigned to them. > 1. Login on Syncope admin console > 2. Go to GROUP page and select a group with assigned several thousands of > users, then click on members -> USER. > You'll see, with a certain level of probability, a stacktrace by wicket > showing timeout exception. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (SYNCOPE-1245) Timeout when retrieving members of a group
[ https://issues.apache.org/jira/browse/SYNCOPE-1245?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matteo Alessandroni resolved SYNCOPE-1245. -- Resolution: Cannot Reproduce > Timeout when retrieving members of a group > --- > > Key: SYNCOPE-1245 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1245 > Project: Syncope > Issue Type: Bug > Components: console >Affects Versions: 2.0.6 > Environment: Syncope installation with several thousdands of groups. > Real test case counts ~15k groups and 160k users >Reporter: Andrea Patricelli > > Pre--requisite: on Syncope there are several thousands of groups and users > assigned to them. > 1. Login on Syncope admin console > 2. Go to GROUP page and select a group with assigned several thousands of > users, then click on members -> USER. > You'll see, with a certain level of probability, a stacktrace by wicket > showing timeout exception. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Reopened] (SYNCOPE-1245) Timeout when retrieving members of a group
[ https://issues.apache.org/jira/browse/SYNCOPE-1245?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matteo Alessandroni reopened SYNCOPE-1245: -- > Timeout when retrieving members of a group > --- > > Key: SYNCOPE-1245 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1245 > Project: Syncope > Issue Type: Bug > Components: console >Affects Versions: 2.0.6 > Environment: Syncope installation with several thousdands of groups. > Real test case counts ~15k groups and 160k users >Reporter: Andrea Patricelli > > Pre--requisite: on Syncope there are several thousands of groups and users > assigned to them. > 1. Login on Syncope admin console > 2. Go to GROUP page and select a group with assigned several thousands of > users, then click on members -> USER. > You'll see, with a certain level of probability, a stacktrace by wicket > showing timeout exception. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Closed] (SYNCOPE-1245) Timeout when retrieving members of a group
[ https://issues.apache.org/jira/browse/SYNCOPE-1245?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Francesco Chicchiriccò closed SYNCOPE-1245. --- > Timeout when retrieving members of a group > --- > > Key: SYNCOPE-1245 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1245 > Project: Syncope > Issue Type: Bug > Components: console >Affects Versions: 2.0.6 > Environment: Syncope installation with several thousdands of groups. > Real test case counts ~15k groups and 160k users >Reporter: Andrea Patricelli > > Pre--requisite: on Syncope there are several thousands of groups and users > assigned to them. > 1. Login on Syncope admin console > 2. Go to GROUP page and select a group with assigned several thousands of > users, then click on members -> USER. > You'll see, with a certain level of probability, a stacktrace by wicket > showing timeout exception. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (SYNCOPE-1245) Timeout when retrieving members of a group
[ https://issues.apache.org/jira/browse/SYNCOPE-1245?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matteo Alessandroni resolved SYNCOPE-1245. -- Resolution: Won't Fix Fix Version/s: (was: 2.0.7) (was: 2.1.0) > Timeout when retrieving members of a group > --- > > Key: SYNCOPE-1245 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1245 > Project: Syncope > Issue Type: Bug > Components: console >Affects Versions: 2.0.6 > Environment: Syncope installation with several thousdands of groups. > Real test case counts ~15k groups and 160k users >Reporter: Andrea Patricelli > > Pre--requisite: on Syncope there are several thousands of groups and users > assigned to them. > 1. Login on Syncope admin console > 2. Go to GROUP page and select a group with assigned several thousands of > users, then click on members -> USER. > You'll see, with a certain level of probability, a stacktrace by wicket > showing timeout exception. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (SYNCOPE-1246) Group membership search stucks with several thousands of groups
[ https://issues.apache.org/jira/browse/SYNCOPE-1246?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matteo Alessandroni resolved SYNCOPE-1246. -- Resolution: Fixed > Group membership search stucks with several thousands of groups > --- > > Key: SYNCOPE-1246 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1246 > Project: Syncope > Issue Type: Bug > Components: console >Affects Versions: 2.0.6 > Environment: Syncope installation with several thousdands of groups. > Real test case counts ~15k groups and 160k users >Reporter: Andrea Patricelli >Assignee: Matteo Alessandroni > Fix For: 2.0.7, 2.1.0 > > > Pre-requisite: on Syncope there are several thousands of groups and users > assigned to them. > 1. Login on Syncope admin console > 2. Go to USER tab and click on User Search > 3. from the leftmost select choose GROUP_MEMBERSHIP > You'll notice that console stucks and no other links work, due to some > internal timeout or long process that retrieves all group names to fill the > right field of the search. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (SYNCOPE-1246) Group membership search stucks with several thousands of groups
[ https://issues.apache.org/jira/browse/SYNCOPE-1246?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16291043#comment-16291043 ] ASF subversion and git services commented on SYNCOPE-1246: -- Commit 76c1140167e59386ad2854ffc7f5ba00fc21e503 in syncope's branch refs/heads/master from [~skylark17] [ https://git-wip-us.apache.org/repos/asf?p=syncope.git;h=76c1140 ] [SYNCOPE-1246] Replaced 'property' dropdown field with an autocomplete textfield in search components > Group membership search stucks with several thousands of groups > --- > > Key: SYNCOPE-1246 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1246 > Project: Syncope > Issue Type: Bug > Components: console >Affects Versions: 2.0.6 > Environment: Syncope installation with several thousdands of groups. > Real test case counts ~15k groups and 160k users >Reporter: Andrea Patricelli >Assignee: Matteo Alessandroni > Fix For: 2.0.7, 2.1.0 > > > Pre-requisite: on Syncope there are several thousands of groups and users > assigned to them. > 1. Login on Syncope admin console > 2. Go to USER tab and click on User Search > 3. from the leftmost select choose GROUP_MEMBERSHIP > You'll notice that console stucks and no other links work, due to some > internal timeout or long process that retrieves all group names to fill the > right field of the search. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (SYNCOPE-1246) Group membership search stucks with several thousands of groups
[ https://issues.apache.org/jira/browse/SYNCOPE-1246?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16291021#comment-16291021 ] ASF subversion and git services commented on SYNCOPE-1246: -- Commit 96a7848485c6f7c685266a301cc479ca2fb3a9d4 in syncope's branch refs/heads/2_0_X from [~skylark17] [ https://git-wip-us.apache.org/repos/asf?p=syncope.git;h=96a7848 ] [SYNCOPE-1246] Replaced 'property' dropdown field with an autocomplete textfield in search components > Group membership search stucks with several thousands of groups > --- > > Key: SYNCOPE-1246 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1246 > Project: Syncope > Issue Type: Bug > Components: console >Affects Versions: 2.0.6 > Environment: Syncope installation with several thousdands of groups. > Real test case counts ~15k groups and 160k users >Reporter: Andrea Patricelli >Assignee: Matteo Alessandroni > Fix For: 2.0.7, 2.1.0 > > > Pre-requisite: on Syncope there are several thousands of groups and users > assigned to them. > 1. Login on Syncope admin console > 2. Go to USER tab and click on User Search > 3. from the leftmost select choose GROUP_MEMBERSHIP > You'll notice that console stucks and no other links work, due to some > internal timeout or long process that retrieves all group names to fill the > right field of the search. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (SYNCOPE-1251) UserTO variable is not updated during Update Activiti Task
[ https://issues.apache.org/jira/browse/SYNCOPE-1251?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marco Di Sabatino Di Diodoro reassigned SYNCOPE-1251: - Assignee: Marco Di Sabatino Di Diodoro > UserTO variable is not updated during Update Activiti Task > -- > > Key: SYNCOPE-1251 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1251 > Project: Syncope > Issue Type: Bug > Components: core >Affects Versions: 2.0.6 >Reporter: Marco Di Sabatino Di Diodoro >Assignee: Marco Di Sabatino Di Diodoro > Fix For: 2.0.7, 2.1.0 > > > During the update process, the variable userTO is not updated in the > workflow. > In the approval phase, if you make a change to the user, the userTO doesn't > match the current one. This causes a wrong user patch. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (SYNCOPE-1251) UserTO variable is not updated during Update Activiti Task
[ https://issues.apache.org/jira/browse/SYNCOPE-1251?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marco Di Sabatino Di Diodoro resolved SYNCOPE-1251. --- Resolution: Fixed > UserTO variable is not updated during Update Activiti Task > -- > > Key: SYNCOPE-1251 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1251 > Project: Syncope > Issue Type: Bug > Components: core >Affects Versions: 2.0.6 >Reporter: Marco Di Sabatino Di Diodoro >Assignee: Marco Di Sabatino Di Diodoro > Fix For: 2.0.7, 2.1.0 > > > During the update process, the variable userTO is not updated in the > workflow. > In the approval phase, if you make a change to the user, the userTO doesn't > match the current one. This causes a wrong user patch. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (SYNCOPE-1251) UserTO variable is not updated during Update Activiti Task
[ https://issues.apache.org/jira/browse/SYNCOPE-1251?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16290817#comment-16290817 ] ASF subversion and git services commented on SYNCOPE-1251: -- Commit afc353944f13d2d124b89ee317b1f50df6667d90 in syncope's branch refs/heads/2_0_X from [~mdisabatino] [ https://git-wip-us.apache.org/repos/asf?p=syncope.git;h=afc3539 ] [SYNCOPE-1251] Fix Update Activiti service task > UserTO variable is not updated during Update Activiti Task > -- > > Key: SYNCOPE-1251 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1251 > Project: Syncope > Issue Type: Bug > Components: core >Affects Versions: 2.0.6 >Reporter: Marco Di Sabatino Di Diodoro > Fix For: 2.0.7, 2.1.0 > > > During the update process, the variable userTO is not updated in the > workflow. > In the approval phase, if you make a change to the user, the userTO doesn't > match the current one. This causes a wrong user patch. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (SYNCOPE-1251) UserTO variable is not updated during Update Activiti Task
[ https://issues.apache.org/jira/browse/SYNCOPE-1251?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16290816#comment-16290816 ] ASF subversion and git services commented on SYNCOPE-1251: -- Commit 265b2a7d7b72634716c58be8d9890a0244888367 in syncope's branch refs/heads/master from [~mdisabatino] [ https://git-wip-us.apache.org/repos/asf?p=syncope.git;h=265b2a7 ] [SYNCOPE-1251] Fix Update Activiti service task > UserTO variable is not updated during Update Activiti Task > -- > > Key: SYNCOPE-1251 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1251 > Project: Syncope > Issue Type: Bug > Components: core >Affects Versions: 2.0.6 >Reporter: Marco Di Sabatino Di Diodoro > Fix For: 2.0.7, 2.1.0 > > > During the update process, the variable userTO is not updated in the > workflow. > In the approval phase, if you make a change to the user, the userTO doesn't > match the current one. This causes a wrong user patch. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (SYNCOPE-1251) UserTO variable is not updated during Update Activiti Task
Marco Di Sabatino Di Diodoro created SYNCOPE-1251: - Summary: UserTO variable is not updated during Update Activiti Task Key: SYNCOPE-1251 URL: https://issues.apache.org/jira/browse/SYNCOPE-1251 Project: Syncope Issue Type: Bug Components: core Affects Versions: 2.0.6 Reporter: Marco Di Sabatino Di Diodoro Fix For: 2.0.7, 2.1.0 During the update process, the variable userTO is not updated in the workflow. In the approval phase, if you make a change to the user, the userTO doesn't match the current one. This causes a wrong user patch. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
