Hi Rajjaz ,
We have already have smsotp and email otp authenticators which are already
developed using HOTP algorithm.
I feel your mentioned authenticator also the similar one. Is there any
differences compared with above two?
Thanks.
On Mon, Mar 7, 2016 at 9:04 PM, Rajjaz Mohammed
+Adding Architecture group
On Tue, Mar 8, 2016 at 10:42 AM, Kasun Thennakoon wrote:
> Hi all,
>
> We have performed several test scenarios on Greg 5.2 , In order to find
> the optimal heap memory size for, run performance tests on the product.
> Below table compares the GC
Hi Tharindu,
On 7 March 2016 at 21:10, Sajith Ravindra wrote:
>
> 2. Having a DB based cache would persist the data even on a restart and
>> the data fetching query would be searching for an specific value(not a
>> range query as against the max-mind DB). But the downside is
> 2. Having a DB based cache would persist the data even on a restart and
> the data fetching query would be searching for an specific value(not a
> range query as against the max-mind DB). But the downside is that for a
> cache miss there would be minimum 3 DB queries (one for the cache table
>
Hi All,
i have planed to develop $Subject,
This OTP[1] relies on two basic things, a shared secret and a moving
factor. As part of the algorithm an HmacSHA1 hash of the moving factor will
be generated using the shared secret. Whenever a new OTP is generated, the
moving factor will increase.
Hi Lasantha,
Upto now we are doing the following way in order to get the geo location
from the stated dump.
1. two columns added filled with long value of lower and upper value of
network ip addresses. Then get the geoname_id with respect to the long
value for the given ip which between this
Hi All,
In AppCloud, We are implementing a feature for Application Launch. We are
considering following URL patterns and custom URL for Application Launch.
- TenantDomain-ApplicationKey-Version.services.cloud.wso2.com
The application and version specific launch URL pattern.
-
Please find design review notes,
- Continue with "container specification" term rather that container spec.
- Container names has to be defined properly (t2.small, m1.large etc).
- Check above container specifications can be provided with kubernetes.
- Add navigation link to upgrade plan
Hi all ,
I'm looking to improve the existing AmazonSNS connector with the following
additional methods.
AmazonSNS : Amazon Simple Notification Service (Amazon SNS) is a web
service that enables you to build distributed web-enabled applications.
Applications can use Amazon SNS to easily push
I see. Let's look into this a bit more and try to get the same added as
part of the "COPE" implementation. I'm sure it will be so catchy to have
this in the product.
Cheers,
Prabath
On Mon, Mar 7, 2016 at 10:35 AM, Inosh Perera wrote:
> Hi Prabath,
>
> This can be implemented
Noted.
On Mon, Mar 7, 2016 at 1:54 PM, Dimuthu Leelarathne
wrote:
> Hi,
>
> +1
>
> Small suggestion for the form - Indicate the location of target telephone
> number as {num} and the text message as {msg}. It could be URL, header or
> payload.
>
> thanks,
> Dimuthu
>
>
> On
Hi,
+1
Small suggestion for the form - Indicate the location of target telephone
number as {num} and the text message as {msg}. It could be URL, header or
payload.
thanks,
Dimuthu
On Mon, Mar 7, 2016 at 1:50 PM, Elilmatha Sivanesan
wrote:
> +1
>
> On Mon, Mar 7, 2016 at
Adding Elilmatha and Malaka.
On Mon, Mar 7, 2016 at 12:55 PM, Pulasthi Harasgama
wrote:
> Hi all,
> The current SMSOTP connector of the Identity Server can only be used with
> an API which uses the GET method and which uses only the parameters: API
> Key, API Secret,
13 matches
Mail list logo