There's a security risk in exposing the token. So encoding won't work. Best is to has i presume.
Thanks, NuwanD. On Tue, May 6, 2014 at 9:43 PM, Sajith Ravindra <[email protected]> wrote: > Hi Lakmali, > > If this is not for a encryption purpose I think it's better to use Base64 > encoding. As per the description i feel that what you are trying to do is > encoding rather than encrypting. Also you can decode it back if you want if > you use Base64 encoding. > > Thanks > *, Sajith Ravindra* > Senior Software Engineer > WSO2 Inc.; http://wso2.com > lean.enterprise.middleware > > mobile: +94 77 2273550 > blog: http://sajithr.blogspot.com/ > <http://lk.linkedin.com/pub/shani-ranasinghe/34/111/ab> > > > On Tue, May 6, 2014 at 9:03 PM, Lakmali Baminiwatta <[email protected]>wrote: > >> Hi all, >> >> For tracking API invocations through Google Analytic, we need to send an >> unique ID based on the API token. As a solution,we can generate the MD5Sum >> value of the API token and send it as the unique ID. >> >> Is it fine to proceed with this approach or do we have a better way to >> achieve this? Appreciate any thoughts. >> >> Thanks, >> Lakmali >> >> >> >> >> -- >> Lakmali Baminiwatta >> Software Engineer >> WSO2, Inc.: http://wso2.com >> lean.enterprise.middleware >> mobile: +94 71 2335936 >> blog : lakmali.com >> >> >> _______________________________________________ >> Dev mailing list >> [email protected] >> http://wso2.org/cgi-bin/mailman/listinfo/dev >> >> > > _______________________________________________ > Dev mailing list > [email protected] > http://wso2.org/cgi-bin/mailman/listinfo/dev > > -- Nuwan Dias Associate Tech Lead - WSO2, Inc. http://wso2.com email : [email protected] Phone : +94 777 775 729
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
