Hi Pubudu, On Wed, Jul 20, 2016 at 11:38 AM, Pubudu Priyashan <[email protected]> wrote:
> Hi Rajith and Ayoma, > > *@Rajith:* I have checked this [1] with ESB Beta2 pack and it works with > both IBM 7 and 8 JDKs once you set the property as you have mentioned. I > have added this Doc JIRA [2] to include this information in official docs. > Is there a way that we can automatically pick the JDK whether it's IBM or > Oracle without setting this particular property? If so, one less step for > the user. So we may need to look into it if that's possible? > ASFAIK this file contains properties that used to enforce csrf guard. I think changing this to automatically pick the jdk is out of our control. We need to define it in the properties file. *@Ayoma* could you please clarify on this. > > *@Ayoma:* Just looped you in just in case those two issues might be > related. As it turns out these aren't. > > [1] https://wso2.org/jira/browse/ESBJAVA-4772 > [2] https://wso2.org/jira/browse/DOCUMENTATION-3648 > > Cheers, > Pubudu. > > Pubudu D.P > Senior Software Engineer - QA Team | WSO2 inc. > Mobile : +94775464547 > > Linkedin: https://uk.linkedin.com/in/pubududp > Medium: https://medium.com/@pubududp > > > On Tue, Jul 19, 2016 at 11:16 PM, Ayoma Wijethunga <[email protected]> wrote: > >> Hi Pubudu, >> >> I hope you were checking with me about "ESBJAVA-4740" [1]. Was >> "ESBJAVA-4772" mentioned by mistake? Rajith is correct about >> "ESBJAVA-4772", although "ESBJAVA-4740" has nothing to do with CSRFGuard. >> >> [1] https://wso2.org/jira/browse/ESBJAVA-4740 >> >> Regards, >> Ayoma >> >> On Tue, Jul 19, 2016 at 10:49 PM, Rajith Roshan <[email protected]> wrote: >> >>> Hi Pubudu, >>> >>> Can you try setting the following property[1] in >>> "Owasp.CsrfGuard.Carbon.properties" file >>> (SERVER_HOME/repository/conf/security) which is default set to [2]. We >>> found same issue with G-Reg and overcame it by setting this property. >>> >>> [1] - org.owasp.csrfguard.PRNG.Provider=IBMJCE >>> [2] - org.owasp.csrfguard.PRNG.Provider=SUN >>> >>> Thanks! >>> Rajith >>> >>> On Mon, Jul 18, 2016 at 12:51 PM, Pubudu Priyashan <[email protected]> >>> wrote: >>> >>>> Hi Senduran, >>>> >>>> We are currently facing the issue logged at [1] when starting the ESB >>>> pack with IBM JDK. Can we please take a look and get this fixed with the >>>> next release? This blocks us from testing the release on IBM JDK. Do let me >>>> know if you require any further information. Thanks! >>>> >>>> [1] https://wso2.org/jira/browse/ESBJAVA-4772 >>>> >>>> >>>> Cheers, >>>> Pubudu D.P >>>> Senior Software Engineer - QA Team | WSO2 inc. >>>> Mobile : +94775464547 >>>> >>>> Linkedin: https://uk.linkedin.com/in/pubududp >>>> Medium: https://medium.com/@pubududp >>>> >>>> >>>> _______________________________________________ >>>> Dev mailing list >>>> [email protected] >>>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>>> >>>> >>> >>> >>> -- >>> Rajith Roshan >>> Software Engineer, WSO2 Inc. >>> Mobile: +94-72-642-8350 <%2B94-71-554-8430> >>> >>> _______________________________________________ >>> Dev mailing list >>> [email protected] >>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>> >>> >> >> >> -- >> Ayoma Wijethunga >> Software Engineer >> Platform Security Team >> WSO2, Inc.; http://wso2.com >> lean.enterprise.middleware >> >> Mobile : +94 (0) 719428123 <+94+(0)+719428123> >> Blog : http://www.ayomaonline.com >> LinkedIn: https://www.linkedin.com/in/ayoma >> > > -- Rajith Roshan Software Engineer, WSO2 Inc. Mobile: +94-72-642-8350 <%2B94-71-554-8430>
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
