[ https://issues.apache.org/jira/browse/SYNCOPE-297?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13566469#comment-13566469 ]
Francesco Chicchiriccò commented on SYNCOPE-297: ------------------------------------------------ Hi Colm, MappingItemTO (as its counterpart MappingItem) is used by either user mapping (UMappingTO / UMapping) and role mapping (RMappingTO / RMapping), the latter clearly not having any password mapping item, only accountid. Please consider that both UMapping and RMapping (via their parent AbstractMapping) will force the extAttrName to be Uid.NAME (i.e. "__NAME__") or OperationalAttributes.PASSWORD_NAME (i.e. "__PASSWORD__") despite of the value contained in the correspondent TO. Having said that, I don't understand exactly what you mean with your question (A); however, IMO you can just proceed with (B). > 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