Hi Dilini,
Thanks for the suggestion. I will follow the 1st approach and let you know
the progress.
Regards,
Dimuth
On Mon, Jun 11, 2018 at 6:05 PM Dilini Muthumala wrote:
> Hi Dimuth,
>
> From the given information, it seems option #1 would be better. This is
> because the user validation
Hi Dimuth,
>From the given information, it seems option #1 would be better. This is
because the user validation must happen realtime.
Joining an input event (authentication request, in this case) against a
table and extracting a result in realtime is a common usecase for SP.
However we should
Adding Tishan and SajithR
On Mon, Jun 11, 2018 at 5:07 PM Dimuth Menikgama wrote:
> Hi all,
>
> I have a custom requirement of publishing a set of attributes to Stream
> Processor in each time a user is successfully authenticated. That event is
> persisted and stored in a relational database
Hi all,
I have a custom requirement of publishing a set of attributes to Stream
Processor in each time a user is successfully authenticated. That event is
persisted and stored in a relational database via SP app. When the same
user tries to authenticate for the second time, I need to validate the