Hi Ishara,
The idea was not to share the user store with SP , Within SP we will not
check whether the user is a subscriber or API Creator, we will let the user
make changes to those tables if the user is an Admin. The admin can be a
subscriber or Api Creator.
Ideally we should have this in
Hi Dinusha,
According to what is discussed with the APIM team( Fazlan and chamila) we
will let the admins configure values for both tables, and within the SP we
will not check whether he is an Api Creator or Subscriber.
On Thu, Aug 9, 2018 at 10:16 AM, Dinusha Dissanayake
wrote:
> Hi Silmy,
Hi Silmy,
Hi all,
>
> According to the current implementation of APIM Analytics , we use
> percentile values to find out certain threshold values (eg:- Abnormal
> request count) . Since generating alerts using percentile values creates
> lots of complexity to the users of the alert, it was
Hi Silmy,
Few things to consider when implementing the gadgets.
1) Only users with a specific role(preferably admin) should be able to do
CRUD on those tables. I think we can change this role using SP
configurations if a customer intends to allow users with another role to do
this task.
2)
Hi Silmy,
1. Let the admins or subcribers set those values in APIM side and
publish it to SP as a stream. A siddhi app can be written to listen to the
stream an store it in database
2. Let the admins or subscriber set a value at SP dashboard itself
using a dashboard widget
If
Hi all,
According to the current implementation of APIM Analytics , we use
percentile values to find out certain threshold values (eg:- Abnormal
request count) . Since generating alerts using percentile values creates
lots of complexity to the users of the alert, it was decided to move
towards a
Hi all,
Currently, I am working on a project to manage function libraries in
adaptive authentication. Here is a brief summary of the project and my
progress.
Introduction:
WSO2 Identity server has a feature called script based adaptive
authentication. It provides the facility to change the
