I recently downloaded the 5.3 RC1 distribution of IS and now I want to set it up to be a key manager for WSO2 API Manager 1.10. I checked the Wilkes p2 repo for a compatible version of the key manager to be installed as a feature, but I can't find any. Neither of versions 5.0.3 and 6.0.4 are installable with the 5.3 RC1 version of WSO2 IS. Is there any way I can proceed from this point, or do I have to wait for the GA release and hope for the compatible key management feature to appear in the p2 repo?
Furthermore, will it even be possible to use the combination of APIM 1.10 and IS 5.3, or will 5.3 require an update of APIM or that IS 5.3 be treated as a 3rd party key manager?
Finally, we managed to sort this out. To start with, WSO2 IS 5.3 was released Jan 11, 2017, but it took a few weeks after APIM 2.1.0 was relased that the required feature (Key Manager feature v 6.1.66) appeared in the p2 repository. Then we used the instructions in the documentation for API Manager to configure Identity Server as key manager.
But that only did part of the work since there are incompatibility issues at database and service levels, so we had to fix those. A description of what we did to get APIM 1.10.0 to work with IS 5.3 can be found at Github.
Related
I'm getting this error while trying to publish my .net core console app. There have been no apparent changes to the environment since last week which makes it very strange.
Windows 10
Microsoft Visual Studio Community 2019 Version 16.9.3
Package Manager Console Host Version 5.9.1.0
NuGet Package Manager version 5.9.0
Here is the publish profile:
And the errors:
I've tried this, https://devblogs.microsoft.com/nuget/deprecating-tls-1-0-and-1-1-on-nuget-org/, but it didn't help.
Well, it turns out you need to specifically disable the TLS 1.1 in the registry.
If you don't have the 'TLS 1.1' key you need to create it first, then add the DWORD values just like for 'TLS 1.2'.
I have a service that is referring to Azure SDK 3.0 in turn using Microsoft.WindowsAzure.Storage.dll of version 6.0.0.0. The service is built on .NET Framework and now when I want to to upgrade the Azure Storage SDK(Blobs, Common and Queues) to version 12.4.2, the library is published in .NET Standard
Per my understanding, I can't refer a .NET Standard library in a .NET Framework Library. I searched all over the internet but I couldn't find any way other than migrating my whole service to .NET Core.NET Standard.
Is there any other way to upgrade the latest version of Azure Storage SDKs?
Is there any other way to upgrade the latest version of Azure Storage SDKs?
Direct upgrade from version 6 to 12 is not possible as SDK version 12 is actually quite different than older versions (9 or below).
Firstly, now the SDK is split in many SDKs and there are different SDKs for each service (Blobs, Files and Queues). Thus you would need to reference different Nuget packages in your source code.
Secondly, there have been many breaking changes in the SDKs thus simply referencing the Nuget packages for version 12 is just not sufficient. You will need to rewrite the code unfortunately.
We are planning to upgrade our oracle application express from 3.2 version. Could someone advice which is the latest stable version of apex (5.1 or 5.1.2)? Also please advice if any separate license is needed to install the latest versions?
From their website:
Oracle Application Express Release 5.1.2.00.09 was released on June
28, 2017. This is a cumulative patch set for Application Express 5.1.0
and Application Express 5.1.1.
You don't need a separate licence, since APEX is a no-cost feature of the Oracle database.
As for upgrading from 3.2 to 5.1 the Installation Guide:
If you have release 1.5.x, 1.6.x, 2.0.x, 2.2.x, 3.0.x, 3.1.x, 3.2.x,
4.0x, 4.1x ,4.2.x or 5.0x of Oracle Application Express, following any of the installation scenarios in this guide upgrades your Oracle
Application Express instance to release 5.1 and creates Oracle
Application Express 5.1 database objects in a new schema and migrates
the application metadata to the new release.
I have an app using Microsoft ASP.NET Web API 2.2 OWIN. Installed the latest version (5.2.3) on Nuget and realized it hasn't been updated since February 9, 2015.
There have been individual updates the following packages since 5.2.3 was released:
Newtonsoft.Json
Microsoft.Owin
Microsoft.Owin.Hosting
Microsoft.Owin.Host.HttpListener
Is there a plan for updating or maintaining Microsoft ASP.NET Web API 2.2 OWIN moving forward?
Is it safe to update the packages above?
FYI. I'm running .NET 4.5.
I've updated all of those packages to the latest versions and have not seen any ill effects in any of my applications. It's not really unusual for a package to not receive updates if it is considered stable and there are no new relevant features to release. I would expect that to change when ASP.NET Core is officially released.
I've read that STS 3.6.0 is based on eclipse Luna. However, I have STS 3.6 (upgraded from the IDE since several versions ago) but in the "about" section it says the Platform is Eclipse Juno SR2 (4.2.2).
Is there something special I have to do to upgrade my STS to eclipse Luna and so be able to use Java 8, and Tomcat 8?
If you update STS using the "Check for Updates" mechanism, it updates to newer versions of STS, but it doesn't update the underlying Eclipse platform version. This is by design to avoid complicated situations with conflicting plugin dependencies, etc. Therefore you would need to start with a fresh STS 3.6.0 for Eclipse 4.4 installation in order to jump to Eclipse 4.4 (which also includes the Java8 support).
If you don't want to manually install a bunch of third-party plugins again manually after starting with a fresh STS installation, you can consider to use a script that installs features automatically, like this one: https://gist.github.com/martinlippert/5155155. It is for Mac, but it should be transferable to other operating systems.
Hope this helps!