server name parses as Server certificates with domain spaces, e.g. "RADIUS name Service of Foo University" are to be problematic with some supplicants. server name Subject/CN == Some supplicants only SubjectAltName:DNS consult the CN when checking the name of an incoming server certificate; some either of the two; some will only check SubjectAltName:DNS. Keeping the desired name in both fields in sync is a safe bet for . Only use one CN. If you have multiple RADIUS servers, either use the same certificate for all of them is no need for the name to match the DNS name of the machine it is running on), or generate multiple certificates, each with CN/subjectAltName:DNS. server name not a wildcard name Some supplicants exhibit ( "*.someidp.tld") behaviour when attempting to parse incoming certificates with a wildcard.
server name parses as domain name Server certificates with spaces, e.g. "RADIUS Service of Foo University" are to be problematic with some supplicants. server name Subject/CN == SubjectAltName:DNS Some supplicants only consult the CN when checking the name of an incoming server certificate; some either of the two; some will only check SubjectAltName:DNS. Keeping the desired name in both fields in sync is a safe bet for . Only use one CN. If you have multiple RADIUS servers, either use the same certificate for all of them is no need for the name to match the DNS name of the machine it is running on), or generate multiple certificates, each with CN/subjectAltName:DNS. server name not a wildcard name ( "*.someidp.tld") Some supplicants exhibit behaviour when attempting to parse incoming certificates with a wildcard.
InstitutionalEduroamImplentationPlan_1.0.docx