|
Description:
|
Considering
Consider
the following configuration, where we have a
custom Partition
CustomPartition
type defined:
{code}
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"));
{code}
When adding a CustomPartition instance, it always fails because PicketLink does not identify a store
to support
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:
{code}
IdentityConfigurationBuilder builder = new IdentityConfigurationBuilder();
builder
.named("default")
.stores()
.file()
.supportType(Partition.class)
.supportType(IdentityType.class)
.supportType(Relationship.class);
{code}
|
