Authentication

                                                                                                       

Features

User

Client

Session

Transparent

Yes

No Telnet Port 259 or HTTP Port 900

Yes

Connection Services

FTP, HTTP, HTTPS, Telnet, RLOGIN

All Services

All Services

Software

Password through Clients GUI

None

Authentication Agent Software required by Client

User Authentication

Transparent user authentication Firewall–1’s default and the user must provide:

Client Authentication

Session Authentication

  

Implicit Client Authentication

Extends access privileges to specific clients without requiring the user to initiate additional sessions on the gateway.

If the client authenticates under a user or session authentication rule, Firewall–1 knows which user is on the client and additional client authentication sessions are not necessary.

If implicit Client authentication is enabled and automatic sign-on rule is opened, all the standard sign-on rules are opened. Define the rules in the following order:

1st time user and session rules are applied

2nd time client authentication rules are applied

User authentication rules are always applied for HTTP preventing the browser from sending authentication password to the HTTP server as client authentication rules DO NOT use Firewall–1 security servers.

Internal Authentication Schemes

External Authentication Schemes

Use generic user’s account for external authentication schemes to avoid overhead of maintaining duplicate user accounts.

 

                                                                                  Back     Home