I have openfire installed on my windows 7 and I am able to add users in the web admin interface .I am also able to connect clients using spark (locally on localhost).When I try to connect with other clients the connection fails .I have tried Psi (http://psi-im.org/) and the gui example for QXmpp (https://github.com/qxmpp-project/qxmpp/tree/master/examples/GuiClient) .Psi fails saying it is problem with certificates： There was an error communicating with the server.Details: Authentication error: Not authorized. I looked into the security settings and can't find anything that lets the QXmpp gui client connect successfuly .
What can I do to minimize security concerns so my QXmpp clients can connect successfully?I might enable those later as I get more comfortable with xmpp programming. I would appreciate any piece of help.
I don't know if openfire disables other clients to connect by default ,but by installing the Client Control plugin(http://www.igniterealtime.org/projects/openfire/plugins/clientControl.jar) and allowing all clients to connect I was able to connect my QXmpp clients.Hope this helps somebody some day.
Related
i have running some NiFi stand alone instances in secured mode. connecting each other vie site-to-site is working fine, i'm not able to get a connection to itself.
let's assume some nifi instances
- https://my-nifi-1.local:9443/nifi
- https://my-nifi-2.local:9443/nifi
- https://my-nifi-3.local:9443/nifi
doing a remote connection between https://my-nifi-1.local:9443/nifi and https://my-nifi-2.local:9443/nifi and https://my-nifi-3.local:9443/nifi works properly.
if my flow sends some data via "Remote connections Output Port" to a Remot-Process-Group on the top level of the flow, then its not working.
ErrorMessage: forbidden - Site-to-Site is not secure.
i tried to configure my RPG using https://my-nifi-1.local:9443/nifi or https://localhost:9443/nifi.
THX for any help
found the solution
Each instances CN has to be added to the users and also there are some policies to apply
Thanks to Bryan Bende I could figure it out -> https://bryanbende.com/development/2016/08/30/apache-nifi-1.0.0-secure-site-to-site
I created an ASP.NET Core Web API and deployed it in Azure as an App Service.
I created a Hybrid Connection and installed the Hybrid Connection Manager on the On-Premise Database Server, set the Hybrid Connection Status to Connected (Successfully connected the App Service with On-Premise Db Server).
When sending Get Request or accessing the Web API on the web browser or Postman
The Result I receive is:
500 - The request timed out. The web server failed to respond within
the specified time.
When developing the Web API on my local machine it works smoothly and I could connect to the On-Premise through a VPN connection.
I also added this piece of code
services.AddDbContext<RepositoryContext>(o => o.UseSqlServer(connectionString, sqlServerOptionsAction: sqlOptions =>
{
sqlOptions.EnableRetryOnFailure(
maxRetryCount: 5,
maxRetryDelay: TimeSpan.FromSeconds(60),
errorNumbersToAdd: null);
}));
In the absence of more information, the 500 error, I guess the most likely reason is that there is a problem connecting to the On-Premise sql server.
TroubleShooting:
Click Diagnose and solve problems to view Application Event Log to view specific logs.
(Optional) Open Application Logging (Filesystem) and Detailed error message.
Specifically, you can log in to the scm website to view the error log.
If you test the interface and connect to the database locally or using vpn, there is definitely no problem. Now the problem must be the database connection part. It is recommended to recheck Hybrid connections. You also can raise a support ticket on portal, let them check logs and help you.
Related Posts:
1. Hybrid Connection Shows “Connected”, but Application Fails to Connect
2. Azure Web App Hybrid Connection Failing
Problem
The Hybrid Connection's Endpoint/Host I made in Azure had a different name as the SQL server. I named the endpoint randomly instead of giving it the actual name/IP address.
Additional info
Even if you installed the Connection Manager on the Server and the Status is set to Connected, this doesn't mean that your App Service will communicate with the Database.
Solution
Create a new Hybrid Connection and set the Endpoint Host name with the actual name/IP address, where the Hybrid Connection Manager is installed.
I was trying to connect mqttbox(Chrome extension) to rabbitmq server for load testing. The client created in mqqtbox is connecting properly but its not able to do load testing.
No much to change, just enable the guest user with administrator permission will resolve the issue.
The problem I have is that we're trying to use our WebApp in Microsoft Azure to connect to an external SQL-database (not our own) through a VPN. The SQL-database is only allowing connections from our local IP-addresses that we put up as a Network (for example 176.0.0.0/24).
We are now connected to the same virtual private network, and through our Azure-VM we can now connect to the SQL-Server through SQL Server Management Studio.
Now we want to do the same with a WebApp, but we're not getting through to the server. It gets "Not authenticated" before reaching the SQL-Server (probably the server isn't accepting our IP from the WebApp).
The different problems I have tried to look through is:
Do we only try to connect through our Outbound IPs?
Is the WebApp not connected to the VPN?
I have unfortunatley not found any real answers, and neither any solutions to my problem. If you have any ideas of how to solve our problem, or maybe know how I could tunnel all of the SQL-calls through the VM, the help would be very much appreciated!
Hybrid connection is one option. What you can also do is enable point-to-site in your VPN. Once you do that, you can directly integrate your web app to the vnet and your connections will work. (Go to your web app -> Settings -> Networking -> VNet Integration)
If your Vnet is V1(older way of creating VNs) then enabling point to site is very straightforward. You can do it through portal. For V2 Vnets you have to do it through powershell commands.
Here is a link for the documentation which explains both the options.
https://azure.microsoft.com/en-in/documentation/articles/web-sites-integrate-with-vnet/
There's a way to "tunnel all of the SQL-calls through the VM". You may want to use hybrid connections (cf https://azure.microsoft.com/en-us/documentation/articles/integration-hybrid-connection-overview/).
The principle is to have an agent installed on the VM that can access the database with the correct IP address.
Suppose you can access the SQL DB as mysqldbsrv from the VM. You add an hybrid connection associated to your web app, you install the agent on the VM. Then, when you connect to mysqldbsrv from the Web App, you go through the VM.
I created a Web Disk at my remote server using and now I am trying to access it at Windows 7 and 8. I downloaded VBS script and also tried connecting using manual instructions provided in cpanel.
Problems
For some reasons it only connects at port 2077 and not 2078 even when I select digest authentication. My sever is secured by SSL certificate.
It disconnects the drive after few seconds and will not connect again. It triggers 'network path not found' error. I have tried enabling NETBIOS over TCP/IP but still no luck. It partially works if I logout and log back in but again disconnects after few seconds.
Desired Output
It should connect using port 2078
The connection should be persistent and I do not have to log out and log back in if I want to reconnect.
Any help will be greatly appreciated.
Thanks,
Though this is an old post but maybe this will help you.
In Windows 7 Basic authentication cannot be persisted by the Credential Manager in Windows 7, this is new to the OS.
The only way with Basic authentication mode to reconnect is to disconnect the drive and reconnect again, because WinHttp is not able to retrieve saved Basic and Digest credentials.
For persistent connections ensure that an authentication scheme is selected that allows to have persistent credentials through a reboot.
For example Kerberos for authentication or certificate based authentication will work.
WORKAROUND
Check source for the workaround.
Source: http://support.microsoft.com/kb/2673544