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

Colm O hEigeartaigh commented on SYNCOPE-297:
---------------------------------------------

Hi Jan,

Could you elaborate on what exception you are getting? I am not seeing an 
exception there.

I believe the problem is due to the functionality added in MappingTO on trunk. 
A AccountId MappingItemTO object has an external attribute name of "__NAME__" 
and "__PASSWORD__" for a Password object. On 1.0.x they just have "null". This 
appears to be confusing the Wicket DropdownChoice, as it is getting initialized 
with a value that does not correspond to the choices (GIVENNAME + SURNAME) in 
this case.

Questions:

 A) Should MappingItemTO have defined external attribute names added for 
AccountID/Passwords?
 B) If the answer to (A) is yes, then I can just remove the external attribute 
choices for AccountID/Password mappings.

Colm.
                
> External Attributes are showing up for AccoundId/Password in Resource User 
> Mappings
> -----------------------------------------------------------------------------------
>
>                 Key: SYNCOPE-297
>                 URL: https://issues.apache.org/jira/browse/SYNCOPE-297
>             Project: Syncope
>          Issue Type: Bug
>            Reporter: Colm O hEigeartaigh
>            Assignee: Colm O hEigeartaigh
>             Fix For: 1.1.0
>
>         Attachments: Screenshot.png
>
>
> I have a Database Connector for a H2 backend with a simple table. I am 
> creating a Resource User Mapping of Username -> Account Id, Password -> 
> Password, and a User schema 'surname' attribute -> SURNAME column in the 
> table.
> The Resource now creates ok, however when I edit it and look at the User 
> mappings, I see that another column name 'GIVENNAME' is appearing as the 
> external attribute for the User Account Id and Password mappings.

--
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