Hi Pulasthi,
On Mon, Jun 11, 2018 at 11:36 AM Pulasthi Mahawithana
wrote:
> Hi Senthalan,
>
> On Mon, Jun 11, 2018 at 11:10 AM Senthalan Kanagalingam <
> sentha...@wso2.com> wrote:
>
>> Hi all,
>>
>> I am working on the $subject. The purpose of this implementation is to
>> have
Its more of a convention. Since our C4 code is tenant aware, we have a
convention to put the tenant id in all the tables so that we can use it for
things outside application logic. Such as tenant data removal/cleanup,
audits, etc.
On Mon, Jun 11, 2018 at 2:15 PM, Vithursa Mahendrarajah
wrote:
>
Hi Godwin,
Sorry, I misunderstood your previous mail. Currently we don't have a
specific need to use tenant_id from AM_APPLICATION_ATTRIBUTES. We have
added it for future references.
Thanks,
On Mon, Jun 11, 2018 at 1:28 PM, Godwin Amila Shrimal
wrote:
> Hi Vithursa,
>
> What I asked is do we
Hi Vithursa,
What I asked is do we really need to keep tenant_id in
AM_APPLICATION_ATTRIBUTES table since we already have tenancy in
Application level ? I guess Application to application attribute has an one
to many relationship.
Thanks
Godwin
On Mon, Jun 11, 2018, 6:43 AM Vithursa
Hi Jerad,
On Sat, Jun 9, 2018 at 10:53 AM Jerad Rutnam wrote:
> Hi Pulasthi,
>
> A minor suggestion on the below configuration part readability.
>
> {authenticationOptions:[
>
> {authenticator:'basic'},
> {idp:'Twitter'},
> {idp:'myIdp', authenticator:'samlsso'}]},
>
> So in the options array
Hi Senthalan,
On Mon, Jun 11, 2018 at 11:10 AM Senthalan Kanagalingam
wrote:
> Hi all,
>
> I am working on the $subject. The purpose of this implementation is to
> have application-specific configurations for authenticators. Currently, we
> can static configurations for the authenticators in
