Hi,
Good to hear it's helpful ;)
It's indeed 100% used for access (configuring + activation) of the build-in
identity stores.
The stores that the application supplied are picked and activated by simply
being there, given that they are enabled CDI beans.
Kind regards,
Arjan Tijms
On Mon, Mar 20, 2017 at 11:37 PM, Will Hopkins <will.hopkins_at_oracle.com>
wrote:
> Hi Arjan,
>
> Yes, very helpful.
>
> Given that the implementation chooses which IdentityStore class to use, is
> it fair to say that the intent is for this to be used for declarative
> access to the built in IdentityStores? I.e., not for IdentityStores the
> application might supply?
>
> Thanks,
>
> Will
>
>
> On March 20, 2017 3:25:43 PM EDT, arjan tijms <arjan.tijms_at_gmail.com>
> wrote:
>>
>> Hi Will,
>>
>> The LdapIdentityStoreDefinition annotation and annotations like that,
>> function essentially as declarative Bean Factories. They are modelled after
>> the existing DataSourceDefinition annotation in Java EE.
>>
>> The annotation can be placed on whatever class seen by CDI. When it's
>> encountered by the CDI extension responsible for processing it, it causes
>> another bean to be programmatically introduced into the CDI context with
>> parameters such as set on the *Definition annotation. The actual type of
>> the bean is left to the implementation, but it implements the IdentityStore
>> interface.
>>
>> This can be seen when looking at the following code from the CdiExtension
>> class in Soteria:
>>
>> Optional<LdapIdentityStoreDefinition> optionalLdapStore =
>>
>> getAnnotation(
>>
>> beanManager,
>>
>> event.getAnnotated(),
>>
>> LdapIdentityStoreDefinition.class);
>>
>>
>> if (optionalLdapStore.isPresent()) {
>>
>> identityStoreBeans.add(new CdiProducer<IdentityStore>()
>>
>> .scope(ApplicationScoped.class)
>>
>> .beanClass(IdentityStore.class)
>>
>> .types(Object.class, IdentityStore.class,
>> LdapIdentityStore.class)
>>
>> .addToId(LdapIdentityStoreDefinition.class)
>>
>> .create(e -> new LdapIdentityStore(optionalLdapStore
>> .get()))
>>
>> );
>>
>> }
>>
>> So per the above code, if an "LdapIdentityStoreDefinition" annotation is
>> present, a Bean<T> is programmatically added, with the actual
>> implementation backed by "org.glassfish.soteria.identitystores.
>> LdapIdentityStore".
>>
>> Hope this helps ;)
>>
>> Kind regards,
>> Arjan Tijms
>>
>>
>> On Mon, Mar 20, 2017 at 5:36 PM, Will Hopkins <will.hopkins_at_oracle.com>
>> wrote:
>>
>>> Arjan, et al.:
>>>
>>> How are those meant to be used? What class would be annotated with,
>>> e.g., LdapIdentityStoreDefinition, and what is the intended effect? Are
>>> they used only to configured the container-provided default impls? Only
>>> application-supplied impls? If the latter, does that mean that the
>>> container-supplied impls are always configured by the container (and not
>>> configurable by users)?
>>>
>>> Sorry if I'm being dense here, but don't understand the model.
>>>
>>> Thanks,
>>>
>>> Will
>>>
>>> --
>>> Will Hopkins | WebLogic Security Architect | +1.781.442.0310 <(781)%20442-0310>
>>> Oracle Application Development
>>> 35 Network Drive, Burlington, MA 01803
>>>
>>>
>>
> --
> Will Hopkins | Platform Security Architect | +1.781.442.0310
> <(781)%20442-0310>
> Oracle Cloud Application Foundation
>
> 35 Network Drive, Burlington, MA 01803
>