[
https://issues.apache.org/jira/browse/SYNCOPE-806?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15224333#comment-15224333
]
Francesco Chicchiriccò commented on SYNCOPE-806:
The actual issue here is that, when defining the mapping for a given
{{AnyType}} A, only attributes defined in A classes are considered by the admin
console; in the case above, the {{USER}} AnyType does not have the {{generic
membership}} AnyTypeClass, where {{postalAddress}} is defined.
The proper fix here is to add, to the {{Provision}} entity the list of
auxiliary classes to be considered with the mapping.
This means that, for the resource {{resource-ldap}} and the AnyType {{USER}},
Syncope will let to optionally specify {{generic membership}} as auxiliary
AnyTypeClass; by consequence, the admin console will include, besides the plain
schemas defined in the class(es) for {{USER}}, the plain schemas defined in
{{generic membership}}, when selecting {{UserPlainSchema}} as internal mapping
type.
> Validate "standalone" resource provisioning
> ---
>
> Key: SYNCOPE-806
> URL: https://issues.apache.org/jira/browse/SYNCOPE-806
> Project: Syncope
> Issue Type: Improvement
> Components: console
>Affects Versions: 2.0.0-M2
>Reporter: Colm O hEigeartaigh
>Assignee: Francesco Chicchiriccò
>Priority: Minor
> Fix For: 2.0.0
>
>
> A lot of the resources configured in the "standalone" distribution appear to
> be missing internal attributes in the provisioning mappings. For example, in
> "resource-ldap" no internal attribute is specified for the mapping to
> "postal". So if you click "Next" on the mapping page you get an error.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
