Hi, I believe we have a few policies in WSAS already with different key > sizes. This is because some people might not have unlimited strength > jurisdiction policy installed. What do you think about enforcing this > and sticking to only Basic256 algo suite? Then we can simply stick to > this set of policies and the WS-Trust policies we already have.
Yes, I also think that is the correct approach. Otherwise we will end up with large number of policies with minor variations. we can show in the documentation how to apply one of these policies and change the properties such as Algo suite, protection order , etc. Thanks, Nandana > > > Thanks, > Ruchith > > Nandana Mihindukulasooriya wrote: > > Hi Devs, > > > > As we don't have time to implement the proposed wizard, we can bring new > > some policies as mentioned in the JIRA [1]. > > > > - Authentication Only > > - Confidentiality Only > > - Confidentiality & Integrity > > - Confidentiality & Authentication > > - Confidentiality & Integrity & Authentication > > - Integrity only > > - Non-repudiation > > > > > > Following are the policies resulted in the discussion we had yesterday. > > Please > > point out if any of those policies doesn't provide the security > requirement > > mentioned. > > http://wiki.apache.org/general/NandanaMihindukulasooriya/WSAS/Policies > > > > What are the policies we bring in to WSAS ? > > > > Thoughts ? > > > > Thanks, > > Nandana > > > > https://wso2.org/jira/browse/WSAS-623 > > > > > > ------------------------------------------------------------------------ > > > > _______________________________________________ > > Wsas-java-dev mailing list > > [email protected] > > http://wso2.org/cgi-bin/mailman/listinfo/wsas-java-dev > > > > _______________________________________________ > Wsas-java-dev mailing list > [email protected] > http://wso2.org/cgi-bin/mailman/listinfo/wsas-java-dev > >
_______________________________________________ Wsas-java-dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/wsas-java-dev
