-
Bug
-
Resolution: Done
-
Major
-
PLINK_2.6.0.Beta3
-
None
Consider the following configuration, where we have a CustomPartition type defined:
IdentityConfigurationBuilder builder = new IdentityConfigurationBuilder(); builder .named("default") .stores() .file() .supportType(CustomPartition.class) .supportType(IdentityType.class) .supportType(Relationship.class); DefaultPartitionManager partitionManager = new DefaultPartitionManager(builder.buildAll()); partitionManager.add(new CustomPartition("Custom Partition")); assertNotNull(partitionManager.getPartition(CustomPartition.class, "Custom Partition"));
When adding a CustomPartition instance, it always fails because PicketLink does not identify a store that supports the CustomPartition type. In this case, the file store.
This only works if we provide a configuration using the base Partition type instead:
IdentityConfigurationBuilder builder = new IdentityConfigurationBuilder(); builder .named("default") .stores() .file() .supportType(Partition.class) .supportType(IdentityType.class) .supportType(Relationship.class);
