David G

Okay, thanks for the response, Trevor. This really would be something we'd be very eager to have as with SSO turned on, you effectively limit a cloud solution to only be accessible from your corporate network. With SSO turned off, you're effectively discouraging your customer base from actively using the portal by complicating the login process with an additional logon (it takes just the smallest things for users not to use self-service!).

Trevor, Bit late to this party but are they any updates on the implementation of impact, urgency and priority matrices? Thanks, David

We've successfully implemented SSO for our instance but unless we're missing something it is either on or off for all sites - live, admin, service & customer. Our 250+ customers will only ever access Service Manager (via service.hornbill.com) from within our corporate network so single sign-on using ADFS is ideal and this works as expected. However, our analysts will access the live site from anywhere, both inside and outside the network. What we'd ideally like to do is enable SSO for service.hornbill.com but use password authentication for live.hornbill.com. Although we can create separate SSO profiles for each site, SSO seems to be either completely on for all or off for all. We found an single historical forum post suggesting this is true but is this interpretation correct? If so, is there anything in the change pipeline to allow differential site authentication?