On 29/01/2013 11:45, Colm O hEigeartaigh wrote:
Do you have such column GIVENNAME in the table configured for your H2 resource,
right?
Yep.
This is normally happening because the admin console tries to populate the "external
attribute name" field, for non-AccountId non-Password rows, by calling schema() on
the underlying connector.
But the problem is that it is doing this for the AccountId + Password rows?
Oh, sorry, I didn't get it: definitely, it's a problem - the core will
discard such values, but it's anyway to be fixed.
Regards.
On Tue, Jan 29, 2013 at 10:35 AM, Francesco Chicchiriccò <
ilgro...@apache.org> wrote:
On 29/01/2013 11:31, Colm O hEigeartaigh wrote:
Thanks Jan! Fix confirmed. However I am running into a number of strange
problems still on trunk. I alluded to this problem earlier: 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.
Can someone confirm this?
Do you have such column GIVENNAME in the table configured for your H2
resource, right?
This is normally happening because the admin console tries to populate the
"external attribute name" field, for non-AccountId non-Password rows, by
calling schema() on the underlying connector.
Regards.
--
Francesco Chicchiriccò
ASF Member, Apache Syncope PMC chair, Apache Cocoon PMC Member
http://people.apache.org/~ilgrosso/
