I've seen some cast on //Build 2015 that uses microsoft azure application insights to trace site/application's wealth..I was wondering if there's a way of doing so on a intranet application with restricted internet access.
is there a way of installing insights service on a windows server?
Or does a similar tool exists?
Thanks
Out of the box you won't be able to use ApplicationInsights on a server with restricted internet access because ApplicationInsights needs to send the collected telemetry over to ApplicationInsights service for analysis and aggregation.
However if you would like to configure a an intermediary endpoint on a server that has internet connection you can replace the endpoint address in ApplicationInsights.config. Inside TelemetryChannel node set the value for EndpointAddress property to your custom endpoint:
<TelemetryChannel>
<EndpointAddress><your custom endpoint></EndpointAddress>
</TelemetryChannel>
Then in your intermediary endpoint route the traffic to http://dc.services.visualstudio.com/v2/track
Related
In Company where I work, we have an ASP.NET web application that is hosted on IIS server and binded already with CertificateA. This certificate is owned by the company.
There is another Company let say CompanyB that is providing some Rest API service based on paid subscription.
CompanyB provides subscribers with CertificateB and ask them to send CirtificateB along with the http request when invoking the Rest service.
We have subscribed and received a copy of the CertificateB.
We imported CertificateB on the server and uses Restsharp package from NuGet library to achieve the goal.
It works perfectly and get the proper response when I run the application from within Visual Studio.
However, when I publish it on IIS and run the application I am getting error says:
"The request was aborted: Could not create SSL/TLS secure channel."
Provided that both IIS and visual studio installed on the same machine.
As I said the binding of our web application is already using CertificateA.
Is there any configuration on IIS need to be done regarding CertificateB.
Thank u
I wish we get rid of this error
I got the issue resolved. All I have to do is to give the right permission to the application pool identity to be able to access the certificate.
I am learning PowerApps and while I am surfing on this, I come across Connector and Connections which are main components before proceeding with actions/triggers. So, could you please explain in detailed what is connector and connections on PowerApps?
Thanks in Advance
A Connector is a proxy that sits between PowerApps/Flows and the backend service. This can either simply pass information and requests
along to the backend service or it can change the request going out or the response coming back from the service.
You can create Connectors for things like OneDrive, Twitter, ShrePoint, Facebook etc. and then use those in your app.
A Connection holds all of the configuration information for the user so that you can use a specific Connector. This could be
authentication information such as username and password, database name, environment, etc. Each time you log in to a connector with different credentials, you are creating a new Connection for the same Connector.
PowerApps Datasources can hold additional configuration information
for the Connection. For example, a datasource can use a SharePoint connection and will provide further information on which Site
and List specifically it is referencing.
I have a ASP.Net WebAPI service that is used by my AngularJS front end and I am making use of Owin and bearer token.
Now there is a need that we need to install an agent on the few of the client machines (developed in .Net core mostly) that is able to connect to our application and make similar calls. I can create a separate controller for this need, but want to host it in the same website.
How can I create a secure connection between this agent and the ASP.Net server hosted on Azure?
Currently I am looking at generating a Token during the agent installation based on the client MAC address and giving it with each call, but I am checking if there are any better way to address this need.
Any help in this direction is welcome.
Regards
Kiran
It seems that you’d like to enable only valid “agents” that installed on the client machines to communicate with your server, if that is the case, Azure AD provides Native Application to Web API authentication scenario (a native application that runs on a phone, tablet, or PC needs to authenticate a user to get resources from a web API that is secured by Azure AD), you could refer to it.
I am setting up API Apps within ASE, and I was having some difficulties understanding the usage of access levels.
I noticed that if the API App access level is set to “Internal” it’s not accessible publicly, however, I do not get an internal endpoint, just a public one – so I am unable to access this application internally (for example – browsing to it from a VM in the same network).
How can I access the API App from say a virtual machine hosted on Azure? How can I get an internal endpoint for an API App?
My goal is to be able to access the API App from my VNet, and to have public access blocked.
How can I accomplish this?
Thanks,
Turns out API Apps only have a single end-point which is a public VIP.
Need to create a network security group on the subnet and add explicit rules for public VIP's of back-end machines that require access to the API. This will block internet traffic to the app when it is on public anonymous.
I am using Elmah in one of our production deployments and would like to secure the module to the local network only and not expose it to the public. I am aware of the remote logging option that can be turned off and also asp.net authorization, however I am interested to know if there is any support in Elmah's configuration to bind to a secondary NIC/network card which only faces the internal network ?
There's nothing built-in Elmah that will allow you to achieve this but here's what you might do: disable elmah.axd on your public site and configure it to write errors to some data source (a file, SQLite database or even SQL server). Then configure an intranet site which will have elmah.axd enabled and will point to the same data source used by your public internet site. This way you could use the intranet site to see the errors. If you have a web server farm and multiple applications you could use a centralized SQL Server database which will store the application name as an additional column so that when you navigate to the intranet elmah.axd you will have a complete overview of the errors occurring on your public production servers.