[
https://issues.apache.org/jira/browse/SYNCOPE-297?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13566510#comment-13566510
]
Colm O hEigeartaigh commented on SYNCOPE-297:
---------------------------------------------
Hi Francesco,
>> A) Should MappingItemTO have defined external attribute names added for
>> AccountID/Passwords?
> Having said that, I don't understand exactly what you mean with your question
> (A); however, IMO you can just proceed with (B).
What I meant was that the 'addAccountIdItem' method here:
http://svn.apache.org/viewvc/syncope/trunk/common/src/main/java/org/apache/syncope/common/to/MappingTO.java?view=markup
is explicitly setting "accountIdItem.setExtAttrName("__NAME__");" (and similar
for the Password case). I was wondering whether it should be doing this, as on
1.0.x the corresponding getExtAttrName() for the AccountId Mapping returns
null. If I set the above call to null then all of the tests pass.
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
