Hi Esteve,

Can you change your configuration as follows:

@Inject
private EEJPAContextInitializer contextInitializer;

/**

• This method uses the IdentityConfigurationBuilder to create an IdentityConfiguration, which
• defines how PicketLink stores identity-related data. In this particular example, a
• JPAIdentityStore is configured to allow the identity data to be stored in a relational database
• using JPA.
  */
  public void initConfig(@Observes IdentityConfigurationEvent event) { IdentityConfigurationBuilder builder = event.getConfig(); builder .named("default") .stores() .jpa() .mappedEntity( AccountTypeEntity.class, RoleTypeEntity.class, GroupTypeEntity.class, IdentityTypeEntity.class, RelationshipTypeEntity.class, RelationshipIdentityTypeEntity.class, PartitionTypeEntity.class, PasswordCredentialTypeEntity.class, AttributeTypeEntity.class) .supportGlobalRelationship(Relationship.class) .addContextInitializer(this.contextInitializer) // Specify that this identity store configuration supports all features .supportAllFeatures(); }

Instead of producing an IdentityConfiguration instance, try to observe the IdentityConfigurationEvent and use the builder to provide your configuration.

We've found an issue when producing the IdentityConfiguration that makes the attribute support not being considered when reading the configuration from it.

This is already fixed for 2.5.2. Which will be released this week.

Thanks.