On Sun, Dec 13, 2015 at 2:05 AM, Michael Perelman < [email protected]> wrote:
> thanks for all the info so far, Kiran! > if i could just step back one email, please. current ServiceBuilder allows > for the OOTB AuthenticationInterceptor's password policy bean's attributes > to be copied over to the PasswordPolicyConfiguration within the > createPwdPolicyConfig() function, which eventually makes its way to the > interceptor. the attribute copying logic is specific to that interceptor, > so it would not work for my custom interceptor, unless i introduced my own > service builder by extending the OOTB ServiceBuilder. my question is how do > i go about letting the server know that my service builder is the one that > needs to be called upon startup instead of the OOTB one? thanks! > one way is to make your authenticator a subclass of AuthenticationInterceptor the only way to make this possible without changing the > > > Date: Sat, 12 Dec 2015 11:31:14 +0800 > > Subject: Re: custom interceptor's AdsBaseBean > > From: [email protected] > > To: [email protected] > > > > On Sat, Dec 12, 2015 at 7:08 AM, Michael Perelman < > > [email protected]> wrote: > > > > > so where do i place the jar with my new classes? your outdated doc > states > > > that it should be placed in HOME/lib/ext, but there is no such dir in > > > 2.0.0M17. should i place it in HOME/lib alongside the > > > apacheds-service-2.0.0-M17.jar file? also, do i need to record my jar's > > > presence in some config file, or will it be automatically picked up by > the > > > virtue of it residing within the /lib dir? > > > > > place it under lib and restart, that is all > > > > > > > > > Date: Fri, 11 Dec 2015 16:01:34 +0800 > > > > Subject: Re: custom interceptor's AdsBaseBean > > > > From: [email protected] > > > > To: [email protected] > > > > > > > > On Fri, Dec 11, 2015 at 8:29 AM, Michael Perelman < > > > > [email protected]> wrote: > > > > > > > > > ok, looks fairly clear, though please correct me if i am wrong in > the > > > > > following assumption. all the PasswordPolicyBean instances are fed > to > > > the > > > > > AuthenticationInterceptorBean since the list is tagged with > > > > > @ConfigurationElement(objectClass = "ads-passwordPolicy", > container = > > > > > "passwordPolicies"). those PasswordPolicyBean instances then get > > > passed to > > > > > all the interceptors residing within the list tagged with > > > > > @ConfigurationElement(objectClass = "ads-authenticator", container > = > > > > > "authenticators"). this passing of policies to interceptors occurs > in > > > > > ServiceBuilder.createInterceptors(). did i miss anything? thanks! > > > > > > > > > right, this is correct > > > > > > > > > > > > > > > Date: Thu, 10 Dec 2015 18:10:11 +0800 > > > > > > Subject: Re: custom interceptor's AdsBaseBean > > > > > > From: [email protected] > > > > > > To: [email protected] > > > > > > > > > > > > On Thu, Dec 10, 2015 at 3:55 PM, Michael Perelman < > > > > > > [email protected]> wrote: > > > > > > > > > > > > > hi. i am running 2.0.0M17 in regular (i.e. not embedded) mode, > and > > > i > > > > > would > > > > > > > like to introduce my own custom interceptor. i am trying to > model > > > it > > > > > after > > > > > > > the OOTB AuthenticationInterceptor, so mine will contain a > password > > > > > policy > > > > > > > bearing several attributes that will be configurable via Apache > > > Studio. > > > > > > > after digging around through the source, i came across > > > > > PasswordPolicyBean > > > > > > > class that is apparently populated with the values from such > > > > > attributes. > > > > > > > the problem is that i am unable to determine as to how the > > > attributes' > > > > > > > values get propagated to this class. i noticed that each such > > > > > attribute is > > > > > > > represented with a respective variable tagged with > > > > > > > @ConfigurationElement(attributeType = "attribute-name", > isOptional > > > = > > > > > true, > > > > > > > defaultValue = "some-val"). if i were to introduce my own > > > > > > > MyPasswordPolicyBean class, would it be enough to just create > > > variables > > > > > > > with the same @ConfigurationElement tags, or do i need to > perform > > > > > > > additional steps in order for those variables to be populated > with > > > > > their > > > > > > > respective attribute values? > > > > > > > > > > > > > for this annotation to work you need to add a new config element > in > > > > > config > > > > > > schema, then server > > > > > > will automatically populate the values in the new bean > > > > > > > > > > > > > > > > > > > > thanks! > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > -- > > > > > > Kiran Ayyagari > > > > > > http://keydap.com > > > > > > > > > > > > > > > > > > > > > > > > > > -- > > > > Kiran Ayyagari > > > > http://keydap.com > > > > > > > > > > > > > > -- > > Kiran Ayyagari > > http://keydap.com > > -- Kiran Ayyagari http://keydap.com
