CoA: различия между версиями
Материал из noname.com.ua
Перейти к навигацииПерейти к поискуSirmax (обсуждение | вклад) |
Sirmax (обсуждение | вклад) |
||
| Строка 1: | Строка 1: | ||
=CoA - Change Of Authorization= |
=CoA - Change Of Authorization= |
||
==Назначение CoA== |
==Назначение CoA== |
||
| − | Цитата: ([http://www.ciscosystems.com/en/US/docs/ios/12_2sb/isg/coa/guide/isgcoa3.html |
+ | Цитата: ([http://www.ciscosystems.com/en/US/docs/ios/12_2sb/isg/coa/guide/isgcoa3.html cisco.com])<BR> |
ISG offers a standard RADIUS interface that is typically used in a pulled model where the request originates from ISG and the response come from the queried servers. ISG also supports the RADIUS Change of Authorization (CoA) extensions defined in RFC 3576 that are typically used in a pushed model and allow for the dynamic reconfiguring of services from external authentication, authorization, and accounting (AAA) or policy servers. |
ISG offers a standard RADIUS interface that is typically used in a pulled model where the request originates from ISG and the response come from the queried servers. ISG also supports the RADIUS Change of Authorization (CoA) extensions defined in RFC 3576 that are typically used in a pushed model and allow for the dynamic reconfiguring of services from external authentication, authorization, and accounting (AAA) or policy servers. |
||
Версия 12:12, 12 января 2009
CoA - Change Of Authorization
Назначение CoA
Цитата: (cisco.com)
ISG offers a standard RADIUS interface that is typically used in a pulled model where the request originates from ISG and the response come from the queried servers. ISG also supports the RADIUS Change of Authorization (CoA) extensions defined in RFC 3576 that are typically used in a pushed model and allow for the dynamic reconfiguring of services from external authentication, authorization, and accounting (AAA) or policy servers.
