I'm confusing to use the developer portal or deprecated developer portal on Azure API Management. What is the difference between them?
There's a former developer portal that was replaced by a newer one.
This page contains images of the former developer portal:
Getting started with Azure API Management
The new developer portal has a modern look and feel:
Overview of the developer portal
Important
The legacy developer portal is now deprecated and it will receive security updates only. You can continue to use it, as per usual, until its retirement in October 2023, when it will be removed from all API Management services.
https://learn.microsoft.com/en-us/azure/api-management/developer-portal-deprecated-migration
Related
I am trying to publish the Azure APIM developer portal - it is enabled for user/pass - authentication. We haven't customized it and are just trying to get it to work.
When I click publish and go to view the portal in a different browser I get the following message
"This is a home page of the Developer portal - an automatically generated, fully customizable website for publishing your API documentation where consumers can discover APIs, learn how to use them, request access, and try them out.
The content hasn't been published yet. You can do so in "Developer portal" section of your API Management Service in the Azure portal. Learn more."
When I go back to the Portal publish page, it resets to show "Publish" as if nothing has happened?
Are there any logs or anything I can test to get this to work?
BTW - the Legacy portal works 100%.
Thank you.
I have Created the APIM instance and added the HTTP Trigger API from Function App and published the developer portal by enabling the CORS option also.
Next, I have created the user and given all APIs Level access in the APIM Instance and opened both deprecated and legacy portal in different browser, logged in with the non-administrative user:
You can see logs of all activities in the Activity log of APIM Instance:
To see the Function App API imported in the APIM Instance, you have to add that API to the products subscribed by that user:
Published the developer portal again with new changes:
Activity Logs:
Result:
You can check each log activity from the Activity log to see complete details whether the operation publish or other is succeeded and how much time it took to complete.
We did a new release of the development portal in the Azure API Management and it showed the following message:
Creating a new revision or changing revisions will automatically update the portal to the latest version of the software. Content saved in the administrative version of the portal will not be changed.
Which caused that in my portal it now shows me in the box in the transaction detail section all the information to request the authorization token with oauth 2.0
How can I hide the authorization element so that it does not show in my portal for security reasons?
The new Authorization section in the API reference pages surfaces only public information required for clients to authenticate against your API. It doesn't show the secret configuration of your OAuth server. This information has always been publicly accessible, now we just visually render it. If, for some reason, you need to hide the public OAuth server details, you can remove the authorization server configuration from your API Management service. Keep in mind that it will also affect the test console.
If you still consider it a problem, please open a GitHub issue in the developer portal repository: https://aka.ms/apimdevportal and precisely describe your concern.
We have an Azure API Management Service that uses a custom domain. We have it added to the custom domain section of the service, and have a certificate uploaded too.
The certificate has recently expired so we went to the blade and updated the certificate. However, when we hit the API the browser is still serving the old certificate, so we are getting an invalid cert error.
Does anyone have any idea why it might be holding onto the old cert?
After long support calls the issue turned out to be a fatal flaw with that version of the APIM. We had no option but to recreate the APIM and redeploy our APIMs. Microsoft assured us that new instances of the APIM wouldn't have the same problem.
The security challenges are often faced while developing an application. Therefore, the information related to security of the application must be known to the developers.
Can Microsoft SQL Server 2008 Web Edition be used in "closed" websites, which are hosted on the Internet, but require users to log in?
We are developing a web application for banks. This is a website for clients of the bank; it allows clients to log in and view information on their personal banking accounts, stock portfolios, etc.
Can this web app use SQL Server 2008 Web Edition?
Here is information on this edition of SQL Server:
http://www.microsoft.com/sqlserver/2008/en/us/web.aspx
It is said on this page that Web Edition can be used only on "public and Internet accessible ... Web applications". Technically, the web app we are developing is public and Internet accessible - although it requires authentication. Won't using Web Edition in our web app violate SQL Server license terms?
Thank you.
Yes, perfectly. The website is public (everyone can see the login screen) and it is internet accessible (as in: accessed from / through the internet). You probably have a larger public site, actually, with some news and legal discplaimers.
As the authentication you do will be WITHIN the app, it is totally within the limits that the license says.
(and yes, I am SPLA license holder, so I know the SPUR you ahve to follow)