[jira] [Updated] (SYNCOPE-836) can't log in back again after logout and delete cookies on Firefox and no error message shown
[ https://issues.apache.org/jira/browse/SYNCOPE-836?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matteo Di Carlo updated SYNCOPE-836: Description: on Firefox: -Log in with existing user -Log out -delete cookies -can't log back in and no error message shown was: on Firefox: -Log in with existing user -Log out -delete cookies -can't log back in Summary: can't log in back again after logout and delete cookies on Firefox and no error message shown (was: can't log in back again after logout and delete cookies on Firefox.) > can't log in back again after logout and delete cookies on Firefox and no > error message shown > - > > Key: SYNCOPE-836 > URL: https://issues.apache.org/jira/browse/SYNCOPE-836 > Project: Syncope > Issue Type: Bug > Components: enduser >Affects Versions: 2.0.0 > Environment: Firefox >Reporter: Matteo Di Carlo >Assignee: Matteo Di Carlo > Fix For: 2.0.0 > > > on Firefox: > -Log in with existing user > -Log out > -delete cookies > -can't log back in and no error message shown -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (SYNCOPE-836) can't log in back again after logout and delete cookies on Firefox.
Matteo Di Carlo created SYNCOPE-836: --- Summary: can't log in back again after logout and delete cookies on Firefox. Key: SYNCOPE-836 URL: https://issues.apache.org/jira/browse/SYNCOPE-836 Project: Syncope Issue Type: Bug Components: enduser Affects Versions: 2.0.0 Environment: Firefox Reporter: Matteo Di Carlo Assignee: Matteo Di Carlo Fix For: 2.0.0 on Firefox: -Log in with existing user -Log out -delete cookies -can't log back in -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (SYNCOPE-835) Allow to configure groups' type extensions
Francesco Chicchiriccò created SYNCOPE-835: -- Summary: Allow to configure groups' type extensions Key: SYNCOPE-835 URL: https://issues.apache.org/jira/browse/SYNCOPE-835 Project: Syncope Issue Type: Improvement Components: console Reporter: Francesco Chicchiriccò Fix For: 2.0.0 Add the option, for a given group, to specify which additional classes are assigned to users or any objects with membership of such group (this is referenced as type extension). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (SYNCOPE-818) Allow to optionally specify the MappingItemTransformer class, for each mapping item
[
https://issues.apache.org/jira/browse/SYNCOPE-818?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
fabio martelli reassigned SYNCOPE-818:
--
Assignee: fabio martelli
> Allow to optionally specify the MappingItemTransformer class, for each
> mapping item
> ---
>
> Key: SYNCOPE-818
> URL: https://issues.apache.org/jira/browse/SYNCOPE-818
> Project: Syncope
> Issue Type: Improvement
> Components: console
>Reporter: Francesco Chicchiriccò
>Assignee: fabio martelli
> Fix For: 2.0.0
>
>
> It is now possible, for each row of the mapping, for a given objectclass on a
> given resource, to specify an optional {{MappingItemTransformer}} which will
> take care of transforming attribute values during propagation and / or pull.
> While this is possible via REST, the admin console does not allow it yet.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Resolved] (SYNCOPE-801) Provisioning mappings are not saved
[ https://issues.apache.org/jira/browse/SYNCOPE-801?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] fabio martelli resolved SYNCOPE-801. Resolution: Fixed > Provisioning mappings are not saved > --- > > Key: SYNCOPE-801 > URL: https://issues.apache.org/jira/browse/SYNCOPE-801 > Project: Syncope > Issue Type: Bug > Components: console >Affects Versions: 2.0.0-M2 >Reporter: Colm O hEigeartaigh >Assignee: fabio martelli > Fix For: 2.0.0 > > Attachments: syncope-missing-mappings.png > > > A fairly major bug here unless I am being stupid again. When I create a new > provisioning mapping when creating a resource, it appears to save > successfully. However when I edit the resource again, no provisioning > mappings appear in the UI. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (SYNCOPE-801) Provisioning mappings are not saved
[ https://issues.apache.org/jira/browse/SYNCOPE-801?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15253603#comment-15253603 ] ASF subversion and git services commented on SYNCOPE-801: - Commit daecdbbc02f6b9011b8b3e721d6c8ec89abf9169 in syncope's branch refs/heads/master from [~fmartelli] [ https://git-wip-us.apache.org/repos/asf?p=syncope.git;h=daecdbb ] [SYNCOPE-801] provides fix for provision rules management > Provisioning mappings are not saved > --- > > Key: SYNCOPE-801 > URL: https://issues.apache.org/jira/browse/SYNCOPE-801 > Project: Syncope > Issue Type: Bug > Components: console >Affects Versions: 2.0.0-M2 >Reporter: Colm O hEigeartaigh >Assignee: fabio martelli > Fix For: 2.0.0 > > Attachments: syncope-missing-mappings.png > > > A fairly major bug here unless I am being stupid again. When I create a new > provisioning mapping when creating a resource, it appears to save > successfully. However when I edit the resource again, no provisioning > mappings appear in the UI. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (SYNCOPE-790) Allow user / group / any object admin form customization
[ https://issues.apache.org/jira/browse/SYNCOPE-790?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Francesco Chicchiriccò reassigned SYNCOPE-790: -- Assignee: Francesco Chicchiriccò > Allow user / group / any object admin form customization > > > Key: SYNCOPE-790 > URL: https://issues.apache.org/jira/browse/SYNCOPE-790 > Project: Syncope > Issue Type: New Feature > Components: console >Reporter: Francesco Chicchiriccò >Assignee: Francesco Chicchiriccò > Fix For: 2.0.0 > > > In Syncope 1.2 there used to be the possibility to determine which fields to > show (and in which order) by configuring from admin console. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
