Connected: An Internet Encyclopedia
RFC 1510 - 3.1.1. Generation of KRB_AS_REQ message

Top: Connected: An Internet Encyclopedia
Up: Requests For Comments
Up: RFC 1510
Up: 3. Message Exchanges
Up: 3.1. The Authentication Service Exchange
Prev: 3.1. The Authentication Service Exchange
Next: 3.1.2. Receipt of KRB_AS_REQ message

### 3.1.1. Generation of KRB_AS_REQ message

The client may specify a number of options in the initial request. Among these options are whether preauthentication is to be performed; whether the requested ticket is to be renewable, proxiable, or forwardable; whether it should be postdated or allow postdating of derivative tickets; and whether a renewable ticket will be accepted in lieu of a non-renewable ticket if the requested ticket expiration date cannot be satisfied by a nonrenewable ticket (due to configuration constraints; see section 4). See section A.1 for pseudocode.

The client prepares the KRB_AS_REQ message and sends it to the KDC.

Next: 3.1.2. Receipt of KRB_AS_REQ message

Connected: An Internet Encyclopedia
RFC 1510 - 3.1.1. Generation of KRB_AS_REQ message