IMO this is only used in metadata service at the moment, if so shall we
place this in metadata service component?
On Fri, Nov 28, 2014 at 5:11 PM, Udara Liyanage wrote:
>
>
> On Fri, Nov 28, 2014 at 5:01 PM, Sajith Kariyawasam
> wrote:
>
>> Should this handler need to be bundle with all the pro
On Fri, Nov 28, 2014 at 5:01 PM, Sajith Kariyawasam wrote:
> Should this handler need to be bundle with all the products? In a
> distributed setup, to which product(s) (SM / CC / AS ..) this should goes
> to ?
>
SM only . May be some part is relevant for metadata service which I am not
sure for
Hi,
IMO is this should be go with separate component. It helps easy when
extending it further.
Thanks !
On Fri, Nov 28, 2014 at 5:01 PM, Sajith Kariyawasam wrote:
> Should this handler need to be bundle with all the products? In a
> distributed setup, to which product(s) (SM / CC / AS ..) this
Hi Udara,
On Fri, Nov 28, 2014 at 4:47 PM, Udara Liyanage wrote:
> Hi,
>
> As I mentioned in a previous mail, I wrote a custom token handler in order
> to generate a JWT token. My concern is how to add this to product. Either
> need to write a separate component or add to an existing one.
> Wri
Should this handler need to be bundle with all the products? In a
distributed setup, to which product(s) (SM / CC / AS ..) this should goes
to ?
On Fri, Nov 28, 2014 at 4:47 PM, Udara Liyanage wrote:
> Hi,
>
> As I mentioned in a previous mail, I wrote a custom token handler in order
> to genera
Hi,
As I mentioned in a previous mail, I wrote a custom token handler in order
to generate a JWT token. My concern is how to add this to product. Either
need to write a separate component or add to an existing one.
Writing a separate component to just a single class won't worth from one
aspect gi
