What about using some other way of authentication. Mutual auth / JWT auth / etc. Earlier when we discuss this I think for a wrong reason I eliminated them. We can get the cert of the wso2 server (default carbon.jks) and store in app cloud and do calls using that. WDYT?
Thanks & Regards Danushka Fernando Senior Software Engineer WSO2 inc. http://wso2.com/ Mobile : +94716332729 On Fri, Aug 12, 2016 at 12:31 PM, Amalka Subasinghe <ama...@wso2.com> wrote: > Hi, > > In App Cloud we want to display all the wsdl endpoints which are deployed > in Data services. > So we need to know the admin password to invoke an admin service, which is > generate when the DSS starts. So we don't know the password. > > # Changing admin password > if [ -z ${ADMIN_PASSWORD+x} ]; then > echo "ADMIN_PASSWORD is not set."; > echo "Generating admin password."; > ADMIN_PASSWORD=${ADMIN_PASS:-$(pwgen -s 12 1)} > echo "=========================================================== > ==============" > echo "Credentials for the instance:" > echo > echo " user name: admin" > echo " password : $ADMIN_PASSWORD" > echo "=========================================================== > ==============" > sed -i > "s/.*<Password>admin<\/Password>.*/<Password>$ADMIN_PASSWORD<\/Password>/" > $CARBON_HOME_PATH/repository/conf/user-mgt.xml > else > echo "ADMIN_PASSWORD set by user."; > fi > > one approach we can take for this is, generate password in our side, save > it in our database and set it to the container as an environment variable. > is this a good approach? Any other ideas? > This will be required to ESB app type as well (ATM ESB invokes the admin > service using admin/admin). > > Thanks > Amalka > > >
_______________________________________________ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
