I have already installed Websphere Applcation Server 8.5.5 on my machine without username password.
But for some reason now after using it for several days without any problem, today I got a problem where I am asked to enter username and password in one of the applications which I deployed on WAS8.5.5.
Now how can I create a username and password in an already installed WAS 8.5.5?
If you want to disable application security,
in Security -> Global Security section, uncheck Enable application security
else you want to enable application security, configure User account repository with available realm definitions.
Related
WAS is configured to use an Active Directory to authenticate, but the default admin account was left on the local file repository. When the AD connection is working we are able to login to the admin console using the default admin account, but when AD is down we are not able to use the default admin account to login. Any ideas as to why this is happening?
Any help would be greatly appreciated.
Check this link Unable to authenticate when a repository is down. You didnt write which version you are running, but by default if one of the federated repos is down you will not be able to log in.
You can use updateIdMgrRealm wsadmin command to set the –allowOperationIfReposDown parameter to true. This will allow you to log in with the user from working repository.
Websphere Application Server has configured LDAP to connect to the Domino server. After the server has been restarted I can no longer access the server with the admin credential.
I can not roll back the configuration because I lost access on the server.
How do I resolve this problem?
I am not sure why you might be seeing this problem. But if you want to get into admin console to fix your security setting, you can disable security as follows temporarily.
To disable security, please perform the following steps via wsadmin:
<WAS_INSTALL_DIR>/bin/> wsadmin -conntype NONE
wsadmin> securityoff
wsadmin> exit
Restart the servers.
Enable the security again from administrative console.
http://www-01.ibm.com/support/docview.wss?uid=swg21405302
I've installed the LDAP Integration plugin in SonarQube(Version 5.4) and restarted the server.
I didn't make any changes to config file.
When I try to login, a credential prompt pops up, here I enter the same credentials I use to login to server. But even after this the sonarqube console asks me for a username and a password, this is the sonarqube username and password not the windows one's.
Do I need to make any changes for SonaQube to use windows credentials? or is it just ldap?
Please let me know if I'm missing something here.
I have installed Oracle WebLogic server 10.3.6. To install it, I have to provide a password for WebLogic user. Is there any other admin user and/or any default password for the admin user?
If exists, I have to disable or removed them for security reason. Please help me experts.
I developed an Intranet application which needs to realize a "git push" from a local repository (on the disk of the web server) to a remote repository.
I launch the git process from the web server, it runs under the IIS pool identity which is a domain account member of the administrators group of the web server machine.
Git needs the user credentials to perform the push action. I integrated a custom version of git-credential-winstore. This program uses the Windows Credential Manager to store generic credentials for a web site. But when the call to the credential's write occurs, I get the error :
Failed to write credential: A specified logon session does not exist. It may already have been terminated
I checked the policy "Network access: Do not allow storage of passwords and credentials for network authentication", it is disabled.
What goes wrong here ?
Pool account needs to gain access to its user profile.
So we need to connect one time to a Windows Session to create user profile (I think it's necessary). Next in the Advanced Settings of the dedicated Application Pool, set "Load User Profile" = true.
Note about credentials : Windows credential target must be changed to manage different users in the same Windows vault. I change "git:https://remote-host" by "git_USERID:https://remote-host".
I set this property to enabled and it works now, maybe it will work for you also: