IBM MobileFirst Studio 6.3 installed on Eclipse Juno. Accessing the Operations Console for the deployed application:
Prompted to enter User + Password. What are the default credentials.
How can I disable the need to enter credentials for the development server.
Also, if you can reference where in the 6.3 documentation this information is detailed. I was not able to locate.
The login screen will appear in cases of session timeouts.
In the development environment the default username/password combination is admin/admin.
These values are hard-coded.
I could not find the documentation for this as well.
I've sent a note about it. If anything comes up I'll update the answer.
Related
I am studying IOT-server. I have a question and please help me.
I use WSO2 IoT server and I am not able to access WSO2 IoT server device Management Console (https://localhost:9443/devicemgt) when I input 'admin' both username and password or input this which created a new account.
As a result, it showed me the Authentication failed. When I saw users list in https://localhost:9443/carbon, it showed admin, new accounts .... etc.
I don't know why it does not log in WSO2 IoT server device Management Console.
Please give your advice and then thank you so much.
You need to check Java version, All wso2 Products have issues with the latest version of Java, if you are using java version "1.8.0_151" then that's a problem, try using java version "1.8.0_144".
If you cannot change java version then you need to change the compression parameter to off in catalina-server.xml file
Can i make some changes in MFP Admin console like changing the user >permissions, roles and so on ..., using IBM MobileFirst v7.1
The source for the console is available in the admin .war file you have deployed to your application server. However note that this operation is not supported by IBM. If you encounter any errors, you're on your own.
I have deployed my worklight server 6.1 in WebSphere Application server liberty profile. And i have created the server configuration for application.
Now My console is opening with out login. kindly suggest how to enable login feature for My worklight console.
Make sure your project's .war file contains the configuration for username/password, as detailed in the following documentation topic: https://www.ibm.com/support/knowledgecenter/SSZH4A_6.1.0/com.ibm.worklight.deploy.doc/admin/r_protecting_ibm_worklight_console.html
Anyone know how to configure v6.2 to LDAP to authenticate on the console (localhost:10080/worklightconsole/). On v6.1, this is done in authenticationConfig.xml but the migration process to v6.2, automatically removed all the configuration that was configure to use LDAP to secure the console with this comment:
"IBM migration removed customSecurityTest named WorklightConsole. IBM migration removed realm named WorklightConsole. It is not supported as of Worklight v6.2"
I have already tried following this PDF and still not working - http://public.dhe.ibm.com/software/mobile-solutions/worklight/docs/v620/09_11_Using_LDAP_login_module_to_authenticate_user_with_LDAP_server_in_hybrid_applications.pdf
Thanks
In previous versions of Worklight, Worklight Console protection was handled by Worklight's security framework. Starting v6.2, this is now handled by the underlying application server, be it WAS, WAS Liberty profile or Tomcat.
In Worklight Studio WAS Liberty profile is used, so you will need to follow these instructions: http://www-01.ibm.com/support/knowledgecenter/SSZH4A_6.2.0/com.ibm.worklight.installconfig.doc/appcenter/t_ac_lib_ldap.html?lang=en
For other application servers follow the relevant instructions from here: http://www-01.ibm.com/support/knowledgecenter/SSZH4A_6.2.0/com.ibm.worklight.installconfig.doc/appcenter/c_ac_ldap_jndi.html?lang=en
I have configured and enabled the App Authenticity in my application using custom Security. Added the security test property in my Application discriptor xml file. In my worklight console the respective application gives me the option to enable the App Authenticity.
Now how to test this feature. Fail case senario. How to explicitly fail the client app for app authenticity. My eithcal Hacking team want to perform this testing.
Thanks.
Easiest way to simulate it would be to:
Deploy your application to the server, build the generated project and install it on the device. See that it works.
Depending on the environment, in application-descriptor.xml:
for Android, alter the signing key used and re-deploy to the server
for iOS, alter the bundleId and re-deploy to the server
Re-launch the already install application, it should now fail.
Note:
In Worklight 6.2 application authenticity will only work with an external application server that Worklight Server is deployed to. Otherwise the feature will "always work" when testing in the Worklight Development Server.
In Worklight 6.1 application authenticity will use a "dummy" challenge when used in the Worklight Developer edition; to really test the feature in v6.1, you must use Worklight Studio and Server based on the Consumer or Enterprise editions.