On Thu, Oct 19, 2017 at 5:21 PM, Niveathika Rajendran
wrote:
> Hi all,
>
> The following points outline the integration of Stream Processor with an
> Identity Provider. Identity Provider Client interface will act as the
> mediator between SP components and Identity Provider.
On Thu, Oct 19, 2017 at 5:21 PM, Niveathika Rajendran
wrote:
> Hi all,
>
> The following points outline the integration of Stream Processor with an
> Identity Provider. Identity Provider Client interface will act as the
> mediator between SP components and Identity Provider.
Hi all,
The following points outline the integration of Stream Processor with an
Identity Provider. Identity Provider Client interface will act as the
mediator between SP components and Identity Provider. The points are
divided into to two main parts based on the authentication mechanism.
*Basic
We had same kind of implementation in C4 by using tomcat valve instead of
filters. May not be same pattern what we expect here.[1]
[1] http://harshathirimanna.blogspot.com/2016/11/
authentication-authorization-common.html
And as I remember we did that to C5 as well by Ruwan using C4
Hi all,
We (Prabath, NuwanD, Suho, few IS team members, few analytics team members)
had an offline discussion regarding $ Subject.
*Problem*
With the new rewrite of C5 based products, we have moved from SOAP based
backend product APIs to REST APIs. And there needs to be a mechanism to
secure