I setup packetbeat on a server and set switch mirror traffic to this server.
It works fine except I can not collect user failed login.
Anything I misunderstood by using packetbeat ?
Any solution with "beats" can do without enable MariaDB Audit Plugin?
Related
I'm using the WSO2 Identity Server version 5.3.0. I'm also using WSO2 API Manager 2.1.0.
I created 2 APIs, one which disables the user which by calling the admin service and also an API to enable the user as well. I also created an API to check the user status(disabled/enabled) which checks whether the relevant user is enabled or disabled once the username is entered.
The whole process works fine for a couple of rounds.
disable a user -> check the status(user gets displayed as disabled) -> enable the same user -> check the status(user gets displayed as enabled)
However, if the same user is disabled from a remote computer, the status wrongly gets displayed as enabled and also the user does not get disabled as well. But after I restart the Identity Server, the status gets displayed correctly as disabled and the user is also seen as disabled from the previous API call.
Has this issue got something to do with the cache in Identity Server?
Any suggestive approach to solve this issue is much appreciated. Thanks
From your description, it seems you have more than one node of Identity Server in your deployment. If so, you have to enable clustering in order for the caches to be synced. Otherwise the cache update in node 1 won't be reflected in the node 2 until the cache expiry time reaches (default 15 minutes) or a restart.
Enabling clustering for US 5.3.0
Hi I am trying to deploy a website on an Azure VM and I already set all the configuration for make a deployment but this error appears when I tried to publish:
Error Web deployment task failed. (You connected to the remote computer ("saveci1.westus.cloudapp.azure.com") using the Web Administration Service, but it could not be authorized. Make sure you are using the correct username and password, that the site the one you are connecting to exists and that the credentials represent a user who has permissions to access this site.Get more information at: http://go.microsoft.com/fwlink/?LinkId=221672#ERROR_USER_UNAUTHORIZED.)
Make sure the site name, user name, and password are correct. If the issue is not resolved, please contact your local or server administrator.
Error details:
You connected to the remote computer ("saveci1.westus.cloudapp.azure.com") through the Web Administration Service, but could not be authorized. Make sure you are using the correct username and password, that the site you are connecting to exists, and that the credentials represent a user who has permissions to access this site. Learn more at: http://go.microsoft.com/fwlink/?LinkId=221672#ERROR_USER_UNAUTHORIZED.
Remote server error: (401) Not authorized. PoC 0
I follow all the steps from here https://github.com/aspnet/Tooling/blob/AspNetVMs/docs/create-asp-net-vm-with-webdeploy.md
Could you please check if is there any IP restriction configured for the resource group in Azure portal as it could be the reason.
Also i would suggest you to put a fiddler and trace the request which is causing the failure.
please check if you are behind any proxy, if yest then try to connect to a network that does not require this SSO through the proxy or use one of the many other ways to publish that do not require an SSO connection from your machine such as, FTP, VSTS, Git etc… and try to deploy it. Most of the time proxies are the reason which could cause failure in deployment.
As a workaround you could ftp to the site & do deployment via that method .
Hope it helps.
i have maxscale installed, I obtain this error:
Refresh rate limit exceeded for load of users' table.
what can I do? I have mariadb database
When the authentication of a user fails, MaxScale reloads the list of database users. This reloading is rate limited which causes the error message in question to be logged.
Inspecting the error logs of MaxScale for any clues about the failed authentication attempts will allow you to fix of the root cause of the problem.
The MaxScale tutorial over at the MariaDB KB shows How to set up MaxScale and how to configure database grants for use with MaxScale.
I created a db via app-data folder, migrated over to server explorer and tried to connect to it and I get
Cannot open database "abc" requested by the login. The login failed. Login failed for user 'xyz'. I came across this: [Cannot open database “test” requested by the login. The login failed. Login failed for user 'xyz\ASPNET'
I have two questions concerning the best answer.
Whenever I connect to ssms windows authentication is selected. So does windows authentication still matter if a db is created using visual studio?
Second is concerning this:
UPDATE: Ok, you're using integrated Windows authentication --> you need to create a SQL Server login for "xyz\ASPNET" on your SQL Server"
What does he mean by create a sql login for user "xyz"?
I thought the purpose of win authentication was so you didnt have to type login and pass to connect. You're automatically connected through windows. Right?
I'm getting the following error on my dev machine when attempting to manage SSO settings:
ERROR: 0xC0002A0F : Could not contact the SSO server 'SSODB'. Check that SSO is
configured and that the SSO service is running on that server.
The Enterprise Single Sign-On Service, RPC service, and COM+ System Application service were all started when I checked, but I gave them a restart anyway and it didn't fix the problem. I can access the SSODB through SSMS.
I unconfigured SSO through BizTalk and reconfigured it (successfully). Alas, this also did not help.
SSO was previously working fine. I did notice this morning upon reboot that my browser home page was reset back to our corporate site (meaning something may have been pushed to machine this morning when I signed on) but no one else on my team is experiencing the same issues.
I'm not sure what to try next. Anyone have any ideas?
So, is SSO still working for BizTalk? If so, this might just be a simple user level config issue for SSO. based on the browser info, some user local settings may have been messed up. Try this:
CD to "C:\Program Files\Common Files\Enterprise Single Sign-On" Use administrator privileges
Type: ssomanage -server [SSO Server Name Here]
This will reset the SSO Server name for your user account.