This discussion has been locked.

You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Agent works, SSO does not

Prior to updating to 9.x we used the Astaro Authentication Agent for web filtering. Even after upgrading to 9.x we continue to use the AAA, but want to look at implementing AD SSO Authentication.

Our ASG120 has a FQDN of vpn.domain.com and an internal nslookup reports vpn.domain.local

I have followed the steps listed in the whitepaper, but cannot get the SSO to authenticate.

How can I troubleshoot where it is failing?

Currently we are on release 9.201-23

Thanks for the assistance.

This thread was automatically locked due to age.

Parents

0 BAlfson over 11 years ago

lbiw, although Configuring HTTP/HTTPS proxy access with AD SSO with a Sophos UTM hasn't been updated for the change in the web interface, the principles are all the same. The document is written for Standard mode. I would have the default policy in Transparent mode and no authentication. If a user doesn't authenticate, a stricter "Guest" policy is applied.

Did that help you find your error?

Cheers - Bob

Sophos UTM Community Moderator
Sophos Certified Architect - UTM
Sophos Certified Engineer - XG
Gold Solution Partner since 2005

MediaSoft, Inc. USA
Cancel
Vote Up 0 Vote Down

Cancel

Reply

0 BAlfson over 11 years ago

lbiw, although Configuring HTTP/HTTPS proxy access with AD SSO with a Sophos UTM hasn't been updated for the change in the web interface, the principles are all the same. The document is written for Standard mode. I would have the default policy in Transparent mode and no authentication. If a user doesn't authenticate, a stricter "Guest" policy is applied.

Did that help you find your error?

Cheers - Bob

Sophos UTM Community Moderator
Sophos Certified Architect - UTM
Sophos Certified Engineer - XG
Gold Solution Partner since 2005

MediaSoft, Inc. USA
Cancel
Vote Up 0 Vote Down

Cancel

Children

No Data