I also think it is good to publish to two tenants. However we need to
validate if there are any security concerns.

E.g. let's say user John belonging to foo.com logs into travelocity.com
registered in bar.com. Tenant admin of foo.com should see it as a login
attempt in his dashboard, by one of his users for an application outside
his domain, and tenant admin of bar.com also should see it in his
dashboard, as a login attempt from a user outside his domain to one of his
apps.

On Fri, Jul 15, 2016 at 5:47 PM, Darshana Gunawardana <[email protected]>
wrote:

>
>
> On Fri, Jul 15, 2016 at 3:47 PM, Hasintha Indrajee <[email protected]>
> wrote:
>
>> Hi All,
>>
>> For SaaS application what is the tenant domain related to a login event ?
>> Is that the tenant domain which the SP is registered or is that the logged
>> in user's tenant domain ?.
>>
>> If we consider sending out tenant domain as just a record, it's fine to
>> add either (reasonable). But the problem is we need a specific tenant
>> domain to publish this event. According to the current way of event
>> publishing to the DAS, we need to start a tenant flow before publishing. In
>> this case we need a specific tenant domain to publish this event. Or else
>> do we need to publish this event to both tenant domains (starting two
>> tenant flows) in a case of SaaS app ?.
>>
>
> +1
>
>>
>>
>>
>> --
>> Hasintha Indrajee
>> WSO2, Inc.
>> Mobile:+94 771892453
>>
>>
>
>
> --
> Regards,
>
>
> *Darshana Gunawardana*Associate Technical Lead
> WSO2 Inc.; http://wso2.com
>
> *E-mail: [email protected] <[email protected]>*
> *Mobile: +94718566859 <%2B94718566859>*Lean . Enterprise . Middleware
>



-- 
Thanks & Regards,

*Johann Dilantha Nallathamby*
Technical Lead & Product Lead of WSO2 Identity Server
Governance Technologies Team
WSO2, Inc.
lean.enterprise.middleware

Mobile - *+94777776950*
Blog - *http://nallaa.wordpress.com <http://nallaa.wordpress.com>*
_______________________________________________
Dev mailing list
[email protected]
http://wso2.org/cgi-bin/mailman/listinfo/dev

Reply via email to