My responses inline.
On Wed, Jan 27, 2016 at 2:16 PM, Chanaka Fernando wrote:
> Hi Dulitha,
>
> AFAIU, we can use this tool to write our synapse configurations in a way
> that we write a code in a scripting language. This tool will convert the
> script into a synapse
Hi Ruwan ,
I will look on your suggestion.
*Thank youVivekananthan Sivanayagam*
*Associate Software Engineer | WSO2*
*E:vivekanant...@wso2.com *
*M:+94752786138*
On Mon, Feb 1, 2016 at 12:23 PM, Ruwan Abeykoon wrote:
> Hi All,
> Please watch
Hi All,
I believe we should integrate Log Analyzer with analytics distributions of
the products.
It is true some of the information you can take from Log analyzer is
already available under normal analytics. For those, we do not need to use
Log analyzer.
However, log analyzer let us find and
Hi,
The initial use case I had with Log Analyzer was, as a general log analysis
tool, where users can just point to a log location, can be WSO2/non-WSO2
logs, and run queries against it / create dashboards. The concern I've with
integrating log analyzer also with our new analytics distributions
On Mon, Feb 1, 2016 at 2:21 PM, Anjana Fernando wrote:
> Hi,
>
> The initial use case I had with Log Analyzer was, as a general log
> analysis tool, where users can just point to a log location, can be
> WSO2/non-WSO2 logs, and run queries against it / create dashboards. The
>
Hi Harshan/Chathura,
@Harshan - As Ayyoob mentioned, we can use a custom grant type
handler for retrieving tokens.
@Chathura - The technician will login to the command line tool and carry
out operations, this avoids the need to type credentials to the device each
time we need to enroll.
Since
On Mon, Feb 1, 2016 at 2:35 PM, Srinath Perera wrote:
>
>
> On Mon, Feb 1, 2016 at 2:21 PM, Anjana Fernando wrote:
>
>> Hi,
>>
>> The initial use case I had with Log Analyzer was, as a general log
>> analysis tool, where users can just point to a log location,
Hi,
Developing Log Analyzer as a generic log analysis tool and building log
analysis apps per specific products is the ideal option IMO. So there will
be a log analytics apps store which has WSO2 product specific log analysis
configurations + any custom log analysis solutions. Then anyone who
On Mon, Feb 1, 2016 at 6:14 PM, Kasun Dananjaya Delgolla
wrote:
> Hi Lakshman,
>
> In terms of Android you can use blocking APIs[1] in Marshmallow SDK (SDK
> 23) to achieve this. We already use DevicePolicyManager API so you can
> straightaway add these new stuff into the same
Hi Inosh,
Please find my questions regarding this process as follows.
[1] How are we planning to get an OOT for each serial and in-case of an
unenrollment, what is the process of getting a new OOT?
[2] Here, are plainning to do an enrollment without associating a user? if
not, how will be other
Hi,
There is a requirement to implement application white listing and
application black listing support in Enterprise Mobility Manager.
Application white listing means creating a list of applications which are
only allowed to run on mobile devices which are connected to EMM.
Application
Hi Lakshman,
In terms of Android you can use blocking APIs[1] in Marshmallow SDK (SDK
23) to achieve this. We already use DevicePolicyManager API so you can
straightaway add these new stuff into the same android agent API layer.
Also for older API levels ( < 23) earlier we used a mechanism just
Hi,
I am in the process of implementing the device reboot support for EMM. This
feature will be available for allowed EMM user roles to restart the device
remotely. There will be an operation added to the device view of the
console.
In case of Android, the agent application will need to
Hi Dilan,
[1] How are we planning to get an OOT for each serial and in-case of an
unenrollment, what is the process of getting a new OOT?
Enrollment in this kind of a scenario, will only be done by a specific user
in a role, and those users only. If unenrolled, the device must be handed
to the
Hi all,
Role based application restriction will be provided. Administrator will
define a list of applications as a black list and a set of roles which is
to be restricted to the application, along with the applications.
Is there any particular reason for not having application policies for
Hi Inosh,
There may be some cases where enterprises need to have application policies
for individual users. But I think that scenario is very unlikely. If we
take an organization, every user will map to one or more user-roles. There
might be situations where a role has only one user (i.e like
Hi Seshika,
Thinking about this, I think we should replace the line chart with a
Heatmap that has time (as days) as X axis and user, role, service provider,
ip ( user can pick any) y axis because heatmap is much better on drill down
and exploration.
[image: Inline image 2]
Then user can click
@Lahiru: +1. I'm hoping to analyze the data that we can get from IS so that
we can design some more, relevant analytics from it. I'll add more
authorization specific analytics as you have mentioned.
@Srinath: +1. I'll change the line graphs to this.
On Tue, Feb 2, 2016 at 9:33 AM, Srinath Perera
Hi All,
WSO2 CEP Team is pleased to announce the Alpha release of WSO2 Complex
Event Processor 4.1.0.
WSO2 Complex Event Processor (CEP) can be used to identify the most
meaningful events within an event cloud, analyzes their impacts, and acts
on them in real time. Built to be extremely high
Hi Seshi,
I think we can consider Authorization stats also. Since WSO2 IS has a good
implementation of XACML spec, we can collect stats on, the requests
allowed, denied, with which granularity, etc.
Thanks.
On Mon, Feb 1, 2016 at 1:59 PM, Seshika Fernando wrote:
> Hi all,
>
20 matches
Mail list logo