18.07.2013 Views

Sidewinder G2 6.1.1 Administration Guide - Glossary of Technical ...

Sidewinder G2 6.1.1 Administration Guide - Glossary of Technical ...

Sidewinder G2 6.1.1 Administration Guide - Glossary of Technical ...

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Adding or modifying a<br />

Windows domain controller<br />

entry<br />

Configuring SSO<br />

4. In the Failed Authentication Message field, specify the message that you<br />

want to display if a user’s authentication attempt fails. The default is<br />

Login incorrect.<br />

5. Click OK to save your changes before returning to the Authentication<br />

Configuration window.<br />

Note: If you want to use Windows Domain authentication after it is configured,<br />

make sure you enable it in the Authentication Configuration window.<br />

The Domain Controller Configuration window is used to add or<br />

modify a domain controller entry. Follow the steps below.<br />

1. In the IP Address field, type the IP address used by the Windows domain<br />

controller.<br />

The Port Number field displays the port used by the Windows domain<br />

controller. The default value is 139. This field cannot be modified.<br />

2. In the Windows Domain Controller Name field, type the name <strong>of</strong> this<br />

Windows domain controller. Type only the host or computer name, not<br />

the fully qualified name. You can determine the name by selecting My<br />

Computer -> Control Panel -> Network on the Windows controller.<br />

3. Click Add to add the entry to the list <strong>of</strong> Windows domain controllers.<br />

Configuring SSO Single sign-on (SSO) works in conjunction with a specified<br />

authentication method to cache a user’s initial authentication, thereby<br />

allowing access to multiple services with a single successful<br />

authentication to the <strong>Sidewinder</strong> <strong>G2</strong>.<br />

This is done by storing the source IP address for a successful<br />

authentication in a cache. All proxy rule services that require<br />

authentication will check that cache for successful authentication. If<br />

the source IP address exists in the cache, transparent authentication<br />

based on the initial authentication takes place and the user is allowed<br />

access without manually re-authenticating.<br />

You can configure SSO to expire cached authentications after a<br />

specified time period has passed (for example, you may choose to<br />

require each user to re-authenticate every two hours). You also have<br />

the option to require a user to re-authenticate after a specified period<br />

<strong>of</strong> idle time (for example, a user must re-authenticate if the cached<br />

authentication has not been accessed for one hour or more). You also<br />

have the option to manually expire cached authentication for a<br />

specific user(s) or for all users, at any time.<br />

Setting Up Authentication 9-27

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!