Hi Nilmini, I had a chat with Sanjeewa (copied) and did the following changes to the content that you produced:
- Instructed the user to create the scripts on their own but gave the ones that are in Sanjeewa's blog as examples. Users can write their own scripts too. - According to Sanjeewa, we can use a single script to sign all JAR files. - Note that I added steps 2 and 3 to generate the key and then import it to the keystore. - In the last step, the user is instructed to change the sec.policy file and start the server. Changing the file is optional IMO, and the example is for the APIM only. Other writers might have to change it according to their products. I have copied this to the shared space and logged an <All> JIRA: https://wso2.org/jira/browse/DOCUMENTATION-1399. Please let me know if there are any discrepancies. Thanks, -Nirdesha On Wed, Dec 10, 2014 at 10:36 AM, Nilmini Perera <nilm...@wso2.com> wrote: > Hi, > > Thanks for this information Sanjeewa. Looping Aruna, Sameera and Sanjaya. > > We previously documented the process of enabling Java Security Manager for > Carbon products [1], which was based on Aruna's blog [2]. This is still > under review because the scripts need to be reviewed. [Please refer mail: > "Official > document for enabling security manager"] > > However, based on the information given in both blogs, could we clarify > the following: > > - Can we instruct the users to create the scripts on their own as > mentioned by Sanjeewa?, or do we provide the necessary scripts as an > attachment in the documentation? Which would be the recommended approach? > - Also, is it necessary to sign the product pack and the patches > separately (using two different scripts) as explained in [1]? > > [1] https://docs.wso2.com/display/Carbon430/Enable+Java+Security+Manager > [2] http://java.dzone.com/articles/enable-java-security-manager > > Thanks and Best Regards, > Nilmini > > On Tue, Dec 9, 2014 at 10:07 PM, Nirdesha Munasinghe <nirde...@wso2.com> > wrote: > >> +1. Thanks for the blog posts, Sanjeewa. I added a JIRA to track this >> task: >> https://wso2.org/jira/browse/DOCUMENTATION-1365. >> >> On Tue, Dec 9, 2014 at 8:26 PM, Sanjeewa Malalgoda <sanje...@wso2.com> >> wrote: >> >>> We might need to add this[1] to product documentation. WDYT? >>> >>> [1] >>> http://sanjeewamalalgoda.blogspot.com/2014/12/how-to-run-wso2-api-manager-180-with.html >>> >>> Thanks, >>> sanjeewa. >>> -- >>> >>> *Sanjeewa Malalgoda* >>> WSO2 Inc. >>> Mobile : +94713068779 >>> >>> <http://sanjeewamalalgoda.blogspot.com/>blog >>> :http://sanjeewamalalgoda.blogspot.com/ >>> <http://sanjeewamalalgoda.blogspot.com/> >>> >>> >>> >> >> >> -- >> >> Thanks, >> >> Nirdesha Munasinghe, >> WSO2 Inc. >> Web:http://wso2.com >> >> Mobile: +94 776321920 >> >> -- >> You received this message because you are subscribed to the Google Groups >> "WSO2 Documentation" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to documentation+unsubscr...@wso2.com. >> For more options, visit https://groups.google.com/a/wso2.com/d/optout. >> > > > > -- > Nilmini Perera > > Senior Technical Writer > WSO2 Inc. > > Mobile: 0094776722152 > > -- Thanks, Nirdesha Munasinghe, WSO2 Inc. Web:http://wso2.com Mobile: +94 776321920
_______________________________________________ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
