lease create the database
> using appropriate database scripts for the database.";
>
> throw new Exception(msg);
>
>
>
> It does not depend on the fact if database is created using scripts or
> not. Simply - the "MariaDB" is not in the list.
>
> Best regards
>
of other users ?
>
> --
> Gayan
> ___
> Iam-dev mailing list
> iam-...@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/iam-dev
>
--
Ruwan Abeykoon | Director/Architect | WSO2 Inc.
(
ub.com/v3/#rate-limiting
>
> Thanks,
> Sathya
> --
> Sathya Bandara
> Senior Software Engineer
> Blog: https://medium.com/@technospace
> WSO2 Inc. http://wso2.com
> Mobile: (+94) 715 360 421
>
>
--
Ruwan Abeykoon | Director/Architect | WSO2 Inc.
(w) +947435800 | Em
t 12:08 PM Thanuja Jayasinghe
wrote:
> Hi Ruwan,
>
>
> On Wed, Mar 18, 2020 at 9:36 AM Ruwan Abeykoon wrote:
>
>> Hi Sathya,
>> If this is only used for authenticating SOAP calls, then we need not
>> worry about managing it with REST.
>> SOAP services is going
luable suggestions on this.
>
> [1] https://app.swaggerhub.com/apis/emswbandara/IAM_CONFIGS/0.1.0
>
> Thanks,
> Sathya
> --
> Sathya Bandara
> Senior Software Engineer
> Blog: https://medium.com/@technospace
> WSO2 Inc. http://wso2.com
> Mobile: (+94) 715 360 421
>
>
an.
>>>>>
>>>>>
>>>> Thanks,
>>>> Malithi
>>>> --
>>>> *Malithi Edirisinghe* | Technical Lead | WSO2 Inc.
>>>> (m) +94 718176807 | (w) +94 11 214 5345 | (e) malit...@wso2.com
>>>> GET INTEGRATIO
notifications to the user.
>>>>>
>>>>> *Deliverables*
>>>>>
>>>>> We have planned to deliver the solution according to the following
>>>>> phases.
>>>>>
>>>>>
t;>> returned within *1 - 2 ms*, however the next line of the correlation
>>>>>> log prints after several *seconds*. Further investigating the same
>>>>>> could notice that some of them are caused by triggering ev
gt;> I have attached the high-level architecture as well.
>>
>>Wathsara Daluwatta | Intern - Engineering | WSO2 Inc.
>>
>> (m) +94717005121 | Email : waths...@wso2.com
>>
>> [image: https://wso2.com/signature] <https://wso2.com/signature>
>&g
model in near future release ?
>
> Thanks,
> Gayan
>
> ___
> Architecture mailing list
> Architecture@wso2.org
> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>
--
Ruwan Abeykoon | Director/Archite
gt; onSuccess: function (context){
>>>>>
>>>>> // Logic to execute if step 3 succeeded
>>>>>
>>>>> },
>>>>>
>>>>> onFail: function (context){
>>>>> forceRetry(
forceRetry(context);
> }
>
>});
> }
> });
>
> }
>
>
> Please share your thoughts on this.
>
>
> Thanks,
> Senthalan
> --
> Senthalan Kanagalingam | Software Engineer | WSO2 Inc.
> (m) +94 (0) 77 18 77 466 |
practical solution.
>>
>> Appreciate your feedback on the $subject.
>>
>> Best Regards
>> Isuranga Perera
>> --
>> *Isuranga Perera* | Software Engineer | WSO2 Inc.
>> +94 71 735 7034 | isura...@w
think Ruwan's reply contains the answer.
>
> Regards,
> Johann.
>
> On Thu, Jul 4, 2019 at 8:48 AM Johann Nallathamby wrote:
>
>> Hi Isura,
>>
>> On Fri, Jun 7, 2019 at 9:16 AM Isura Karunaratne wrote:
>>
>>>
>>>
>>> On Wed, Jun 5, 201
.
WDYT?
[1] https://github.com/wso2/carbon-identity-gateway
Cheers,
Ruwan A
--
Ruwan Abeykoon | Director/Architect | WSO2 Inc.
(w) +947435800 | Email: ruw...@wso2.com
___
Architecture mailing list
Architecture@wso2.org
https://mail.wso2.org/cgi-bin
in the database). So when using a clustered setup
>> those artifacts should be shared among all the nodes by using one of the
>> following file sharing mechanisms.
>>
>>- Dep Sync
>>- rSync
>>- Shared File System
>>
>>
>> *Solution *
>>
above solutions, I would like to go ahead with the claim based
>> solution (Solution2) since it’s more suitable with the current
>> capabilities we having in consent mgt.
>>
>> Appreciate your thoughts.
>>
>> Thanks
>>
>> Godwin
>> --
>> Godw
Hi All,
On Wed, May 29, 2019 at 9:51 AM Hasanthi Purnima Dissanayake <
hasan...@wso2.com> wrote:
> Hi Shammi,
>
> Are you planing to provide a check box to select the user stores at the
>> time it creates the SP?
>>
>
> At the moment a handler level implementation will do this and no any UI
>
, this was given as a workaround
AFAIK. Yes we need to add some function like
"clearAuthenticators({idp_list}, {authenticator_list})" or something along
to get the requirement done.
> Regards,
> Johann.
>
> On Thu, Apr 18, 2019 at 7:02 PM Ruwan Abeykoon wrote:
>
>> Hi
ssion on this.
>
> Thanks & Regards,
> Johann.
>
> --
> *Johann Dilantha Nallathamby* | Associate Director/Solutions Architect |
> WSO2 Inc.
> (m) +94 (77) 7776950 | (w) +94 (11) 2145345 | (e) joh...@wso2.com
> [image: Signature.jpg]
>
--
aptive
>> authentication to inject\modify a claim with transformation.
>>
> This is great.. Is there any sample or javascript api to manipulate cliams
> ?
>
>>
>> For the pure provisioning flows, +1 to come up with some mechanism.
>>
>> Thanks,
>
+1 for the technical solution.
Cheers,
Ruwan
On Wed, Feb 20, 2019 at 1:17 PM Johann Nallathamby wrote:
> IAM Team,
>
> I don't intend to talk about the importance of the claim transformations
> during provisioning use cases. Currently to support such cases, we propose
> to write custom
WSO2 IS requests to
> validate the binding code and requests an access token, Auth0 returns
> access token and ID token. By using the ID token WSO2 IS sends user info.
>
>
> Please find the Business use case ,
>
>
>
> --
> R.Nirubikaa
> Software Engineering Intern | W
;>>>>>>
>>>>>>> Description
>>>>>>>
>>>>>>> {key}
>>>>>>>
>>>>>>> Key of the configuration
>>>>>>>
>>>>>>>
1,2.
Will come to this bit later.
Cheers,
Ruwan
On Mon, Oct 15, 2018 at 11:20 PM gayan gunawardana
wrote:
>
> Hi Ruwan,
>
> This is a very good initiative and I have few things to clarify.
> On Sun, Oct 14, 2018 at 8:38 AM Ruwan Abeykoon wrote:
>
>> Hi Devs,
>>
&
he "circuit-breaker" is not something hard to do. We
need to wrap all the calls to existing USM with "CircuitBreaker" (new
class) which keeps track of calls and throw necessary IOException.
Cheers,
Ruwan
--
*Ruwan Abeykoon*
*Associate Director/Architect**,*
*WSO2, Inc. http
[+] Stable - go ahead and release
>>>>>
>>>>>[-] Broken - do not release (explain why)
>>>>>
>>>>>
>>>>>
>>>>> Thanks,
>>>>>
>>>>> - WSO2 Identity and Access Management Team -
- In *Session* table, details of *Browser, OS* and *Location* will not
>be used in query. So we can store this information as JSON object.
>
>
> Regards
>
> --
> Chuhaashanan
> Intern - Software Engineering
>
>
>
--
*Ruwan Abeykoon*
*Associate Director/Arch
s://wso2.com/signature] <https://wso2.com/signature>
>>>
>>>
>>
>> --
>> *Hasitha Abeykoon*
>> Associate Technical Lead; WSO2, Inc.; http://wso2.com
>> *cell:* *+94 719363063*
>> *blog: **abeykoon.blogspot.com* <http://abeykoon.blog
ve this we can use a different logger for these new logs and the
> logs should be in debug level. So the new logs won't be visible in an
> existing deployment. If a customer needs to see these logs, they just need
> to configure log4j to enable DEBUG for the new logger and direct the logs
&
ttp://wso2.com/> - Lean . Enterprise . Middleware
>
> mobile : +94775615183
>
>
>
--
*Ruwan Abeykoon*
*Associate Director/Architect**,*
*WSO2, Inc. http://wso2.com <https://wso2.com/signature> *
*lean.enterprise.middleware.*
___
A
hat it's not enough and used 5120 for now. Is there a maximum size
>>> that we can decide on?
>>>
>>>>
>>>>
>>>>
>>>
>>
>> --
>> Maduranga Siriwardena
>> Senior Software Engineer
>> WSO2 Inc; htt
p authentication to associate those two accounts automatically.
>
>
> Any suggestions would be appreciated.
>
> Thanks,
> Nila.
>
>
> --
> Nilasini Thirunavukkarasu
> Software Engineer - WSO2
>
> Email : nilas...@wso2.com
> Mobile : +94775241823
> We
: 1,
> "comment" : "some comments"
> });
> if anyone didn't want the propeties, they can use {} or null.
>
> Your comments and feedback related to these identified functions and
> signature are highly appreciated.
>
> thanks,
> Senthalan.
> --
>
> *Senthalan
or the current session. Or else he can
> call the admin and ask him to kill a session.
>
> thanks,
> Dimuthu
>
>
> On Mon, Apr 2, 2018 at 2:14 PM, Ruwan Abeykoon <ruw...@wso2.com> wrote:
>
>> Hi Dimuthu,
>> The problem would be that the user will not be
gt;>>> Software Engineer | WS*O₂* Inc.
>>>>>>
>>>>>> M : +*94710124103 <071%20012%204103>* | http://wso2.com
>>>>>>
>>>>>> [image: http://wso2.com/signature] <http://wso2.com/signature>
>>>>>>
>>>
Hi Dimuth/Vihanga,
I think we need to get the minimal solution implemented and demonstrated
first. The minimal product would,
1. Close the oldest session, when the session count exceeds maximum allowed
count. No need to provide a UI to the user.
2. Log the above case in separate identifiable log
gt; Appreciate your suggestions and comments on the above approach.
> Thanks and Regards
> --
> Indunil Upeksha Rathnayake
> Software Engineer | WSO2 Inc
> Emailindu...@wso2.com
> Mobile 0772182255
>
--
*Ruwan Abeykoon*
*Associate Director/Architect**,*
*WSO2, Inc. http
Hi Indunil,
Please make sure this behavior is properly explained in the documentation,
with references to the spec.
Cheers,
Ruwan
On Mon, Mar 12, 2018 at 10:30 AM, Indunil Upeksha Rathnayake <
indu...@wso2.com> wrote:
>
>
> On Wed, Feb 28, 2018 at 5:15 PM, Dulanja Liyanage
>
21, 2018 at 3:46 PM, Isura Karunaratne <is...@wso2.com>
>> wrote:
>>
>>> Hi Ruwan,
>>>
>>> On Wed, Feb 21, 2018 at 3:28 PM, Ruwan Abeykoon <ruw...@wso2.com> wrote:
>>>
>>>> Hi All,
>>>>
>>>> In order to
Hi All,
In order to comply with GDPR regulations, we are planning to incorporate
privacy and cookie policy URL configuration into carbon 4 "carbon.xml" .
The following element will be added to "carbon.xml", as this needs to be
available fr any product based on c4.
This configuration will be
Hi Harsha,
This is for C4.
For IS perspective, 5.5.0 and few releases to come will be on C4. But we
want to make them more container native.
So we need to move these system properties to a file, outside of
"wso2server.sh", so that they can be scripted easily.
And even these are the last one to be
asons, we are planing to use base 64 encoded
>>>>>>> fully qualified username as the userId in the above request.
>>>>>>>
>>>>>>
>>>>>> Would like to know the rationale behind base64 encoding the username.
>>>>>>
Hi All,
-1 on adding anything to SP Configuration. This needs to be separated from
SP object, or table itself.
Reason:
1. We need to minimize DB changes adding features.
2. Adding a column per validator (XACML here) is not scalable. (What if
another validator is added in future, do we add another
Hi Dushan,
Thanks for sharing the "Componentspace". It seems a complete and
comprehensive solution.
This purpose of this "agent" ( we need to rename this, as it is not an
agent, but a library), is to be included in VS solution. We have no plan to
install this library in IIS.
+1 on comprehensive
risk score?
>
> On Tue, Jan 23, 2018 at 10:43 PM, Ruwan Abeykoon <ruw...@wso2.com> wrote:
>
>> Hi Dimuthu,
>> +1 on using existing infrastructure with IS.
>>
>> We need to implement "Risk Calculator" logic in DAS, with Spark and
>> Siddhi queries.
.
>>
>>
>>
>>
>> Whatever the risk calculator does is to reuse the existing data-stores as
>> the above diagram.
>>
>> thanks,
>> Dimuthu
>>
>>
>>
>> On Fri, Jan 19, 2018 at 9:04 AM, Ruwan Abeykoon <ruw...@wso2.com> wrote
3. User Credentials Update By Admin [4]
>>>>>
>>>>> <https://github.com/wso2/carbon-kernel/blob/release-4.4.20/core/org.wso2.carbon.user.core/src/main/java/org/wso2/carbon/user/core/listener/UserOperationEventListener.java#L144>
>>>>>
>>>
Hi Hasintha,
We do not need to export anything we do not keep in our databases.
Could you please explain further if we need to do anything extra for
Federated case.
Cheers,
Ruwan
On Mon, Jan 22, 2018 at 5:33 PM, Hasintha Indrajee
wrote:
> Just a quick question. How are we
}
> }
> });
> }
> }
> }
> });
> }
>
>
> In the above script, we define a cookie called *testcookie*. At the
> initial authentication stage, the user has to go through both s
nd calculates the risk score.
>
> We will be considering
>
> IP address
> Geolocation
> Number of failed attempts between two successful logins
>
> when generating the rules to calculate the risk score.
>
> Regards,
> Pamoda
>
>
> On Tue, Jan 16, 2018 at 9:4
Hi Sathya,
We can enhance the DefaultRequestCoordinator itself, rather than extending
and creating new coordinator, as there is no functional change done by
adding the "request" and "response" to authentication context.
Cheers,
Ruwan
On Wed, Jan 17, 2018 at 10:40 AM, Sathya Bandara
t;
> I have seen some users have already implemented a small script which calls
> the LDAP user store & verifies the password updated date & sends mails.
>
> Thanks,
> Asela.
>
>
>>> Thanks,
>>> Asela.
>>>
>>>
>>>>- The passw
i Lanka and after one day of travelling
> if I log from United States, Facebook is suspicious and throw me some
> security questions.*
>
> Thanks
>
> On Tue, Jan 16, 2018 at 9:09 AM, Ruwan Abeykoon <ruw...@wso2.com> wrote:
>
>> Hi Pamoda,
>> He
>>>> WSO2, Inc.
>>>> lean.enterprise.middleware
>>>>
>>>> Mobile: *+94 77 7776950*
>>>> LinkedIn: *http://www.linkedin.com/in/johann-nallathamby
>>>> <http://www.linkedin.com/in/johann-nallathamby>*
>>>> Medium: *https://
oftware Engineer | WSO2
>>
>> Email: nad...@wso2.com
>> Mobile: +94778222607 <077%20822%202607>
>> Web: http://wso2.com
>>
>> <http://wso2.com/signature>
>>
>
>
>
> --
> Dimuthu Leelarathne
> Director, Solutions Architecture
>
> WSO2
uld not worry about it.
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> Please share your thoughts.
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
HI All,
We should not remove extensibility.
We need to look for an alternative way on this do any improvement while
keeping extensibility.
Cheers,
Ruwan
On Thu, Nov 9, 2017 at 3:28 PM, Danushka Fernando
wrote:
> Hi All
> In released IS 5.3.0 we have capability of extending
t;>>> *and *log4j2.properties,* in carbon-logging the issue was fixed.
>>>>
>>>>
>>>>- Pax-logging overcomes the above issues and therefore, the default
>>>>pax-logging api can be used
>>>> - This provides log4j2 bridge inte
Hi all,
For billing, we could borrow Telocom CDR [1] concept.
Simply this is set of event logs conforming to predefined tabular format.
Usually billing is done examining the CDR and apply various financial
rules, and is out of the scope of the system which produces CDR.
[1]
Hi Irunika,
In C4, applications use commons logging. We never wanted to use Log4J
directly. Hence the architecture you proposed is already there in C4.
In C5 we use slf4j, in place of commons logging, which architecturally the
same.
Hence I do not see any value in introducing another WSO2
ases.
>
> Thanks & Regards,
> Johann.
>
> --
>
> *Johann Dilantha Nallathamby*
> Senior Technical Lead - WSO2 Identity Server
> Governance Technologies Team
> WSO2, Inc.
> lean.enterprise.middleware
>
> Mobile - *+9476950*
> Blog - *http://nallaa.wordpre
w the authentication chain corresponding to a service provider
> is loaded by its name. But with this design it will be by the name and the
> ACR value.
>
> This will require minimal changes at the framework level.
>
> Also - let's keep adaptive authentication out of this. We can add
oolean isApplicable(StepConfig stepConfig, AuthenticationContext
context);
}
The other aspects of framework remains architecturally unchanged as the
framework relies on the bre-bult Sequence to perform authentication
completion.
Cheers,
Ruwan
--
*Ruwan Abeykoon*
*Associate Director/Arc
va/org/wso2/carbon/launcher/extensions/OSG
> iLibBundleDeployerUtils.java
>
> Thanks,
> *Jayanga Dissanayake*
> Associate Technical Lead
> WSO2 Inc. - http://wso2.com/
> lean . enterprise . middleware
> email: jaya...@wso2.com
> mobile: +94772207259 <+94%2077%20220%20725
ponent(name = "some.component.exposing.Authorizer",
>
> *service = Authorizer.**class**,*
> immediate = true
> )
>
>
> [1] https://github.com/wso2/carbon-uuf/blob/master/
> components/uuf-core/src/main/java/org/wso2/carbon/uuf/internal/deployment/
> Os
here.*
> }
> }
>
>
> Best Regards,
> Vidura Nanayakkara
>
> On Fri, May 12, 2017 at 5:24 PM, Ruwan Abeykoon <ruw...@wso2.com> wrote:
>
>> Hi All,
>> >>
>> # Authorizer for this app
>> authorizer: "org.wso2.carbon.uuf.sample.s
a90
>>
>> <http://wso2.com/signature>
>>
>> WSO2 Inc. www.wso2.com
>> lean.enterprise.middleware
>>
>> ___
>> Architecture mailing list
>> Architecture@wso2.org
>> https://mail.wso2.org/cgi-bin/ma
e>
>>
>> ___
>> Architecture mailing list
>> Architecture@wso2.org
>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>>
>>
>
>
>
http://www.google.com/url?q=http%3A%2F%2Fwso2.com=D=1=AFQjCNEZvyc0uMD1HhBaEGCBxs6e9fBObg>
> 20, Palm grove Avenue, Colombo 3
> E-Mail: aye...@wso2.com <ayshsa...@gmail.com>
>
> ___
> Architecture mailing list
> Arc
t;
> *Danesh Kuruppu*
> Senior Software Engineer | WSO2
>
> Email: dan...@wso2.com
> Mobile: +94 (77) 1690552 <+94%2077%20169%200552>
> Web: WSO2 Inc <https://wso2.com/signature>
>
>
> _______
> Architecture mailing li
>>>>>>>>>> Architecture mailing list
>>>>>>>>>> Architecture@wso2.org
>>>>>>>>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>>>>>>>>>>
>
t and Password History validation
>
> Thanks,
> Gayan
>
> --
> Gayan Gunawardana
> Software Engineer; WSO2 Inc.; http://wso2.com/
> Email: ga...@wso2.com
> Mobile: +94 (71) 8020933
>
> ___
> Architecture mailing list
>
tyStoreImpl.java#L985
>
> Thanks,
> Gayan
> --
> Gayan Gunawardana
> Software Engineer; WSO2 Inc.; http://wso2.com/
> Email: ga...@wso2.com
> Mobile: +94 (71) 8020933
>
--
*Ruwan Abeykoon*
*Associate Director/Architect**,*
*WSO2
>>
>>>>
>>>>
>>>
>>>
>>> --
>>> Thanks & Regards,
>>>
>>> *Johann Dilantha Nallathamby*
>>> Technical Lead & Product Lead of WSO2 Identity Server
>>> Governance Technologies Team
>>> WSO2, Inc.
>
duct Lead of WSO2 Identity Server
>>> Governance Technologies Team
>>> WSO2, Inc.
>>> lean.enterprise.middleware
>>>
>>> Mobile - *+9476950*
>>> Blog - *http://nallaa.wordpress.com <http://nallaa.wordpress.com>*
>>>
>>> _
Mobile: +94 (77) 1690552 <+94%2077%20169%200552>
>>>> Web: WSO2 Inc <https://wso2.com/signature>
>>>>
>>>>
>>>> ___
>>>> Architecture mailing list
>>>> Architecture@wso2.org
>>>>
Hi All,
@Johann
I think security questions/account recovery options should not be treated
as server-configurations. I would rather consider them as the runtime data
much like the SP/IdP data. Hence single server config does not apply for
this case IMO.
>>Each component must pass its own
ote:
>
>> Noted Ruwan.
>>
>> Biruntha
>>
>> Associate Software Engineer
>> WSO2
>> Email : birun...@wso2.com
>> Linkedin : https://lk.linkedin.com/in/biruntha
>> Mobile : +94773718986 <+94%2077%20371%208986>
>>
>> On Fri, Nov 25, 2016
>>> private Set senderConfigurations;
>>>>
>>>> }
>>>>
>>>>
>>>>> Have we thought about secure vault too?
>>>>>
>>>>
>>>> Yes, we resolve all secure valut values and system property valu
>
>>
>> --
>>
>> Best Regards,
>>
>> Malaka Silva
>> Senior Technical Lead
>> M: +94 777 219 791
>> Tel : 94 11 214 5345
>> Fax :94 11 2145300
>> Skype : malaka.sampath.silva
>> LinkedIn : http://www.linkedin.com/pub/malaka-
lcome.
>
>
> --
> Best Regards,
> Danoja Dias
> Intern Software Engineering - WSO2
>
> Email : dan...@wso2.com
> Mobile : +94771160393
>
> [image: http://wso2.com/signature] <http://wso2.com/signature>
>
--
*Ruwan Abeykoon*
*As
common problem for all the artifact deployment among the
> cluster not only IS.
>
> Thanks
>
--
*Ruwan Abeykoon*
*Associate Director/Architect**,*
*WSO2, Inc. http://wso2.com <https://wso2.com/signature> *
*lean.enterprise.middleware.*
_
Hi All,
If this is about unit testing on DAO, we are also experimenting with simple
JDBC approach[1]. No Dependency Injection.
We could test the DAO, the SQL correctness etc. because there is no Mock
objects.
I am not in favor of DI on developing a platform as we have no control over
which get
t;>>>>>>>> the config
>>>>>>>>>>>>>> change.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> 2. Since the config DB table has a known structure a UI can
>>>>
r otherwise use the information
> contained in this communication. Internet communications cannot be
> guaranteed to be timely, secure, error or virus-free. The sender does not
> accept liability for any errors or omissions.
>
--
*Ruwan Abeykoon*
*Associate Director/Architect**,*
gt;>> Ramith Jayasinghe
>>>> Technical Lead
>>>> WSO2 Inc., http://wso2.com
>>>> lean.enterprise.middleware
>>>>
>>>> E: ram...@wso2.com
>>>> P: +94 772534930
>>>>
>>>> ___
PassThrough+Transport
>>>>
>>>> Thanks.
>>>>
>>>> --
>>>> *Isuru Udana*
>>>> Technical Lead
>>>> WSO2 Inc.; http://wso2.com
>>>> email: isu...@wso2.com cell: +94 77 3791887
>>>> blog: http:/
ftware Architect - WSO2, Inc. http://wso2.com
> email : nuw...@wso2.com
> Phone : +94 777 775 729
>
> ___
> Architecture mailing list
> Architecture@wso2.org
> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>
>
--
gt;>>>>>>
>>>>>>>
>>>>>>> [1] -
>>>>>>> https://github.com/wso2/carbon-governance/tree/master/components/governance/org.wso2.carbon.governance.rest.api
>>>>>>>
>>>>>>>
>>
d.spark.common.udf/src/main/java/org/wso2/carbon/analytics/shared/common/udf/DateTimeUDF.java
>
> --
> Thanks & Regards,
>
> Inosh Goonewardena
> Associate Technical Lead- WSO2 Inc.
> Mobile: +94779966317
>
> _______
> Archite
+Miyuru, Dunith
On Mon, Jun 13, 2016 at 11:43 AM, Ruwan Abeykoon <ruw...@wso2.com> wrote:
> Hi Sameera,
> Yes, storing the time in "epoch time" is correct.
>
> Its the presentation which should depend on "Locale"
>
> The disagreement here is which is
time. So we need to convert this
> epoch time in JS level. I will work on a fix and let you know. If we can
> get the server time zone, we can do as Ruwan said.
>
> On Mon, Jun 13, 2016 at 11:27 AM, Ruwan Abeykoon <ruw...@wso2.com> wrote:
>
>> Hi All,
>> The
t; decision on whether to share/not to share the dashboard. WDYT ?
>>>>>>
>>>>>> Any comments on this is highly appreciated.
>>>>>>
>>>>>> [1]
>>>>>> https://docs.google.com/a/wso2.com/document/d/1JjB0Ehf6L
enior Software Engineer
>>> WSO2, Inc.; http://wso2.com
>>> 20, Palmgrove Avenue, Colombo 3
>>>
>>> E-mail: tgtshan...@gmail.com
>>>
>>>
>>> _______
>>> Architecture mailing list
>&g
ed approach. We ended up writing OAuth2 token
>> provisioning on top of DAS.
>>
>> 3. Tomcat uses Java logging now (
>> https://tomcat.apache.org/tomcat-9.0-doc/logging.html). They support
>> other logging systems through 'juli'. May be we should switch to Java
>&g
aworld.com/article/2076333/java-web-development/use-a-randomaccessfile-to-build-a-low-level-database.html
Cheers,
Ruwan
--
*Ruwan Abeykoon*
*Architect,*
*WSO2, Inc. http://wso2.com <http://wso2.com/> *
*lean.enterprise.middleware.*
email:
gt;>>>>> system bundle to solve this. Please contact Rasika if that's the case.
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> With Regards,
>>>>>
>>>>> *Rasika Perer
t;> M: +94 71 680 9060 E: rasi...@wso2.com
>>>> LinkedIn: http://lk.linkedin.com/in/rasika90
>>>>
>>>> WSO2 Inc. www.wso2.com
>>>> lean.enterprise.middleware
>>>>
>>>
>>>
>>>
>>> --
>>> Nuwan Wi
___
>>>> Architecture mailing list
>>>> Architecture@wso2.org
>>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>>>>
>>>>
>>>
>>>
>>> --
>>> With regards,
>>> *Manu*r
1 - 100 of 129 matches
Mail list logo