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
Related
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
I have to implements a single sign on procedure between 2 web applications.
One of them is running on OAS version 10.1.2, developed using JDeveloper 10g, the application uses ADF framework (10.1.2) and Java 1.4. It authenticates users using a JAZN.xml file, so the users/ passwords aren't in database.
The other is a RESTful application running on a Glassfish 4.1 server, developped in Java 8. Each modules are bundled as OSGi bundles. Authentication not implemented yet.
We were planning on using an LDAP server (Oracle Internet Directory, the only one working with ADF 10.1.2) but I can't seem to be able to find clear documentation about it.
I've found http://java2go.blogspot.com/2012/05/oracle-adf-with-sso-definitive-guide.html which is for WebLogic not OAS, and http://sqltech.cl/doc/oas10gR31/web.1013/b28967/adding_security001.htm which is for version 10.1.3
1- Is there a place with more documentation, how-to, on LDAP configuration with ADF 10.1.2?
2- Is it possible to manage Users/password from the app using LDAP authentication or we must connect to LDAP server to change/create users/passwords?
3- what do you think would be a better approach to implement SSO?
I am using Worklight 6.2 consumer edition. When I deploy my app, following warning flashes on server console:
[WARNING ] FWLSE0259W: Application authenticity protection is not being performed within the Worklight Development Server. In order to fully test Application authenticity protection, deploy the application to a non-development Worklight Server (i.e. external Worklight Server). [project MyProject].
I am using Web Sphere Liberty Profile 8.5.5.1 server. Pls advise how to make this warning make go away?
As the message says, if you are trying to test Application Authenticity Protection in Worklight Studio (the Eclipse development environment of Worklight), Authenticity protection is not supposed to work.
To test Application Authenticity in Worklight 6.2, you must deploy Worklight using IBM Installation Manager to your Application Server (WAS, Liberty, Tomcat), as well as your .war, .wlapp, .adapters, etc... and set it up in Worklight Console belonging to this instance of Worklight.
Only then should it work.
I am trying to install and configure Worklight application center on liberty profile.
I have installed the worklight 6.2 using the installation manager. Along the installation process i have installed the appcenter as well.
The installation was successful. But when i try to access the console it giving me "Context root not found".
Also I have checked the server.xml of the liberty server. It contains the appcenterconsole.war and the applicationcenter.war mapped.
Does anyone experience this problem as well?
This might be the same problem as mentioned here: Worklight Development Server does not start
Please make sure you use Oracle Java, not IBM Java!
I am running Worklight Studio 6 from Worklight Enterprise Edition download with Eclipse Juno.
My application is using form security with the WASLTPA login module. The application tests correctly.
When I add AppAuthenticity (needed for device provisioning) my client sees the following error in the console. (None in the server log)
Failed to load resource: the server responded with a status of 401 (Unauthorized)
drilling deeper I see:
/*-secure-
{"challenges":{"wl_authenticityRealm":{"WL-Challenge-Data":"o97e2ph8kguqh1vpljbio1o5k3+23.507-9.852-31.807 "}}}*/
I am running this on the Worklight Development Server packaged with Worklight Studio.
You have mentioned both the Enterprise Edition and Developer Edition.
Please clarify your question with the following: You have installed Worklight using the IBM Installation Manager, yes?
You have an application server (Tomcat/WebSphere/Liberty) installed and you've used the supplied Ant scripts to create the Worklight database(s), configure them, deploy the Worklight platform files to the application server, as well as deploy your project's .war file? (and of course the .wlapp /.adapter file(s)...).
If you have done the above, then you will have in your Worklight Server, now installed on the application server, the required components for App Authenticity to work.
Then there is the case of how you actually configured your project for App Authenticity.
Make sure you follow these steps to set up App Authenticity