PRABATH'S TECH BLOG

When you run the pre-defined security scenarios in the WSO2 ESB most probably you already faced the Illegal key size or default parameters exception org.apache.axis2.AxisFault: Error in encryption     at org.apache.rampart.handler.RampartSender.invoke(RampartSender.java:76)     at org.apache.axis2.engine.Phase.invokeHandler(Phase.java:340)     at org.apache.axis2.engine.Phase.invoke(Phase.java:313)     at org.apache.axis2.engine.AxisEngine.invoke(AxisEngine.java:261)     at org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:426)     at org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:398)     at org.apache.axis2.description.OutInAxisOperationClient.executeImpl(OutInAxisOperation.java:224)     at org.apache.axis2.client.OperationClient.execute(OperationClient.java:149)     at org.apache.axis2.client.Ser...

Security is  one of the major concern when we developing API base integrations or application developments. WSO2 supports WS Security , WS-Policy and WS-Security Policy specifications. These specifications define a behavior model for web services. Proxy service security requirements are different from each others. WSO2 ESB providing pre-define commonly used twenty security scenarios to choose based on the security requirements. This functionality is provided by the security management feature which is bundled by default in service management feature in ESB. This configuration can be done via the web console until ESB 4.8.1 release, but this has been removed from the ESB 4.9.0. Even though this feature isn't provided by the ESB web console itself same functionality can be achieved by the new WSO2 Dev Studio . WSO2 always motivate to use dev studio to prepare required artifacts to the ESB rather than the web console. Better way to explain this scenario is by example. Following...