[
https://issues.apache.org/jira/browse/SYNCOPE-297?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Colm O hEigeartaigh updated SYNCOPE-297:
----------------------------------------
Attachment: syncope-297.patch
Hi guys,
I'd like some feedback on the attached patch. It does two things:
a) Removes the external attribute values for AccountId/Passwords in the
MappingTO class (ignored by core anyway)
b) Disables the ext attr dropdown list when it's an account id or password
This fixes the problem reported in the JIRA. I've run into a similar problem
though. If you edit the user mappings, and de-select the AccountId checkbox and
click on the extr attribute dropdown list (but don't select a value, just click
on it), and then re-click on AccountId, you get a "extAttrName is required"
error message. Any ideas?
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, syncope-297.patch
>
>
> 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
