CODEWITHSUNDEEP
sslibm-mobilefirst
djna
djna

Reputation: 55957

Worklight 6.0 application using SSL

Worklight 6.0.0, targeting iPad.

I have a simple demonstration application, no authentication at present. I am demonstrating use of reverse proxy. So I am building my application using the Build for Remote Server workaround and can see in xcode the correct server specification. I have some adapter calls, but for a particular demo scenario I also want to make an explicit call to

WL.Client.connect( ... );

If I use an http connection I see a request like this:

http://192.168.0.19/MyApp/apps/services/api/Work01/ipad/init

and it works just fine. If instead I use an SSL connection, as expected I see this

https://192.168.0.19:443/Infrabel01/apps/services/api/Work01/ipad/init

And I get the following error.

> [ERROR   ] FWLSE0059E: Login into realm 'NullLoginModule' failed. The
> environment 'ipad' supports multiple versions, therefore you must
> request it with a version parameter.. [project Infrabel01] The
> environment 'ipad' supports multiple versions, therefore you must
> request it with a version parameter. [ERROR   ] 
> FWLSE0117E: Error code: 4, error description: AUTHENTICATION_ERROR, 
> error message: An Error occurred while performing authentication using loginModule
> NullLoginModule, User Identity Not available. [project Infrabel01]
> [project Infrabel01]

That "request it with a version parameter" is intriguing. Is there some extra parameter I need to pass? Or is the overall implication that connecting over SSL requires authentication?

Upvotes: 1

Views: 940

Answers (2)

Sergio D.
Sergio D.

Reputation: 21

I had the same problem.

I have solved it by using the real IP address of the server in the WL app instead of using localhost:

  1. When the emulator is running your app, press the Menu button.
  2. Select to change your server URL
  3. Remove "localhost" and use the IP address.
  4. Accept and try again.

This fixed my problem.

Upvotes: 2

Eric Wang
Eric Wang

Reputation: 109

Please make sure your Worklight server or proxy server is enabled SSL with certificate which signed by a trust public CA like Verisign. Worklight not support private CA certificate.

Upvotes: 0

Related Questions