[ 
https://issues.apache.org/jira/browse/SYNCOPE-221?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13484741#comment-13484741
 ] 

Jan Bernhardt commented on SYNCOPE-221:
---------------------------------------

Wouldn't it be better to show or hide this field (AccountLink) depending on the 
chosen connector bundle, instead of providing an enable/disable checkbox?

Users new to Syncope wouldn't know when to enable or disable AccountLink and 
this could cause some confusion. But if this field is only available when 
required from the connector bundle, this field could also become mandatory and 
thus prevent configuration errors (both ways, also for connectors not requiring 
an AccountLink).

The missing piece here is, how to identify if a connector bundle requires an 
AccountLink or not? Is there some kind of information available within the 
connector bundle?
Any Ideas?

Regards
Jan



                
> Let user explicitly choose to give value for AccountLink (when defining 
> resource schema mapping)
> ------------------------------------------------------------------------------------------------
>
>                 Key: SYNCOPE-221
>                 URL: https://issues.apache.org/jira/browse/SYNCOPE-221
>             Project: Syncope
>          Issue Type: Improvement
>          Components: console
>            Reporter: Francesco Chicchiriccò
>            Assignee: Colm O hEigeartaigh
>             Fix For: 1.1.0-incubating
>
>         Attachments: syncope-221.patch
>
>
> Resource modal window currently shows an input value for AccountLink: 
> however, this value is (currently) only meaningful for LDAP and 
> ActiveDirectory connector bundles but might cause misbehaviours when provided 
> for other connector bundle.
> It would be best to hide this field by default, allowing users to choose when 
> to give value for this.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Reply via email to