Hi,
I try to get started with SSO on Pulse Connect Secure. I asked Pulse Support for a How-To but they say I have to collect Fiddler logs, send them to Pulse and they can configure SSO.
Is there really no How-To available?
If there is no How-To, how can I get started anyway?
Hi,
There are many ways to do SSO (kerberos, ntlm, form post, saml).
If you explain your use case, probably the community will be able to help.
We have several web applications we want to use in combination with kerberos e.g. standard applications like Outlook Web Access or web applications developed by ourselves.
But I don't really know how to get started.
Thank you for your reply @zanyterp.
I am trying to configure the Users>Resource Policies>Web>SSO>General but I am not sure about doing it correctly.
Like our OWA supports Basic Auth (starting with that before trying kerberos or NTLM). So I tried it with Basic with System credentials and Variable credentials using <USERNAME> and <PASSWORD> so the primary credentials will be used to log in to OWA but I still get the log in page instead of getting logged in by the system.
I feel like I'm missing something but cannot put the finger on it.
9apps wrote:Thank you for your reply @zanyterp.
I am trying to configure the Users>Resource Policies>Web>SSO>General but I am not sure about doing it correctly.
Like our OWA supports Basic Auth (starting with that before trying kerberos or NTLM). So I tried it with Basic with System credentials and Variable credentials using <USERNAME> and <PASSWORD> so the primary credentials will be used to log in to OWA but I still get the log in page instead of getting logged in by the system.
I feel like I'm missing something but cannot put the finger on it.
We have several web applications we want to use in combination with kerberos e.g. standard applications like Outlook Web Access or web applications developed by ourselves.
Thank you for the advice about <username[1]>.
Just to make sure [1] is the primary credential set or is it [0]?
I've managed to configure SSO for OWA via POST by creating a new Web Application Resource Profile with Type "Microsoft OWA 2016".
Enabling "Remote SSO" with "servername.tld:443/owa" as Resource and "servername.tld:443/owa/auth.owa" as Post URL.
I wonder if I can do it similar with NTLM but I'm kinda lost about that.