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

Jan Bernhardt commented on SYNCOPE-297:
---------------------------------------

Hi Colm,

when I was trying to reconstruct your issue, I discovered this error. Here is 
what I did to run into this error:

Build syncope from trunk. Start standalone version. Login as admin. Create new 
resource with predefined H2 connector. Setup some basic UserSchemaMapping. 
Saved Resource. Reopened created resource and took a look at UserSchemaMappings.

I changed port configuration from my console to 9081 so that I could monitor 
network traffic. Here I discovered "null" as a response for 
"/rest/connector/schema/list?showall=true" when handling H2 connections. By 
analyzing "null" response, I discovered previously mentioned error. I also 
tried another connector with normal results for 
"/rest/connector/schema/list?showall=true".

Best regards.
Jan



                
> 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