Legacy portal deprecation #2643
Replies: 54 comments
-
Is there a timeline for deprecation, i.e. months or a year after GA? |
Beta Was this translation helpful? Give feedback.
-
@dcbrown16 - not at this moment. Any concerns whether it's for example 6 months vs 1 year? |
Beta Was this translation helpful? Give feedback.
-
@mikebudzynski I'm checking in for a customer in Japan through support. They don't have any particular requests regarding the period, as long as it is announced clearly. Thanks! |
Beta Was this translation helpful? Give feedback.
-
We have some additional detailed questions:
|
Beta Was this translation helpful? Give feedback.
-
@dcbrown16 Thanks, good points. Just to clarify - there won't be an automatic switch to the new version. It's a manual process to configure the new portal in a similar manner to the old one, as indicated here: https://docs.microsoft.com/azure/api-management/api-management-howto-developer-portal#faq
|
Beta Was this translation helpful? Give feedback.
-
Once the new developer portal is GA, how do we disable the legacy developer portal explicitly if we wanted to? Say for instance that we wanted to avoid having 2 locations for documentation, and instead simply migrate exclusively to the new portal. Im wondering if this is an option. |
Beta Was this translation helpful? Give feedback.
-
This will be possible after GA - probably a few months after the release. A workaround in the meantime would be to use the Application Gateway with API Management in VNET and not expose the old developer portal to the public. |
Beta Was this translation helpful? Give feedback.
-
thank you @mikebudzynski , Im happy to hear this will be supported after GA. Thank you as well for the secondary idea for isolating the old developer portal from public. |
Beta Was this translation helpful? Give feedback.
-
Hello,
Many thanks, |
Beta Was this translation helpful? Give feedback.
-
We plan to have a production-ready version of the portal in mid-November and the new version will include significant changes to the widgets (some are already there) and default content and structure. If this timeline works for you, I suggest that you hold off until then and go with the new developer portal - especially because there won't be an automated migration between the old and the new portals. |
Beta Was this translation helpful? Give feedback.
-
Any idea on timing of the old portal deprecation? It would be good to know for planning purposes. We would prefer at least 8 months notice - 12 months preferred. |
Beta Was this translation helpful? Give feedback.
-
The deprecation plans are not finalized yet. Any deprecation will be announced at least 6 month in advance |
Beta Was this translation helpful? Give feedback.
-
What are the migration steps to convert an existing APIM instance to use the new dev portal? Or does a new APIM instance have to be created at this time as a replacement? |
Beta Was this translation helpful? Give feedback.
-
https://docs.microsoft.com/en-us/azure/api-management/api-management-howto-developer-portal#how-can-i-migrate-from-the-old-developer-portal-to-the-new-developer-portal |
Beta Was this translation helpful? Give feedback.
-
Hi Mike, thanks for all the work on the new Developer Portal! Do you have a timeline for enabling social login providers for sign-up and sign-in? I've noticed you have a card titled "[Later] Sign in/up with online identity providers", is it planned in the short-term? We came to rely on Google for sign in since AD is not supported in some tiers of the API Management. |
Beta Was this translation helpful? Give feedback.
-
@mikebudzynski : I found an nother missing feature as our backend is secured with OAuth2. There is a restriction on the interactive Console in compartion to the legacy portal:
Found that on https://docs.microsoft.com/en-us/azure/api-management/api-management-howto-oauth2. |
Beta Was this translation helpful? Give feedback.
-
@mikebudzynski : We have an application error on the page- "https://ericssondeveloperapi.portal.azure-api.net/products" |
Beta Was this translation helpful? Give feedback.
-
OAuth 2.0 is already available in the developer portal, the documentation is outdated - we will fix it. @kmurari029, thanks for bringing this up, we will investigate this issue. |
Beta Was this translation helpful? Give feedback.
-
Can we publish the new developer portal and run it in parrallell with the legacy portal for some time? |
Beta Was this translation helpful? Give feedback.
-
Yes. |
Beta Was this translation helpful? Give feedback.
-
Legacy developer portal is now deprecated and will retire on October 31, 2023. See this post in API Management's announcements repository for more details and migration instructions. |
Beta Was this translation helpful? Give feedback.
-
@mikebudzynski - I am getting this intermittent error on hit of the APIM url (https://momodeveloper.mtn.com/ )- "Something is not right. It could be a temporary glitch or a bug. Please, try again ". The issue is not consistent, it works for some time and some time not. The project is deployed on Legacy portal and is in production. We haven't done any changes of late. However, for some other APIM it's not coming this issue. What could be the issue? Thanks in advance. |
Beta Was this translation helpful? Give feedback.
-
@kmurari029 Please, contact Azure Support - they will be able to assist you with the problem in a timely manner. |
Beta Was this translation helpful? Give feedback.
-
@mikebudzynski Looks like publisher portal (Legacy) option is missing in portal overview. How do we make changes to developer portal (Legacy). We don't see any communication about this change. |
Beta Was this translation helpful? Give feedback.
-
@mikebudzynski Yes, we now don't see the option- publisher portal(legacy) . How do we do edits to the custom pages created in the existing legacy portal now?? |
Beta Was this translation helpful? Give feedback.
-
@vinoth12988 I found it. Click on the Deprecated developer portal link from the Overview portal. It will open your application in admin mode. In the application top right corner, you have Administrator section. Click on it. Then click Manage option. here you get all custom pages created what we had in publisher portal(legacy) |
Beta Was this translation helpful? Give feedback.
-
@kmurari029 - Thanks!! Yes i found under Administrative interface |
Beta Was this translation helpful? Give feedback.
-
Hello @kmurari029 @mikebudzynski Any one has issue in accessing the Publisher portal link. |
Beta Was this translation helpful? Give feedback.
-
@vinoth12988, we haven't made any changes in that area. Please, contact Azure support for assistance. |
Beta Was this translation helpful? Give feedback.
-
This should be closed i.m.o, one caviat is that the "legacy developer portal" button is still shown on Azure but it doesn't do anything. Perhaps something to share with the product team directly. (show an error page) |
Beta Was this translation helpful? Give feedback.
-
If you have questions, comments, or concerns related to deprecation of the old developer portal, please post them here.
Aggregate:
Beta Was this translation helpful? Give feedback.
All reactions