The app was registered and worked fine to call O365 Discovery Service to discover API endpoints. But it stopped working lately. I know Discovery Service is to be obsoleted next year, but it should still work now.
Error is:
{"error":{"code":"101,
Microsoft.Online.Services.O365Discovery.O365DiscoveryException","message":"The
app ID is blocked for access of the O365 Discovery Service."}}
Newly created apps does not have access to O365 discovery endpoint due to deprecation. You can now use the graph api to get the info you want.
More info can be found here: https://learn.microsoft.com/en-us/previous-versions/office/office-365-api/how-to/discover-service-endpoints
Related
We have a .Net app that uses Apereo CAS for authenticating. We verified that the app service is not able to hit the CAS back end to submit the ticket coming from CAS. There should be a GET from our App Service in Azure to the CAS server in a different environment but we can't find any info in the logs that will show us an error.
The Apereo code runs inside of the App Svc, configured by entries in our web.config, so we aren't making the GET request in our code.
Maybe someone has had this problem before and figured it out? (hopefully)
Thank you!
Each time we look to create a collection on the discovery GUI using the API we are getting API timeout issues. This happens very erratically.
IBM provides one Website to see if the Services and Systems work fine. The site shows if have Maintenance and the Problems with the services.
I had the same problem with another service. My service works fine now. Verify if you service are ok and check if the service was with status no known issues too.
Check the error:
See the Website.
Unable to login to a newrelic service bound to a bluemix app, returns a Login Failed ! message on the browser
The bluemix app is hooked up to a SSO service, I was able to login to same newrelic instance 2 days ago, now for some reason it stopped working.
Is there a way to get this working without deleting this instance of newrelic ?
You may be encountering an issue with Bluemix restarting services to address a newly identified security vulnerability. See the status updates for individual services here: https://developer.ibm.com/bluemix/maint151023/
I'm building a CloudFoundry application in Bluemix using the API Management service. For this I'm following this tutorial http://www.ibm.com/developerworks/cloud/library/cl-bluemix-api-mgmt-app/index.html.
I can successfully create an API Plan for a custom REST API application (running on a Liberty server on Bluemix as well) and it is published.
I can also create a service in my Bluemix dashboard using the new Custom API, which I take as the API plan was successfully deployed on Bluemix.
Whenever I try to bind this new service I get the following message:
BXNUI2055E: Unable to connect to Cloud Foundry because of the
following exception: "Read timed out." If the problem persists, see
the Troubleshooting topics in the IBM Bluemix Documentation to check
service status, review troubleshooting information, or for information
about getting help.
From time to time I also get this message
The service broker returned an invalid response for the request to
https://apimasv1-stage.stage1.mybluemix.net/d118dceb-edbf-4a7f-9bab-d44371b0c9f9/privateservices/v2/service_instances/1a60830c-0796-4105-afb4-e3477424acf9/service_bindings/ebb853dc-ec88-4987-b8f2-e9acd38d1741.
Status Code: 502 Bad Gateway, Body: 502 Bad Gateway: Registered
endpoint failed to handle the request.
Also, I can open the API portal and see the services listed in there. However, whenever I try to test the service, I get the following error
A security error has occurred. If using a self-signed certificate on
your gateway, you will need to accept it in your browser, which you
can do by clicking the following link.
https://api.wawona.apim.ibmcloud.com/victorshmx1ibmcom-dev/sb/LibraryREST/rs/authors/1
Also, below in the response I get this message:
NetworkError: Failed to execute 'send' on 'XMLHttpRequest': Failed to
load
'https://api.wawona.apim.ibmcloud.com/victorshmx1ibmcom-dev/sb/LibraryREST/rs/authors/1'.
I must clarify this service (the liberty app) doesn't have any security constraint to access the REST service nor I added some kind of security in the API Management portal.
Another thing to clarify is that I can bind other services, but not this one.
Does anyone know how I can fix those problems? Is there a known issue with IBM API Management service?
this seems to be an error with the service API Management instance you are trying to bind to.
You could open a ticket to support team following the link you can find here:
https://developer.ibm.com/bluemix/support/
Click on 'Contact IBM' and open a 'Support ticket'
According to the documentation it only seems possible to authenticate against the windows azure service management API by attaching a certificate to each request which I previously have uploaded to the management portal.
The new management API has been built using the service management API, but it uses windows live authentication. Is it possible to use windows live to get the windows azure subscription ID and the certificate, so I can use the same authentication mechanism the management portal uses?
What makes you think that the Service Management API uses Live ID for authentication? It is just the portal that uses Live ID for authentication.
If you dig a bit you will notice that all the service requests from the management portal are made against https://manage.windowsazure.com/Service while The Base URI for management service is: https://management.core.windows.net
So, No, you can't authenticate against the Management API with Live ID. Moreover, it is the Management API is not new. The portal is New. The management API has been there for a while and is updated from time to time to reflect new services that are coming.
UPDATE AFTER THE 2 COMMENTS
Following Gaurav's explanation I will just add a simple architecture diagram (super simplified and totally my thought, but this is how would I build it in very minimalistic way):
[User's browser (portal)] ==> Sends XmlHttpRequest (AJAX) to ==> [Portal Service]
then
[Portal service backend] ==> signs request with predefined certificate and sends request to ==> [management.core.windows.net/subscription-id/whatever/service/command]
This actually is a very common practice to provide UI to a (web) service.
This way both conditions are implemented:
You use Live ID to authenticate with the portal
The Windows Azure Service Management API are yet, still and only protected by a Certificate.