Adfs Ssl Certificate Does Not Contain All Upn Suffix Values

You can use a wildcard certificate that covers all of the possible names used at your company or you can add the additional names as subject alternative names.
Adfs ssl certificate does not contain all upn suffix values. This command sets the list. Users with upn suffix values not represented in the certificate will not be able to workplace join their devices. To enable users with the corresponding upn suffix to register their devices provide a new ssl certificate containing the. If your company uses multiple upn suffixes then your ad fs server ssl certificate must contain an entry for each upn suffix.
Users with upn suffix values not represented in the certificate will not be able to workplace join their devices. Users with these upn suffix values will not be able to register their devices. The ssl certificate does not contain all upn suffix values that exist in the enterprise. B setup adfs and did not use upn suffix enterpriseregistrationupn suffix resolution add an additional custom upn suffix that you can use to register a device with adfs.
Upn values that are not included in the ssl certificate have been found in the enterprise. This alone will not make our 415 go away nor will it allow our friends in other forests or domains to workplace join using our sts. The ssl certificate does not contain all upn suffix values that exist in the enterprise. Set the list of upn suffixes.
You can satisfy this requirement in two ways. You can also use a wildcard ssl certificate that covers all possible registration names. My main issue is that the wildcard ssl certificate does not contain the subject alternative name of domaininternal thus i cannot use this internally and will have to rely on my ad cs certificate. Issue the ad fs certificate complete.
For example enterpriseregistrationupn suffix. Any discovered upn suffix must have a corresponding registration name in the ssl certificate for ad fs. This cmdlet does not affect the custom upn suffixes that you set manually by running the add adfsdeviceregistrationupnsuffix cmdlet. Getting back to the action we left off at updating the certificate.