[swift-users] Single-Sign On SSO with Swift Client Openfire Server Windows 2016 Windows 10

Kevin Smith kevin.smith at isode.com
Wed Mar 22 11:01:53 UTC 2017


HI Butch,

I’ve just checked, and this code was also present in 3.0. For Kerberos SSO to work, just enter the domain name in the User Address field at login, and it’ll deduce the rest.

Swift 4.0 is due ‘soon’.

Best,
Kev

> On 22 Mar 2017, at 10:50, Butch MacDougall <butch.macdougall at junotech.com> wrote:
> 
> Kevin,
> 	So does this mean that Swift 3.0 will not support Kerberos SSO even with the system-settings.xml (singleSignOn=true)? Is there a scheduled release date for Swift 4.0? I am on a time sensitive project.
> 
> Thanks,
> 	Butch
> 
> -----Original Message-----
> From: Kevin Smith [mailto:kevin.smith at isode.com] 
> Sent: Wednesday, March 22, 2017 4:42 AM
> To: Butch MacDougall <butch.macdougall at junotech.com>
> Cc: swift-users at swift.im
> Subject: Re: [swift-users] Single-Sign On SSO with Swift Client Openfire Server Windows 2016 Windows 10
> 
> Hi Butch,
> 
> On 20 Mar 2017, at 14:20, Butch MacDougall <butch.macdougall at junotech.com> wrote:
>>              I am looking for documentation (instructions) on how to setup Single-Sign On SSO with Swift Client
> 
> Swift 4.0 won’t expose Kerberos SSO functionality to the user (we’re aiming for this for 5.0, but that’s not set in stone yet), but it can be enabled by dropping a system-settings.xml file alongside the swift.exe binary containing
> 
> <settings>
> <singleSignOn>true</singleSignOn>
> </settings>
> 
> (assuming the server is set up etc.)
> 
> For smart cards, click the certificate button to the right of the password input.
> 
> Best,
> Kev
> 
> 



More information about the swift-users mailing list