[
https://issues.apache.org/jira/browse/SYNCOPE-297?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13566513#comment-13566513
]
Francesco Chicchiriccò edited comment on SYNCOPE-297 at 1/30/13 2:36 PM:
-------------------------------------------------------------------------
Provided that, as I say above, the value of MappingItemTO.extAttrName is
ignored by core for AccountId and Password items, why not setting both values
to null (as in 1_0_X) from the admin console?
was (Author: ilgrosso):
Provided that, as I say above, the value of MappingItemTO.extAttrName is
ignored by core for AccountId and Password items, why not setting both to
values to null (as in 1_0_X) from the admin console?
> 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
