Hello PulseSecure Team,
Pulselauncher no longer is able to connect from command line on 9.1.8.
The same command line used to work on the earlier versions.
sample command : "pulselauncher.exe" -url TESTURL -u TEST-USER -p TESTPASS -r TESTREALM
Did anyone have it working with the url, username, password and realm options?
Hi venkigdl,
Could you please specify the auth method used?
Does it require user interaction?
Regards,
Pulse Secure
Thanks Pulse Secure Team for the quick response.
Details from connection store:
ive "99d5f178-101d-48f8-918a-a9e9469a9e85" {
client-certificate-location-system: "false"
client-certificate-selection-rule: "AUTO"
connection-identity: "user"
connection-lock-down: "false"
connection-policy: "manual"
connection-policy-override: "true"
connection-source: "preconfig"
enable-stealth-mode: "false"
friendly-name: "MYFRIENDLY 3"
guid: "99d5f178-101d-48f8-918a-a9e9469a9e85"
reconnect-at-session-timeout: "false"
server-id: "0285M6WD100HH1ONS"
show-stealth-connection: "false"
sso-cached-credential: "false"
this-server: "false"
uri: "https://TESTABCD.fr"
uri-list: "https://TESTABC.fr"
uri-list-randomize: "false"
uri-list-use-last-connected: "false"
use-for-connect: "true"
use-for-secure-meetings: "false"
version: "6"
}
Yes.. We do have UI that is shown when tried using pulse.exe ( a couple of prompts that need User acceptance). The same works still with the old version of pulselauncher
Logs :
PulseSecureService.exe dsAccessService p3332 t276C accessService.cpp:238 - 'AccessService' creating instance on service iveAccessMethod...
PulseSecureService.exe dsAccessService p3332 t276C accessPluginLoader.cpp:118 - 'AccessService' plugin C:\Program Files (x86)\Common Files\Pulse Secure\iveConnMethod\iveConnMethod.dll, verifying signature...
PulseSecureService.exe dsAccessService p3332 t276C verify.cpp:50 - 'dsVerifySignature' verifying signature on C:\Program Files (x86)\Common Files\Pulse Secure\iveConnMethod\iveConnMethod.dll
PulseSecureService.exe dsAccessService p3332 t3A2C dsaccessworkqueue.cpp:185 - 'WorkQueue' Queued work unit 313
PulseSecureService.exe dsAccessService p3332 t3A2C dsaccessworkqueue.cpp:263 - 'WorkQueue' Start running work unit 313
PulseSecureService.exe Integration p3332 t3A2C method.cpp:635 - 'Integration' IntegrationAccessMethod:nConnectionChange(userdata:99d5f178-101d-48f8-918a-a9e9469a9e85)
PulseSecureService.exe ConnectionManager p3332 t3A2C EventHandler.cpp:58 - 'ConnectionManager' queueing connect change task on userdata:99d5f178-101d-48f8-918a-a9e9469a9e85
PulseSecureService.exe dsAccessService p3332 t3A2C dsaccessworkqueue.cpp:185 - 'WorkQueue' Queued work unit 762
PulseSecureService.exe UiModel p3332 t3A2C StoreListener.cpp:142 - 'UiModel' CStoreListener:nConnectionChange(pszType(userdata), pszId(99d5f178-101d-48f8-918a-a9e9469a9e85))
PulseSecureService.exe dsAccessService p3332 t81C DSAccessServiceFactory.cpp:66 - 'AccessService' Client requesting a service instance
PulseSecureService.exe dsAccessService p3332 t81C accessService.cpp:238 - 'AccessService' creating instance on service UiModelService...
PulseSecureService.exe dsAccessService p3332 t276C verify.cpp:243 - 'dsVerifySignature' C:\Program Files (x86)\Common Files\Pulse Secure\iveConnMethod\iveConnMethod.dll signed by Pulse Secure, LLC and verified
PulseSecureService.exe dsAccessService p3332 t276C verify.cpp:260 - 'dsVerifySignature' verifySignature complete with result 1
PulseSecureService.exe iveConnectionMethod p3332 t276C iveConnMethod.cpp:81 - 'iveConnectionMethod' DSAccessPluginInit: Flags 0x1
Hello Pulse Secure Team,
Did you find time to look into the problem?
Thanks,
Venki
Do see a new connection gets created on the Pulse Client UI right after you execute the launcher command?
Any error message displayed on the UI client?
Hello Pulse Connect Secure Certified Expert ,
Yes a UI notification is shown in the tray that the authentication is rejected and then a new connection is started by the Pulse Client UI.
Let me know if you need any further information.
Thanks,
Venki
Hi Venki,
Thanks for the details,
If the user needs to enter any details like OTP, then this is not supported.
We understand it was working fine before, however, it was a bug and now it stands corrected.
If, the user doesn't need to interact like entering OTP and if still the issue occurs,
Please open a Support ticket as it needs detailed investigation along with certain set of logs.
Regards,
Pulse Secure.