We are using Glassfish and cannot access admin console remotely when 'enable-secure-admin' is enabled using the default port 4848.
We are trying access over dev-vpn, but cannot do so when we use the subcommand 'enable-secure-admin' . If it is disabled we can see the web-page but cannot login.
Is it something to do with 'http-redirect' ?
Related
SonarQube 8.6+ enforces user authentication by default.
How do I allow anonymous access since the first startup?
I am running SonarQube on a local Docker Container and I would like to automate this step. That is, I am looking for a solution not involving:
Log on to SonarQube with the default credentials (login: admin, password: admin).
Change the default password.
Manually disable the Force user authentication property from Administration > Configuration > General Settings > Security.
You could enable the anonymous access by adding the following property to the $SONARQUBE-HOME/conf/sonar.properties file:
sonar.forceAuthentication=false
How to modify the file in Docker you can find here: https://stackoverflow.com/a/27714071/4944847
After installing patch 10.3.6.0.200114, Weblogic console could not log in, indicating "WebLogic Server has rejected this user name or password. Please try again. " However, the service can be accessed normally
There is a bug in this PSU which prevent web app like the admin console to authenticate users. Oracle published a patch to correct this issue : SU Patch [EIL8]: 10.3.6.0.200114WLSPSU Overlay: CANNOT LOGIN TO CONSOLE, BUT CAN LOGIN TO EM WITH THE SAME USER
Download it from MOS and patch your WebLogic server installation.
I am having an issue deploying my app to a remote server. This is the error I get when trying run the cli add command:
mfpdev server add myqaserver --url https://mbmfp.mycompany.com --login admin --password aaaa --setdefault
Error: URL 'https://mbmfp.mycompany.com' is not valid. The URL must have the following format 'protocol://host:port'. Run 'mfpdev help server add' for more information.
My hostname name https://mbmfp.mycompany.com contains the port. So adding the port again will cause an issue
Initially, I tried the register command and was prompt to used the add command
mfpdev app register https://mbmfp.mycompany.com mfp
How do I fix this issue?
INFO
IBM MFP version 8.0.0-2016121916
Thanks
Doesn't look like you're executing the commands correctly...
Here's an example:
mfpdev server add
? Enter the name of the new server definition: mydevserver
? Enter the fully qualified URL of this server: http://mydevserver.example.com:9080
? Enter the MobileFirst Server administrator login ID: admin
? Enter the MobileFirst Server administrator password: admin
? Save the admin password for this server?: Yes
? Enter the context root of the MobileFirst administration services: mfpadmin
? Enter the MobileFirst Server connection timeout in seconds: 30
Verifying server configuration...
The following runtimes are currently installed on this server: mfp
Server profile 'mydevserver' added successfully.
Then, navigate to the root folder of the application and:
mfpdev app register mydevserver
Learn more here: https://mobilefirstplatform.ibmcloud.com/tutorials/en/foundation/8.0/application-development/using-mobilefirst-cli-to-manage-mobilefirst-artifacts/#add-a-new-server-instance
We are running Glassfish 3.1.2.2 authenticating against an Active Directory realm. Authentication works correctly the vast majority of the time, but occasionally, authentication will suddenly start failing for all users, and we'll see errors like this in the server log:
[#|2014-03-19T21:37:32.331+0000|WARNING|glassfish3.1.2|javax.enterprise.system.container.web.com.sun.web.security|_ThreadID=1098;_ThreadName=Thread-2;|WEB9102: Web Login Failed: com.sun.enterprise.security.auth.login.common.LoginException: Login failed: Failed file login for jeff.|#]
Note that the error message is failed file login. It appears as if Glassfish is occasionally reverting back to the file realm rather than the active directory realm.
When this problem happens, after a short time without any intervention on our part, authentication will suddenly start hitting Active Directory again and users will be able to login again.
Any ideas why Glassfish would occasionally revert to authentication against the file realm when we've configured it to use Active Directory? Should I delete the file realm altogether?
I finally determined the trigger for this. We had been connecting JVisualVM to our Glassfish instance to monitor performance. Everytime I connect JVisualVM (over JMX connection using Glassfish admin credentials), Glassfish immediately reverts to using the file realm instead of the LDAP realm. I have no idea why JVisualVM would cause this behavior in Glassfish, but it is consistently reproducible. The only workaround I have discovered is:
Disconnect JVisualVM.
In Glassfish admin console go to -> Configurations -> server-config -> Security
Change default realm (to anything other than LDAP realm), Save.
Change default realm back to LDAP realm, Save.
Clients should now again be able to authenticate against LDAP.
This is a simple question: is there a way to tell GlassFish to load & deploy admin console during startup and not on-demand?
In the admin console, go to the "Domain"view. There a checkbox labeled
Load console after DAS startup. Make sure it's checked. Don't forget to save, now the admin console will be loaded automatically instead of on the first access.
You can also use the asadmin utility to change this setting:
asadmin set configs.config.server-config.admin-service.property.adminConsoleStartup=ALWAYS