Keeping environment specific stuff at the synapse config level is a completely wrong.
thanks, Amila. On Thu, Jul 18, 2013 at 10:48 PM, Dushan Abeyruwan <dus...@wso2.com> wrote: > Hi > Regarding $subject, what would be the best way to accomplish ? > According to the EntitlementMediator implementation it seems > we are using a different approach as shown below [1], any reason which > prevent us moving to synapse secure vault and also seems there are zero > documentation related to Synapse secure vault configuration. > > > [1] > > https://svn.wso2.org/repos/wso2/carbon/platform/trunk/components/identity/org.wso2.carbon.identity.entitlement.mediator/src/main/java/org/wso2/carbon/identity/entitlement/mediator/EntitlementMediator.java > > > public void setRemoteServicePassword(String remoteServicePassword) { > if (remoteServicePassword.startsWith("enc:")) { > try { > * this.remoteServicePassword = new > String(CryptoUtil.getDefaultCryptoUtil()* > * > .base64DecodeAndDecrypt(remoteServicePassword.substring(4)));* > } catch (CryptoException e) { > log.error(e); > } > } else { > this.remoteServicePassword = remoteServicePassword; > } > } > > Cheers, > Dushan Abeyruwan > Associate Tech Lead > *Integration Technologies Team* > *WSO2 Inc. http://wso2.com/* > *Mobile:(+94)714408632* > > _______________________________________________ > Architecture mailing list > Architecture@wso2.org > https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture > > -- *Amila Suriarachchi* Software Architect WSO2 Inc. ; http://wso2.com lean . enterprise . middleware phone : +94 71 3082805
_______________________________________________ Architecture mailing list Architecture@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
