Hi
I want to configure SSO for client server application Lotus through WSAM. Where is the option in configuration for SSO and this need any special license?
Thanks
Howdy - SSO and WSAM don't play together - here is another thread where this issue came up:
https://forums.pulsesecure.net/topic/pulse-connect-secure/22600-wsam-amp-sso#M4625
HI
Thanks for your help. let me explain you my scenario kindly suggest the solution with SSO. I want to access the exchange server though for send/recieve emails through outlook client over the internet via SSL box.
Kindly suggest the what access method I can use with SSO?
Thanks
Currently the SA Platform provides 4 major types of SSO functionality as listed below and an administrator should use a method that their backend infrastructure supports.
1. Basic Auth
2. NTLM
3. Kerberos
4. Form Post (Remote SSO)
However these 4 methods are restricted to Web based applications that are access via Web Access Method only (as Mentioned in above post)
Having said this, if you are using domain PC's/machines then you may leverage the SSO built into the client application. I.e.. Outlook in your case. For this you should configure WSAM to support 'Domain Authentication'.
To configure Domain Authentication (high level steps)
1. Roles > SAM > Add application > Select Domain Authentication
2. Roles > SAM > Add Servers > Add the Domain Controllers IP
3. Create WSAM ACL's to allow the IP's entered in above step)
Hi ruc
Thanks for your reply. It means that using your high level steps I can still use SSO with outlook client with exchange server?
Other things is that kindly can you explain the below authentication methods for SSO in one or two lines.
1. Basic Auth
2. NTLM
3. Kerberos
4. Form Post (Remote SSO)
Thanks
Yes - the high level steps documented will allow for credentials to be passed from the client machine to the Exchange server. The machine must be a member of a Domain.
Out of order but here are some explainations on the other stuff:
1- Form Post - used to pass credentials into to an HTML page. This is for web page based authentication where you are passing values like username and password to the web page for processing.
The other policies are tied into the types of challenges issues by the authenticating machines. I would recommend the admin guide - "Defining Resource Policies: Single Sign-On"
Hi Kevin
Thanks for the reply. But I have one confusion that you and ruc both said machine should be the part of domain. For example I am at home and wants to access my emails on exchange server through SSL VPN via outlook client then in this SSO will work?
Thanks