radiusd.conf: Why extra "Auth-Type" in authenticate section?

[Martin Gadbois]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi,

- From a typical radiusd.conf:

authenticate {
	Auth-Type PAP {
		pap
	}
... snip ...

	eap
}

Why the "Auth-Type PAP { }" construct? I tried RTFM and RTFC, but I have
not seen an actual description of why that is there. From the
"authenticate" radiusd.conf documentation:

#  Note that it does NOT mean 'try each module in order'.  It means
#  that a module from the 'authorize' section adds a configuration
#  attribute 'Auth-Type := FOO'.  That authentication type is then
#  used to pick the apropriate module from the list below.


So why specify "Auth-Type PAP { pap }" at all if the system will select
authentication 'pap' when Auth-Type == PAP?

Thanks,

- --
==============         +----------------------------------------------+
Martin Gadbois         | "Windows might take you from 0 to 60 faster, |
S/W Developer          |  but to go to 100 you need Unix."            |
Colubris Networks Inc. +----------------------------------------------+
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFFbIvs9Y3/iTTCEDkRAqf0AJ9Phxbej5KtfSVULJwtCnmMV1GbjACeJbGO
aDtM2jrSJ+rO5zgGLbrJu5U=
=q6pD
-----END PGP SIGNATURE-----