You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@syncope.apache.org by "Francesco Chicchiriccò (JIRA)" <ji...@apache.org> on 2016/04/20 10:49:25 UTC
[jira] [Commented] (SYNCOPE-832) Mapping settings doesn't save
[ https://issues.apache.org/jira/browse/SYNCOPE-832?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15249504#comment-15249504 ]
Francesco Chicchiriccò commented on SYNCOPE-832:
------------------------------------------------
{quote}
Actually this issue blocks all my further tasks, so I'll be happy if there any workaround
{quote}
Hi [~gordeychuk.s],
the only workarounds available at the moment are either via Java client or Swagger UI, none of them being particularly comfortable.
Hang tight, SYNCOPE-801 should be resolved soon for 2.0.0-SNAPSHOT.
Regards.
> Mapping settings doesn't save
> ------------------------------
>
> Key: SYNCOPE-832
> URL: https://issues.apache.org/jira/browse/SYNCOPE-832
> Project: Syncope
> Issue Type: Bug
> Components: console, core
> Affects Versions: 2.0.0-M2
> Environment: Tomcat 8.0.33
> Amazon Linux AMI release 2014.03
> Syncope 2.0.0-M2 (installed via jar installed)
> ldap connector version: 1.5.0
> Reporter: Sergey Gordeychuk
> Priority: Critical
>
> *Steps to reproduce:*
> # Create LDAP connector (heartbeat check is ok, so connection to LDAP server works ok)
> # Create Resource for this LDAP connector
> # Go to provisioning tab
> # Create mapping for USER or GROUP entity
> # Fill with info and click save
> # Close this popup
> # Click Edit resource and go to Provisioning tab
> *Expected result:*
> Mapping settings saved
> *Actual result:*
> Mapping settings doesn't saved and I can't pull info from LDAP server because pulling tasks said that "No mapping configured for both users and groups: aborting... "
> https://www.dropbox.com/s/uvgptqs5721uyu3/log.zip?dl=0
> I attached DEBUG log files with process of creating mapping
> Actually this issue blocks all my further tasks, so I'll be happy if there any workaround
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)