I have made a copy of one of our live ldap servers to use in testing environment.
In our live system we have 2 ldap servers in master/master configuration.
My question is on our testing environment as there is only one server how can I delete the offline ldap server from DSCC. I have tried to remove it using the web interface but as its offline it throws an can't communicate error.
I have also tried using the dsccreg remove-server command with no success.
Any ideas?
You probably want to look at MOS note 1920317.1
Related
A Weblogic server got hacked and the problem is now removed.
I am looking through the infected VM's now in a sandbox and want to see what if any data was accessed on the application servers.
the app servers were getting hammered with ssh requests and so we identified the infected VM's as the web logic VMS, we did not have http logging on. Is there any way to Identify if any PII was Compromised?
Looked through secure logs on weblogic as well as looked through the PIA logs
I am not sure how to identify what if any data was accessed
I would like to find out what went out of our network and info or data
what should I be looking for
is there anything I can learn from looking at the weblogic servers running on red hat?
I would want to believe that SSH was not the only service being hammered, and that was a large attempt to make eyes be on Auth logging whilst an attempt on other services is made.
Do you have a Time frame that you are working with?
Have the OS logs been checked for that time frame?
.bash_history been checked? env variables? /etc/pass* for added users? aliases? reverse shells open on the network connections? New users created on services running on that particular host?
Was WebLogic the only service running on this publicly available host?
What other services and ports were available?
Was this due to an older version of Weblogic or another service, application, plugin?
Create yourself an excel spreadsheet and start a timeline.
Look at all the OS level logging possible and start to make note of anything that looks suspicious, to then follow that breadcrumb to exhaustion.
I have a FreeRADIUS server that uses ldap as as a storage backend for its users. They are both located on the same machine running UBUNTU Linux 12.04 LTS.
Now I would like to set up another ldap server on another machine to add redundancy so that I could use it in case of my local ldap server's failure. Can anyone tell me how I can do it? Nothing is mentioned in RADIUS configuration files regarding multiple ldap servers.
The same question applies to Samba.
Any help would be greatly appreciated.
This is actually pretty easy, you can just list multiple servers here in the LDAP configuration, separated by commas.
libldap takes care of the rest.
Edit: For later versions of FreeRADIUS 3 the LDAP module expects multiple instances of the server config item. For example:
server = 'ldap1.example.org'
server = 'ldap2.example.org'
server = 'ldap3.example.org'
This is so internally, when the module is rewriting the URIs, they're already broken out into separate strings, which makes the code easier. It also looks a bit cleaner.
I need a way to use Glassfish 3.1.2.2 admin service (REST call to deploy and configre) from a remote machine and from local machine (command line and applications).
It is clear that for remote access it is necessary to enable secure admin. If we enable secure admin it will break all local access from applications. These application can not be changed to using https to access the admin service. Only thing I can change is that we can use a different port.
I see two possible ways for me:
Using a hack. So I can administrate with secure administrate disable. So I can use plan http. For use a possible solution, because this machine used internally in a test environment.
Configure Glassfish that we can use admin service remote via secure access https and from a local environment with http.
We prefer solution 1, because it fit better in our environment and we have lesser effort. At the moment I see no way or exist a solution (not for production)?
I tried something for solution 2, simular to http-listener-1 http-listener-2. So use two ports 4848 for local unsecure access and as example 4949 for remote secure access.But I always fail with configuration. So I start with a step by step configuration. First enable admin interface oon two ports and as second step I want to add the secure access to the new port admin-listener. But I got only one of the ports working.Please can anyone help me with target configuration? Any domain.xml will be welcome.
Thanks florian
You can try to use SSH and run asadmin utilities from remote machine.
I have an application that needs to be deployed to two different servers (environments).
I have two environments on two separate servers, server1 and server2.
Both servers have different IIS Manager user accounts and passwords configured.
The builds however all happen on server1 and it appears that no matter what settings I pass via the build definition, everything gets deployed to server 1.
I can publish to server2 manually from the Publish command in VS2010 but this needs to be automated in TFS.
This used to work fine but then started happening a couple of weeks ago.
How can I correct this problem?
In the end, although I followed the IIS generated settings file, I had to set the MSDeployPublishMethod to WMSVC (it was set to MSDeploy). I can't tell you why this works and the other doesn't but this is how I solved it. If anyone has any details on where one can find out more about the various Web Deploy settings please advise!
I've just installed XAMPP and just wondering what are the benefits of running Apache as a service?
One of the benefits is that when installed as a service is that you can limit the privileges (directories read/write access, network access, this means better security of course) of the account that runs it (the default is the LocalSystem account on Windows, you can find more about it here).
And as admin pointed out, you can also keep the service running without you being logged in all the time.
The benefits of a service in general (on Windows) :
It can automatic start at System Logon
Start and stop not related to a specific user session
Run in Background
Can run under a special account (LocalSystem, Network Service)
From Vista/Server 2008 onwards run in Session 0 (Isolation)
If you use apache only for developing purpose you can avoid to install it as service and run it when needed directly from your user session, in a production enviroment is highly recommended to install and run it as service ...
-Don't have to start it after each boot.
-If you log off the server continues running.
If you will use the server all the time, set it as a service... If not, just start it when you need it to keep the resourses free.