WSAM fails to auto-launch

[papageno_]

As far as I can tell, I have configured an SA4500 to auto-launch WSAM on login, but it fails to run.  Can anyone suggest why?

WSAM is enabled at the role level, and Auolaunch WSAM is enabled at the role level.  When a user logs in to the role, the Welcome page only shows Junos Pulse under the Client Application Sessions, and WSAM doesn't launch.  The user is definitely authenticating to the role configured for WSAM.

I have placed the SA in the client's Trusted zone for IE, and even installed WSAM manually.

The SA is running version 7.2R3

Any help gratefully received.

[jayLaiz_]

This works for me in 7.2r3

Under the role and general options, did you verify secure application manager checkbox is checked

Regards,

Jay

[muttbarker_]

This is working "as designed" - In 7.2 if you have a role that has has WSAM and Pulse enabled then you will only see Pulse under the client application sessions. The Pulse component can be launched and will provide the WSAM capability. 

Check the release notes for a more detailed description.

[papageno_]

jayLaiz - Yes to both role and general options.

[papageno_]

Hi muttbarker

Thanks for the feedback - it is somewhat helpful and I have now configured the access I was attempting through WSAM via Pulse instead.  However, I'm not sure your answer is the "last word" on the subject.  According to my reading, it should still be possible to work with WSAM instead of Pulse, and as JayLaiz says, it works for him in 7.2r3.

This KB article suggests that it is still possible to use WSAM instead of Pulse, simply by disabling the Pulse option in Role...General...Overview, and WSAM should deploy instead.

I'm not sure my customer actually needs to use WSAM with the new code.  They are replacing older SA boxes that do not support Pulse, but if I can get it to work it may ease the migration.  So if anyone has any ideas on why WSAM doesn't appear on the user's home page, and won't auto-deploy, I'd be interested to hear them.

All the same, many thanks for the input.

[muttbarker_]

Yes - WSAM can still be deployed. However what was trying to say (poorly) was that if you deployed WSAM and Pulse concurrently then the only option the end user would get would be Pulse as Pulse would provide the WSAM functionality. Disable Pulse and WSAM appears. Enable Pulse and the policies developed under the WSAM profiles would be implemented by Pulse so the WSAM launch option (or auto-launch) is disabled. 

Are you saying that you setup a WSAM resource profile, disabled Pulse from the General Tab and it still did not show or auto-launch? I actually did some extensive testing, turning Pulse on and off, playing with this and never saw that happen. 

Thanks!

[jayLaiz_]

Hi Papageno,

Muttbarker is right, WSAM can be configured via pulse in 7.2x so if you check pulse, WSAM will not show and vice versa.

Regards,

Jay

[papageno_]

Hi Muttbarker

Yes - that's exactly what I'm saying.  The WSAM resource profile works fine through Pulse, if I have the Pulse checkbox ticked on the General tab.  I can absolutely guarantee this is true, and the traffic is being carried over the Pulse connection, because I can see the traffic hitting the WSAM server from the Pulse VPN client address on the right port.

However,  if I untick the box, the WSAM launch icon does not appear on the user's home page, nor does it auto-launch as configured.  I feel I'm missing something obvious in the configuration, as JayLaiz reports no such problem.

Any ideas?

[muttbarker_]

Wow! I wish I had a suggestion for you. But your testing is exactly the same scenario that I ran through when I went to 7.2 except the results are different

I always get WSAM to launch / display if Pulse is disabled via the General Tab. I can also tell you that in testing this functionality I never saw anything in either the log (event / user) or policy trace that would help debug. My only other suggestion would be turn on debug on the client and check those logs. 

Bizarre.