Currently the only version of the SDK for Duo works with the deprecated v2 of Duo's web SDK. I'm looking for a way to simply get started with bringing Duo's 2FA into my ColdFusion application. I've looked at Duo's guide for upgrading from v2 to v4 and it isn't terribly specific. They seem to no longer be developing the ColdFusion SDK, but I've got a very large legacy ColdFusion application that can't be easily migrated to node or something else at the moment. This is the SDK I've seen so far: https://github.com/duosecurity/duo_coldfusion
Related
Facebook sdk v3 is depreciated so i am getting issue on my live site. I cant upgrade my php version because my application does not support higher versions of php. So i need solution on current situation.
Thank you in advance.
I currently have the task of updating a Sitecore Instance 6.6 with SIP 3.2. The target is reaching Sitecore 7.0, so we can use Item Buckets.
The problem is when I update Sitecore to 7.0, it doesn't work with SIP 3.2, because assembly references doesn't match anymore and Sitecore 7.0 runs on .NET 4.5, where SIP 3.2 runs on .NET 3.5. So the Sitecore Backend does not work anymore and I cannot update the SIP.
If I update the SIP to 4.0 (which works with Sitecore 7.0) before updating the Sitecore Instance to 7.0, I get a similar problem.
Any idea what I can do to update both together? Or is there another way of achiving Sitecore 7.0 with SIP 4.0?
I would recommend uninstalling SIP first. You can achieve this is via removing the code files and configs from the solution manually - you can try leaving the Sitecore Items there as they shouldn't cause issues.
It will be helpful to redownloading the SIP package, unzip to see the files and view which files and configs it contains, then remove those from your solution.
A simpler way if you have Sitecore Rocks is to create an Anti-package - https://www.sitecore.net/nl-be/learn/blogs/technical-blogs/trevor-campbell/posts/2013/02/28-days-of-sitecore-rocks-package-management-part-1.aspx
Once you have removed SIP, complete your upgrade of Sitecore and confirm your site serves correctly afterwards.
Then its a matter of installing the correct version of SIP for the version of Sitecore 7 you have upgraded to. This will mitigate the issue of assemblies being different versions.
I would recommend backing up your databases before the upgrade as best practice but to also retrieve any SIP Item you may later need.
My question is concerning the Rally javascript SDK 1.32.
My line of thinking is this: SDK 1.32 seems to only return objects with APIMajorVersion 1 and MinorVersion 32, yet there exist versions from 1.33 to 1.43 as well (though they are all now deprecated as well). It makes sense to me that since SDK 2.0 must return objects from version 2.0, that there should be a way to specify what webservice version to return objects from.
My question is this: am I right that there is a way to obtain Rally objects from webservice v2.0 from SDK 1.32? If so, how would I do that?
I'm not just asking this out of laziness-- I am on the tail-end of an internship and would not necessarily have time to learn the new SDK and reimplement all that I have done on SDK 1.32.
Thanks for any responses!
This answer:
1.39 Rally API Version source for Java Script
shows how to utilize AppSDK 1.x using different versions of WSAPI.
However, AppSDK 1.x utilizes the adhoc.js Webservices endpoint for querying. This endpoint has been deprecated in Webservices 2.0. As a result, AppSDK 1.x will not work against Rally Webservices 2.0.
I'd recommend using AppSDK 2rc1, which is built on Webservices 2.0.
I want to create web service in liferay 6.1. But if i do such things, like in liferay 6.0 i have errors like java.io.IOException: Type {http://model.test.liferay.com}xxxx is referenced but not defined.
We have been having this error as well. I have posted multiple times on the liferay forums and contacted them directly (enterprise customer), but no one cares.
So we fixed it by staying on version 6.0.6
I gave up after discovering these API changes.
in docroot/WEB-INF/src/META-INF/shard-data-source-spring.xml
6.0.6:
com.liferay.portal.dao.shard.ShardAdvice
6.1:
com.liferay.portal.dao.shard.advice.ShardAdvice
docroot/WEB-INF/src/META-INF/base-spring.xml
6.0.6
com.liferay.portal.spring.annotation.BeanReferenceAnnotationBeanPostProcessor
6.1
com.liferay.portal.spring.bean.BeanReferenceAnnotationBeanPostProcessor
It seems not to be so easy to develop on 6.0.6 and to deploy on 6.1. (vice versa I didn't try)
I would appreciate feedback on experience with Confluence 4.0 from people who have implemented this version. In particular have you found the 4.0 release stable in your environments?
I've found it exceptional on my Ubuntu 10.10 - stable, but I'm running a limited number of users.
Installer was improved. I miss full-page wiki markup, but clipboard support to copy and paste images directly on a page is excellent.
Personally speaking, it was worth the upgrade.
I'm developing plugins for confluence. If you have a confluence 3.x instance with lots of 3rd party plugins - upgrading to confluence 4 won't work because most 3rd party plugins are not (yet) confluence 4 compatible. Check compatibility for each of the plugins on https://plugins.atlassian.com