Hi Maduranga,
In the wso2as-5.3.0\repository\conf\datasources\master-datasources.xml, I
do find a jndiConfig item:
[image: Inline image 1]
Is the problem related with the post [1].
[1]: http://wso2.markmail.org/search/?q=list%3Aorg.wso2.dev+
failed+to+get+WSO2+data+source%3A+Name+%5Bjdbc%2FWSO2C
Hi,
I'm trying to configure SSO in wso2es 2.1.0 in our staging environment. I
configured the SAML2SSOAuthenticator in
/repository/conf/security/authenticators.xml as shown in [1]. I
get the exception [2] when I try to login the mgt console. The issuer
carbonServerSP is configured with the Assertio
Hi Isuru,
Yes, the existing unit test[1] is using HikariCP implementation and I'm
currently working on minor improvements.
[1].
https://github.com/wso2/carbon-datasources/tree/master/components/org.wso2.carbon.datasource.core/src/test
Thanks.
On Wed, Nov 30, 2016 at 11:38 AM, Isuru Perera wrot
+1 to keep only the HikariCP based implementation.
Do we have unit tests for HikariCP based implementation?
On Wed, Nov 30, 2016 at 11:30 AM, Thanuja Uruththirakodeeswaran <
thanu...@wso2.com> wrote:
> Thanks a lot all !!! Will remove tomcat implementation.
>
> Thanks.
>
> On Wed, Nov 30, 2016 a
Thanks a lot all !!! Will remove tomcat implementation.
Thanks.
On Wed, Nov 30, 2016 at 11:13 AM, Kishanthan Thangarajah <
kishant...@wso2.com> wrote:
> We first started off with tomcat jdbc pool based impl, but later decided
> to move on Hikari due it's performance reliability over tomcat. We c
We first started off with tomcat jdbc pool based impl, but later decided to
move on Hikari due it's performance reliability over tomcat. We can safely
remove the tomcat impl.
On Tue, Nov 29, 2016 at 2:07 PM, Anjana Fernando wrote:
> Hi,
>
> We ourselves are specifically not. Kicha or Sameera may
Hi wenxing,
Have you defined a datasource in any of the xml files in
/repository/conf/datasources folder with jndi name as
jdbc/WSO2CarbonDB like below?
jdbc/WSO2CarbonDB
Thanks,
Maduranga.
On Wed, Nov 30, 2016 at 9:56 AM, Rajith Roshan wrote:
> Hi,
>
> Once the server is started (Co
Since these are patch versions will there be a problem in simply upgrading
from 4.4.1 to 4.4.10 ?
On Tue, Nov 29, 2016 at 8:46 PM Rajith Roshan wrote:
> Hi,
>
> You can not simply update the kernel version from 4.4.1 to 4.4.10. You
> have to update all the dependent components as well in order t
Hi,
Once the server is started (ConfigurationContextService is active) you
should be able to get the datasources as below. All the jndi configs should
be bound to context by then.
Context ctx = new InitialContext();
dataSource = (DataSource) ctx.lookup(dataSourceName);
Thanks!
Rajith
On Wed,
Hi Shenavi,
As a practice, we announce security fixes to customer via a support ticket
and then provide it publicly for each product [1].
[1] - http://wso2.com/security-patch-releases/
Regards,
Nira
On Wed, Nov 30, 2016 at 7:42 AM, Prakhash Sivakumar
wrote:
> Hi Shenavi,
>
> We have issued a
Hi Shenavi,
We have issued a patch to prevent CSRF attacks in all the products based on
carbon 4.2.0. Please apply the patch [1] .
[1] WSO2-CARBON-PATCH-4.2.0-1464 -
http://product-dist.wso2.com/downloads/carbon/4.2.0/WSO2-CARBON-PATCH-4.2.0-1464.zip?utm_source=pagedirect&utm_medium=product&utm_c
Thanks to Rajith.
The problem is how to tell the versions of all the dependent components?
Need to check all the release notes of the dependent components and choose
the one with the same Core version?
-- Original --
*From: * "Rajith Roshan";;
*Send time:* Tuesday,
Dear all,
I met with an issue in getting the JNDI datasource with the callstack
below. Appreciated for any hint on this problem:
AS: 5.3.0
javax.naming.NameNotFoundException: Name [jdbc/WSO2CarbonDB] is not bound
in this Context. Unable to find [jdbc].
at org.apache.naming.NamingContext.l
Hi All,
I observe the "AuthenticationHandler not found exception"[1] when the
dashboard jaggery app calls[2] the backend REST services over the HTTPS. By
debugging, we found that this issue occurs only when the carbon server is
started with the hostname verification enable mode. If the hostname
ve
WSO2 API Manager team is pleased to announce WSO2 API Manager 2.1.0-BETA
release.
Distribution : https://github.com/wso2/product-apim/releases/tag/v2.1.0-beta
Analytics : https://github.com/wso2/analytics-apim/releases/tag/v2.1.0-beta
Tooling : https://github.com/wso2/devstudio-tooling-apim/releas
Hi All
In an attempt to mitigate the CSRF attacks from jaggery apps using
application server 5.2.1 it was reccomended to use the CSRF attacks
following the guide to Implement CSRF prevention based on OWASP CSRFGuard
[1]. But it was mentioned that this is supported for products with kernal
version
Hi Devs,
This is the release candidate of WSO2 Enterprise Mobility Manager 2.2.0.
Please download EMM 2.2.0 RC2 and test the functionality and vote. Vote
will be open for 72 hours or as needed.
Know issues: https://wso2.org/jira/issues/?filter=13384
Fixes provided : https://wso2.org/jira/issu
Hi,
You can not simply update the kernel version from 4.4.1 to 4.4.10. You have
to update all the dependent components as well in order to build the
application server.
Thanks!
Rajith
On Fri, Nov 25, 2016 at 11:45 AM, wenxzhen wrote:
> Dear all,
>
> Is there any potential risk to upgrade the C
Hi Amit,
Basically you can store the actual value in registry [1] or as a local
entry [2]. These features comes out of the box with WSO2 ESB. When you save
you will get a key for each entry. So you need to maintain different value
set for different environments but key(s) should be same.
After do
Hi
Related to interacting with gadgets in dashboard app, I have evaluated the
operation level permissions required for logged in users in order to work
with gadgets properly. I have summarized services used, operations and
permissions required in [1]
Some of the service operations required advan
Hi,
We ourselves are specifically not. Kicha or Sameera may know, I guess they
just implemented both ways initially. I also think we shouldn't have two
separate implementations of the same thing, and just get one implementation
tested and used properly.
Cheers,
Anjana.
On Tue, Nov 29, 2016 at 1:
Hi Anjana and Team,
Are we using the tomcat JDBC connection pool implementation[1] in
carbon-datasources repo anywhere? If not, shall we remove it from the repo.
Please give your suggestions.
[1].
https://github.com/wso2/carbon-datasources/tree/master/components/org.wso2.carbon.datasource.core/sr
Hi Dilan,
The answers are in-line.
*Maninda Edirisooriya*
Senior Software Engineer
*WSO2, Inc.*lean.enterprise.middleware.
*Blog* : http://maninda.blogspot.com/
*E-mail* : mani...@wso2.com
*Skype* : @manindae
*Twitter* : @maninda
On Tue, Nov 29, 2016 at 6:40 AM, Dilan Udara Ariyaratne
wrote:
23 matches
Mail list logo