2015
DOI: 10.17487/rfc7542
|View full text |Cite
|
Sign up to set email alerts
|

The Network Access Identifier

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1
1
1

Citation Types

0
21
0

Year Published

2015
2015
2022
2022

Publication Types

Select...
6
3

Relationship

0
9

Authors

Journals

citations
Cited by 21 publications
(21 citation statements)
references
References 12 publications
0
21
0
Order By: Relevance
“…In addition, common constructions such as "user@example.com" (e.g., the Network Access Identifier from [RFC7542]) are allowed as usernames under this specification, as they were under [RFC4013].…”
Section: Definitionmentioning
confidence: 99%
“…In addition, common constructions such as "user@example.com" (e.g., the Network Access Identifier from [RFC7542]) are allowed as usernames under this specification, as they were under [RFC4013].…”
Section: Definitionmentioning
confidence: 99%
“…2) The user's identity is forwarded to the RADIUS authentication server of the user's IdP through several RADIUS proxies in the federation network. The destination of the next-hop RADIUS proxy is determined by the realm [10] included in the user's identity. 3) If the RADIUS authentication server has received the authentication request including the user's identity, the server sends its server certificate back to the user's terminal.…”
Section: Overview Of Wlan Roaming Systemsmentioning
confidence: 99%
“…The RADIUS client, acting as an RP, transmits a SAML request element within a RADIUS Access-Request message. This message MUST include a single instance of the RADIUS User-Name attribute whose value MUST conform to the Network Access Identifier [RFC7542] scheme. The RP MUST NOT include more than one SAML request element.…”
Section: Operationmentioning
confidence: 99%
“…Indicates that the content of the element is in the form of a Network Access Identifier (NAI) using the syntax described by [RFC7542]. Indicates that the subject is the system entity (either the user or machine) authenticated by a previously transmitted RADIUS Access-Accept message, as identified by the value of that RADIUS message's State attribute.…”
Section: Metadata Considerationsmentioning
confidence: 99%