Mobile Apps, internal use, certificate warnings

%3CLINGO-SUB%20id%3D%22lingo-sub-80294%22%20slang%3D%22en-US%22%3EMobile%20Apps%2C%20internal%20use%2C%20certificate%20warnings%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-80294%22%20slang%3D%22en-US%22%3E%3CP%3EHi%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWe%20are%20currently%20deploying%20Skype%20for%20business%20mobile%20apps%20for%20internal%20use.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EBefore%20that%2C%20the%20use%20of%20mobile%20apps%20was%20mostly%20external.%20No%20problem...%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EBut%20it%20appears%20that%20by%20using%20applications%20internally%2C%20users%20receive%20many%20warning%20related%20to%20the%20fact%20that%20internally%2C%20certificates%20are%20signed%20by%20the%20Active%20Directory%20Certification%20Authority.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIn%20BYOD%20scenario%2C%20we%20can%20deploy%20our%20root%20CA%20to%20device%2C%20not%20a%20problem%2C%20but%20for%20some%20population%2C%20mobile%20are%20only%20used%20as%20%22mobile%20Lync%20Phone%22%2C%20and%20when%20you%20deploy%20root%20CA%20to%20android%20phones%2C%20you%20are%20required%20to%20set%20an%20unlock%20code.%26nbsp%3BThis%20is%20not%20compatible%20with%20the%20intended%20use.%26nbsp%3B%3CBR%20%2F%3E%3CBR%20%2F%3E%3C%2FP%3E%3CP%3EIs%20there%20a%20way%20to%20prevent%20this%20%3F%20After%20a%20lot%20of%20reading%20I%20have%20find%20a%20discussion%20saying%20that%20you%20have%20to%20redirect%20ALL%20https%20connections%20like%20meet.domain.com%2C%20including%20desk%20phones%2C%20windows%20clients%2C%20etc...%2C%20to%20reverse%20proxy%2C%20like%20that%20it's%20our%20public%20certicates%20that%20are%20presented%20to%20mobile.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThis%20seems%20to%20me%20completely%20absurd%20and%20at%20least%20not%20optimized%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ESo%20what%20is%20the%20good%20practice%20for%20Mobile%20Apps%20using%20internally%20with%20internal%20certs%20from%20ADCS%20%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThanks%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-80294%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EMobile%20Client%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3ESign-in%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-88591%22%20slang%3D%22en-US%22%3ERe%3A%20Mobile%20Apps%2C%20internal%20use%2C%20certificate%20warnings%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-88591%22%20slang%3D%22en-US%22%3E%3CP%3EHi%2C%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3Esorry%20I%20was%20out%20of%20office.%3C%2FP%3E%3CP%3Efor%20sure%20it's%20possible%20to%20replace%20all%20certs%20with%20public%20certs...But%20it's%20not%20without%20cost...%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-84220%22%20slang%3D%22en-US%22%3ERe%3A%20Mobile%20Apps%2C%20internal%20use%2C%20certificate%20warnings%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-84220%22%20slang%3D%22en-US%22%3E%3CP%3EPlease%20let%20me%20know%20if%20you%20wanna%20know%20how%20it%20should%20be%20done.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-84219%22%20slang%3D%22en-US%22%3ERe%3A%20Mobile%20Apps%2C%20internal%20use%2C%20certificate%20warnings%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-84219%22%20slang%3D%22en-US%22%3E%3CP%3EYes%2C%20possible%20and%20done%20that.%20And%20some%20organization%20who%20prefer%20to%20use%20Public%20cert%20for%20all%20secure%20communication%20over%20internal%20cert.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20%26nbsp%3Bhad%20configured%20and%20deployed%20public%20SSL%20certificates%20for%20Frontend%2C%20Oauth%2C%20RP%2C%20and%20Edge%20for%20a%20few%20customers%20and%20working%20perfect.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-82463%22%20slang%3D%22en-US%22%3ERe%3A%20Mobile%20Apps%2C%20internal%20use%2C%20certificate%20warnings%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-82463%22%20slang%3D%22en-US%22%3E%3CP%3EIs%20it%20possible%20to%20purchase%20public%20certs%20for%20the%20internal%20SfB%20Infrastructure%3F%3C%2FP%3E%0A%3CP%3EThis%20is%20really%20the%20best%20route%20to%20take%20and%20will%20eliminate%20a%20lot%20of%20headaches%20if%20you%20want%20to%20provide%20the%20full%20feature-set%20for%26nbsp%3BBYOD%20SfB%20Mobile%20clients%20that%20are%20on%20your%20internal%20network.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-81468%22%20slang%3D%22en-US%22%3ERe%3A%20Mobile%20Apps%2C%20internal%20use%2C%20certificate%20warnings%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-81468%22%20slang%3D%22en-US%22%3E%3CP%3Eit%20seems%20that%20we%20receive%20first%20an%20answer%20for%20lyncdiscoverinternal.domain.com%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSTRONG%3E06-23%2007%3A31%3A55.391%3C%2FSTRONG%3E%209235%20INFO%20APPLICATION%20CUcwaAutoDiscoveryGetUserUrlOperation.cpp%3A412%20CUcwaAutoDiscoverGetUserUrlOperation%3A%3AonEvent%20received.%20%26nbsp%3BStatus%20%3D%20S_OK%20(S0-0-0)%2C%20url%20%3D%20%3CA%20href%3D%22http%3A%2F%2Flyncdiscoverinternal.domain.com%2F%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttp%3A%2F%2Flyncdiscoverinternal.domain.com%2F%3C%2FA%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3Ethen%20after%20from%20lyncdiscover.domain.com%3C%2FP%3E%3CP%3E%3CSTRONG%3E06-23%2007%3A31%3A55.525%3C%2FSTRONG%3E%209235%20INFO%20APPLICATION%20CUcwaAutoDiscoveryGetUserUrlOperation.cpp%3A412%20CUcwaAutoDiscoverGetUserUrlOperation%3A%3AonEvent%20received.%20%26nbsp%3BStatus%20%3D%20S_OK%20(S0-0-0)%2C%20url%20%3D%20%3CA%20href%3D%22http%3A%2F%2Flyncdiscover.domain.com%2F%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttp%3A%2F%2Flyncdiscover.domain.com%2F%3C%2FA%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-81465%22%20slang%3D%22en-US%22%3ERe%3A%20Mobile%20Apps%2C%20internal%20use%2C%20certificate%20warnings%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-81465%22%20slang%3D%22en-US%22%3E%3CP%3EBut%20it's%20%22normal%22%20if%20it%20try%20to%20connect%20to%20%3CA%20href%3D%22https%3A%2F%2Flyncdiscoverinternal.domain.com%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Flyncdiscoverinternal.domain.com%3C%2FA%3E%2C%20it%20will%20get%20certificate%20warning.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3Ewhat%20I%20don't%20understand%20is%20why%20is%20it%20trying%20to%20connect%20to%20this%20internal%20url%20if%20mobile%20phone%20use%20external%20connection%20first...%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWhen%20I%20look%20for%20the%20log%2C%20first%20connection%20are%20going%20to%20lyncdiscover.domain.com...But%20why%20after%20that%20it%20try%20lyncdiscoverinternal.domain.com%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-81458%22%20slang%3D%22en-US%22%3ERe%3A%20Mobile%20Apps%2C%20internal%20use%2C%20certificate%20warnings%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-81458%22%20slang%3D%22en-US%22%3E%3CP%3Ecertificate%20warning%20%3A(%3C%2Fimg%3E%3C%2FP%3E%3CP%3Eprompt%20for%20an%20internal%20cert%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-81442%22%20slang%3D%22en-US%22%3ERe%3A%20Mobile%20Apps%2C%20internal%20use%2C%20certificate%20warnings%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-81442%22%20slang%3D%22en-US%22%3E%3CP%3ESounds%20perfect.%20What%20happens%20when%20you%20try%20to%20login%20the%20client%20from%20the%20mobile%20device%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-81077%22%20slang%3D%22en-US%22%3ERe%3A%20Mobile%20Apps%2C%20internal%20use%2C%20certificate%20warnings%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-81077%22%20slang%3D%22en-US%22%3E%3CP%3ESo%20I%20just%20do%20the%20test.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EFrom%20my%20mobile%2C%20on%20corporate%20wifi%2C%20if%20I%20go%20with%20the%20browser%20to%20%3A%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Fpools4bpriws.domain.com%2FAutodiscover%2FAutodiscoverService.svc%2Froot%2Fuser%3ForiginalDomain%3Ddomain.com%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fpools4bpriws.domain.com%2FAutodiscover%2FAutodiscoverService.svc%2Froot%2Fuser%3ForiginalDomain%3Ddomain%3C%2FA%3E.com%2C%20I%20have%20an%20error%20401%20unauthorized%2C%20with%20the%20public%20cert%20from%20globasign...%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-80925%22%20slang%3D%22en-US%22%3ERe%3A%20Mobile%20Apps%2C%20internal%20use%2C%20certificate%20warnings%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-80925%22%20slang%3D%22en-US%22%3E%3CP%3Epools4bpriws.domain.com%20is%20pointing%20to%20public%20ip%20of%20the%20reverse%20proxy%20(internally%20and%20externally)%26nbsp%3B%3C%2FP%3E%3CP%3Epools4bpriws.domain.local%20is%20pointing%20to%20frontend%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3Eso%20I%20don't%20unterstand%20why%20I've%20got%20this%20internal%20cert%3C%2FP%3E%3CP%3EI%20have%20just%20verified%20and%20from%20an%20internal%20computer%20with%20IE%2C%20if%20I%20go%20to%20the%20URL%20I%20receive%20the%20public%20cert%20from%20globalsign...I%20can't%20verify%20from%20home%20in%20the%20Wifi%20vlan%20but%20it%20should%20be%20the%20same...I%20will%20verify%20tomorrow%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CEM%3ESo%2C%20in%20your%20topology%2C%20what's%20the%20FQDN%20of%20your%20external%20webserviceS%3F%3C%2FEM%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3Epools4bpriws.domain.com%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-80850%22%20slang%3D%22en-US%22%3ERe%3A%20Mobile%20Apps%2C%20internal%20use%2C%20certificate%20warnings%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-80850%22%20slang%3D%22en-US%22%3EAre%20you%20pointing%20DNS%20(internal)%20to%20internal%20DMZ%20address%20or%20external%20IP%3F%3CBR%20%2F%3ELike%20Ivan%20is%20asking%2C%20what's%20the%20external%20webservices%20FQDN%3F%3CBR%20%2F%3E%3CBR%20%2F%3E%3CBR%20%2F%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-80697%22%20slang%3D%22en-US%22%3ERe%3A%20Mobile%20Apps%2C%20internal%20use%2C%20certificate%20warnings%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-80697%22%20slang%3D%22en-US%22%3E%3CP%3ESo%20you%20are%20failing%20here%3A%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E06-21%2014%3A56%3A27.853%2014597%20INFO%20TRANSPORT%20CUcwaAutoDiscoveryResponse.cpp%3A116%20location%20value%20is%20external%3CBR%20%2F%3E06-21%2014%3A56%3A27.854%2014597%20INFO%20TRANSPORT%20CUcwaAutoDiscoveryResponse.cpp%3A190%20User%20url%20is%20%3CA%20href%3D%22https%3A%2F%2Fpools4bpriws.domain.com%2FAutodiscover%2FAutodiscoverService.svc%2Froot%2Fuser%3ForiginalDomain%3Ddomain.com%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fpools4bpriws.domain.com%2FAutodiscover%2FAutodiscoverService.svc%2Froot%2Fuser%3ForiginalDomain%3Ddomain.com%3C%2FA%3E%3C%2FP%3E%0A%3CP%3E%3D%3D%3D%3C%2FP%3E%0A%3CP%3E06-21%2014%3A56%3A28.547%2014597%20DEBUG%20%5BHttp%5D%20CertificateDialog%3A%20Showing%20certificate%20dialog%20for%20UserCertificateApprovalRequest%20%7B%20mRequestId%20%3D%20edf8ca96-309a-43fe-afc7-59a84adc5fe2%2C%20mTrigger%20%3D%20UntrustedCertificate%2C%20mCertificateInfo%20%3D%20X509CertificateInfo%20%7B%20Issuer%20%3D%20DOMAIN-CA%2C%20Subject%20%3D%20pools4bpri.domain.local%2C%20SigAlgName%20%3D%20SHA1withRSA%2C%20NotBefore%20%3D%2002%20nov.%202015%2002%3A11%3A47%20PM%2C%20NotAfter%20%3D%2001%20nov.%202017%2002%3A11%3A47%20PM%2C%20SerialNumber%20%3D%20758225337598940103081203869516454363911946403%20%7D%2C%20mTrustModel%20%3D%20null%20%7D%3D%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3D%3D%3D%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3ESo%2C%20in%20your%20topology%2C%20what's%20the%20FQDN%20of%20your%20external%20webserviceS%3F%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-80687%22%20slang%3D%22en-US%22%3ERe%3A%20Mobile%20Apps%2C%20internal%20use%2C%20certificate%20warnings%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-80687%22%20slang%3D%22en-US%22%3E%3CP%3Eactually%20they%20do%20query%20it%20just%20that%20we%20redirect%20to%20UCWA%20external.%20THat's%20all.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-80646%22%20slang%3D%22en-US%22%3ERe%3A%20Mobile%20Apps%2C%20internal%20use%2C%20certificate%20warnings%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-80646%22%20slang%3D%22en-US%22%3E%3CP%3EI%20attach%20you%20the%20log%20if%20you%20see%20something..%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3Edomain.com%20replace%20our%20public%20domain%20name%3C%2FP%3E%3CP%3Edomain.local%20replace%20our%20internal%20domain%20name%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-80618%22%20slang%3D%22en-US%22%3ERe%3A%20Mobile%20Apps%2C%20internal%20use%2C%20certificate%20warnings%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-80618%22%20slang%3D%22en-US%22%3EIf%20HTTPS%20is%20configured%20correctly%20it%20will%20hit%20the%20first%20try.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-80600%22%20slang%3D%22en-US%22%3ERe%3A%20Mobile%20Apps%2C%20internal%20use%2C%20certificate%20warnings%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-80600%22%20slang%3D%22en-US%22%3E%3CP%3Enot%20better%20...%3C%2FP%3E%3CP%3EI%20see%20in%20the%20log%20that%20it%20try%20to%20contact%20%3CA%20href%3D%22https%3A%2F%2Flyncdiscover.domain.com%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Flyncdiscover.domain.com%3C%2FA%3E%20then%20he%20try%20to%20contact%20%3CA%20href%3D%22http%3A%2F%2Flyncdiscover.domain.com%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttp%3A%2F%2Flyncdiscover.domain.com%3C%2FA%3E%20(not%20allowed%2C%20only%20https)%20then%20%3CA%20href%3D%22https%3A%2F%2Flyncdiscoverinternal.domain.com%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Flyncdiscoverinternal.domain.com%3C%2FA%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EDoes%20I%20have%20to%20open%20http%20%3F%20I%20have%20read%20in%20microsoft%20document%20that%20it%20is%20not%20recommended%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-80580%22%20slang%3D%22en-US%22%3ERe%3A%20Mobile%20Apps%2C%20internal%20use%2C%20certificate%20warnings%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-80580%22%20slang%3D%22en-US%22%3ECorrect%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-80577%22%20slang%3D%22en-US%22%3ERe%3A%20Mobile%20Apps%2C%20internal%20use%2C%20certificate%20warnings%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-80577%22%20slang%3D%22en-US%22%3ELike%20mentioned%20above%20pc%20client%20is%20using%20lyncdiscoverinternal%20first%20then%20lyncdiscover.%20Mobile%20clients%20use%20lyncdiscover.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-80575%22%20slang%3D%22en-US%22%3ERe%3A%20Mobile%20Apps%2C%20internal%20use%2C%20certificate%20warnings%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-80575%22%20slang%3D%22en-US%22%3E%3CBLOCKQUOTE%3E%3CHR%20%2F%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F34020%22%20target%3D%22_blank%22%3E%40Erwin%20Bierens%3C%2FA%3E%20wrote%3A%3CBR%20%2F%3EMobile%20devices%20are%20not%20checking%20lyncdiscoverinternal.%20First%20check%20on%20mobile%20devices%20is%20lyncdiscover.%3CBR%20%2F%3E%3CBR%20%2F%3E%3CHR%20%2F%3E%3C%2FBLOCKQUOTE%3E%3CP%3ESo%20I%20will%20create%20it.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3Ebut%20no%20impact%20on%20windows%20clients%20and%20desk%20phones%20%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-80574%22%20slang%3D%22en-US%22%3ERe%3A%20Mobile%20Apps%2C%20internal%20use%2C%20certificate%20warnings%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-80574%22%20slang%3D%22en-US%22%3E%3CP%3EI%20just%20sent%20me%20the%20log%20from%20the%20device%20mobile.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIt%20seems%20that%20it%20first%20try%20to%20connect%20to%20lyncdiscover.domain.com%2C%20failed%20because%20DNS%20entry%20doesn't%20exist%20(Exception%20UnknownHostException%20caught%20while%20executing%20http%20request%20Get%20%3CA%20href%3D%22http%3A%2F%2Flyncdiscover.domain.com%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttp%3A%2F%2Flyncdiscover.domain.com%3C%2FA%3E)%20and%20then%20try%20to%20connect%20to%20%3CA%20href%3D%22https%3A%2F%2Flyncdiscoverinternal.domain.com%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Flyncdiscoverinternal.domain.com%3C%2FA%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EBut%20it's%20strange%20because%20for%20me%20it's%20the%20opposite%20of%20what%20I%20read%20before%20(first%20lyncdiscoverinternal%20then%20lyncdiscover)%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-80573%22%20slang%3D%22en-US%22%3ERe%3A%20Mobile%20Apps%2C%20internal%20use%2C%20certificate%20warnings%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-80573%22%20slang%3D%22en-US%22%3EMobile%20devices%20are%20not%20checking%20lyncdiscoverinternal.%20First%20check%20on%20mobile%20devices%20is%20lyncdiscover.%3CBR%20%2F%3E%3CBR%20%2F%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-80570%22%20slang%3D%22en-US%22%3ERe%3A%20Mobile%20Apps%2C%20internal%20use%2C%20certificate%20warnings%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-80570%22%20slang%3D%22en-US%22%3E%3CP%3EIs%20that%20internally%20a%20DNS%20record%20lyncdiscover.domain.com%20must%20exist%20and%20point%20to%20the%20reverse%20proxy%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-80563%22%20slang%3D%22en-US%22%3ERe%3A%20Mobile%20Apps%2C%20internal%20use%2C%20certificate%20warnings%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-80563%22%20slang%3D%22en-US%22%3E%3CBLOCKQUOTE%3E%3CHR%20%2F%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F34020%22%20target%3D%22_blank%22%3E%40Erwin%20Bierens%3C%2FA%3E%20wrote%3A%3CBR%20%2F%3EMobile%20devices%20don't%20connect%20to%20internal%20Autodiscover%20Service%20(will%20use%20internal%20certicate).%20This%20is%20only%20used%20for%20Desktop%20Client.%20Like%20Ivan%20mentioned%20UCWA%20request%20will%20land%20on%20Reverse%20proxy%20and%20will%20be%20forwarded%20to%20Skype%20external%20web%20services%20url(public%20certificate%20which%20the%20mobile%20phone%20can%20check)%2C%20this%20one%20is%20using%20port%208080%20and%204443%20(in%20default%20configuration).%3CBR%20%2F%3E%3CBR%20%2F%3E%3CHR%20%2F%3E%3C%2FBLOCKQUOTE%3E%3CP%3EIf%20mobile%20device%20use%20lyncdiscoverinternal%20dns%2C%20then%20it%20will%20connect%20internally%20first%20%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-80561%22%20slang%3D%22en-US%22%3ERe%3A%20Mobile%20Apps%2C%20internal%20use%2C%20certificate%20warnings%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-80561%22%20slang%3D%22en-US%22%3E%3CP%3EIf%20he%20did%20that%2C%20he%20would%20not%20show%20me%20any%20private%20certificates%20and%20I%20would%20not%20have%20warning%3A%20D%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-80540%22%20slang%3D%22en-US%22%3ERe%3A%20Mobile%20Apps%2C%20internal%20use%2C%20certificate%20warnings%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-80540%22%20slang%3D%22en-US%22%3EMobile%20devices%20don't%20connect%20to%20internal%20Autodiscover%20Service%20(will%20use%20internal%20certicate).%20This%20is%20only%20used%20for%20Desktop%20Client.%20Like%20Ivan%20mentioned%20UCWA%20request%20will%20land%20on%20Reverse%20proxy%20and%20will%20be%20forwarded%20to%20Skype%20external%20web%20services%20url(public%20certificate%20which%20the%20mobile%20phone%20can%20check)%2C%20this%20one%20is%20using%20port%208080%20and%204443%20(in%20default%20configuration).%3CBR%20%2F%3E%3CBR%20%2F%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-80526%22%20slang%3D%22en-US%22%3ERe%3A%20Mobile%20Apps%2C%20internal%20use%2C%20certificate%20warnings%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-80526%22%20slang%3D%22en-US%22%3E%3CP%3EYou%20won't%2C%20as%20the%20described%20in%20the%20article%20mobility%20is%20always%20hairpinned%20over%20the%20reverse%20proxy.%26nbsp%3B%3C%2FP%3E%0A%3CP%3Econsult%20here%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EThe%20UCWA%20request%20will%20land%20on%20your%20RP%20and%20redirect%20to%20external%20web%20fqdn.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-80520%22%20slang%3D%22en-US%22%3ERe%3A%20Mobile%20Apps%2C%20internal%20use%2C%20certificate%20warnings%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-80520%22%20slang%3D%22en-US%22%3E%3CP%3E%3CU%3EHi%20Erwin%2C%3C%2FU%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CU%3Ecurrently%20I%20don't%20have%20lyncdiscover.xxxx%20record%20on%20our%20internal%20DNS.%3C%2FU%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CU%3EBut%20it's%20not%20what%20I%20understand%20here%20%3A%3C%2FU%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CU%3E%3CSPAN%3EWhen%20you%20use%20Automatic%20Discovery%2C%20mobile%20devices%20use%20DNS%20to%20locate%20resources.%20During%20the%20DNS%20lookup%2C%20a%20connection%20is%20first%20attempted%20to%20the%20FQDN%20that%20is%20associated%20with%20the%20internal%20DNS%20record%20(lyncdiscoverinternal.%3CINTERNAL%20domain%3D%22%22%20name%3D%22%22%3E).%20If%20a%20connection%20cannot%20be%20made%20by%20using%20the%20internal%20DNS%20record%2C%20a%20connection%20is%20attempted%20by%20using%20the%20external%20DNS%20record%20(lyncdiscover.%3CSIPDOMAIN%3E).%20A%20mobile%20device%20that%20is%20internal%20to%20the%20network%20connects%20to%20the%20internal%20Autodiscover%20Service%20URL%2C%20and%20a%20mobile%20device%20that%20is%20external%20to%20the%20network%20connects%20to%20the%20external%20Autodiscover%20Service%20URL.%20External%20Autodiscover%20requests%20go%20through%20the%20reverse%20proxy.%20The%20Lync%20Server%202013%20Autodiscover%20Service%20returns%20all%20Web%20Services%20URLs%20for%20the%20user's%20home%20pool%2C%20including%20the%20Mobility%20Service%20(Mcx%20and%20UCWA)%20URLs.%20However%2C%20both%20the%20internal%20Mobility%20Service%20URL%20and%20the%20external%20Mobility%20Service%20URL%20are%20associated%20with%20the%20external%20Web%20Services%20FQDN.%20Therefore%2C%20regardless%20of%20whether%20a%20mobile%20device%20is%20internal%20or%20external%20to%20the%20network%2C%20the%20device%20always%20connects%20to%20the%20Lync%20Server%202013%20Mobility%20Service%20externally%20through%20the%20reverse%20proxy.%3C%2FSIPDOMAIN%3E%3C%2FINTERNAL%3E%3C%2FSPAN%3E%3C%2FU%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3EFor%20me%2C%20it%20tries%20first%20to%20lyncdiscoverinternal%2C%20and%20as%20soon%20it%20will%20find%20it%2C%20it%20will%20connect%20to%20it.%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%3CSPAN%3EAfter%20it%20should%20use%20external%20web%20url.%20but%20if%20it%20uses%20another%20url%2C%20like%20meet.domain.com%2C%20etc%2C%20internal%20DNS%20will%20always%20send%20it%20to%20front%20end%20server%2C%20and%20we%20will%20have%20problem%20with%20certificates.%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-80469%22%20slang%3D%22en-US%22%3ERe%3A%20Mobile%20Apps%2C%20internal%20use%2C%20certificate%20warnings%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-80469%22%20slang%3D%22en-US%22%3EHi%20Benoit%2C%3CBR%20%2F%3EMobile%20apps%20are%20using%20the%20dns%20records%20lyncdiscover.domain.com%20for%20login%20in.%3CBR%20%2F%3EDesktop%20clients%20are%20using%20in%20first%20case%20lyncdiscoverinternal.domain.com.%3CBR%20%2F%3E%3CBR%20%2F%3ERecommendation%20is%20to%20point%20A%20record%20lyncdiscoverinternal.domain.com%20to%20front%20end%20server%2Fpool.%20lyncdiscover.domain.com%20A%20record%20should%20point%20to%20the%20reverse%20proxy%2C%20in%20this%20case%20the%20external%20webservices%20url%20will%20be%20used%20(port%20translation%2080%2C443%20to%208080%204443).%3CBR%20%2F%3E%3CBR%20%2F%3EThere%20is%20documentation%20on%20technet%20about%20how%20mobility%20needs%20to%20be%20configured.%3CBR%20%2F%3Elink%3A%20%3CA%20href%3D%22https%3A%2F%2Ftechnet.microsoft.com%2Fen-us%2Flibrary%2Fhh690030(v%3Docs.15).aspx%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Ftechnet.microsoft.com%2Fen-us%2Flibrary%2Fhh690030(v%3Docs.15).aspx%3C%2FA%3E%3C%2FLINGO-BODY%3E
Occasional Contributor

Hi,

 

We are currently deploying Skype for business mobile apps for internal use.

 

Before that, the use of mobile apps was mostly external. No problem...

 

But it appears that by using applications internally, users receive many warning related to the fact that internally, certificates are signed by the Active Directory Certification Authority.

 

In BYOD scenario, we can deploy our root CA to device, not a problem, but for some population, mobile are only used as "mobile Lync Phone", and when you deploy root CA to android phones, you are required to set an unlock code. This is not compatible with the intended use. 

Is there a way to prevent this ? After a lot of reading I have find a discussion saying that you have to redirect ALL https connections like meet.domain.com, including desk phones, windows clients, etc..., to reverse proxy, like that it's our public certicates that are presented to mobile.

 

This seems to me completely absurd and at least not optimized

 

So what is the good practice for Mobile Apps using internally with internal certs from ADCS ?

 

Thanks

28 Replies
Hi Benoit,
Mobile apps are using the dns records lyncdiscover.domain.com for login in.
Desktop clients are using in first case lyncdiscoverinternal.domain.com.

Recommendation is to point A record lyncdiscoverinternal.domain.com to front end server/pool. lyncdiscover.domain.com A record should point to the reverse proxy, in this case the external webservices url will be used (port translation 80,443 to 8080 4443).

There is documentation on technet about how mobility needs to be configured.
link: https://technet.microsoft.com/en-us/library/hh690030(v=ocs.15).aspx

Hi Erwin,

 

currently I don't have lyncdiscover.xxxx record on our internal DNS.

 

But it's not what I understand here :

 

When you use Automatic Discovery, mobile devices use DNS to locate resources. During the DNS lookup, a connection is first attempted to the FQDN that is associated with the internal DNS record (lyncdiscoverinternal.<internal domain name>). If a connection cannot be made by using the internal DNS record, a connection is attempted by using the external DNS record (lyncdiscover.<sipdomain>). A mobile device that is internal to the network connects to the internal Autodiscover Service URL, and a mobile device that is external to the network connects to the external Autodiscover Service URL. External Autodiscover requests go through the reverse proxy. The Lync Server 2013 Autodiscover Service returns all Web Services URLs for the user's home pool, including the Mobility Service (Mcx and UCWA) URLs. However, both the internal Mobility Service URL and the external Mobility Service URL are associated with the external Web Services FQDN. Therefore, regardless of whether a mobile device is internal or external to the network, the device always connects to the Lync Server 2013 Mobility Service externally through the reverse proxy.

 

For me, it tries first to lyncdiscoverinternal, and as soon it will find it, it will connect to it.

After it should use external web url. but if it uses another url, like meet.domain.com, etc, internal DNS will always send it to front end server, and we will have problem with certificates.

 

You won't, as the described in the article mobility is always hairpinned over the reverse proxy. 

consult here

 

The UCWA request will land on your RP and redirect to external web fqdn. 

Mobile devices don't connect to internal Autodiscover Service (will use internal certicate). This is only used for Desktop Client. Like Ivan mentioned UCWA request will land on Reverse proxy and will be forwarded to Skype external web services url(public certificate which the mobile phone can check), this one is using port 8080 and 4443 (in default configuration).

If he did that, he would not show me any private certificates and I would not have warning: D

 

 


@Erwin Bierens wrote:
Mobile devices don't connect to internal Autodiscover Service (will use internal certicate). This is only used for Desktop Client. Like Ivan mentioned UCWA request will land on Reverse proxy and will be forwarded to Skype external web services url(public certificate which the mobile phone can check), this one is using port 8080 and 4443 (in default configuration).


If mobile device use lyncdiscoverinternal dns, then it will connect internally first ?

Is that internally a DNS record lyncdiscover.domain.com must exist and point to the reverse proxy?

Mobile devices are not checking lyncdiscoverinternal. First check on mobile devices is lyncdiscover.

I just sent me the log from the device mobile.

 

It seems that it first try to connect to lyncdiscover.domain.com, failed because DNS entry doesn't exist (Exception UnknownHostException caught while executing http request Get http://lyncdiscover.domain.com) and then try to connect to https://lyncdiscoverinternal.domain.com

 

But it's strange because for me it's the opposite of what I read before (first lyncdiscoverinternal then lyncdiscover)

 

 


@Erwin Bierens wrote:
Mobile devices are not checking lyncdiscoverinternal. First check on mobile devices is lyncdiscover.


So I will create it.

 

but no impact on windows clients and desk phones ?

Like mentioned above pc client is using lyncdiscoverinternal first then lyncdiscover. Mobile clients use lyncdiscover.

not better ...

I see in the log that it try to contact https://lyncdiscover.domain.com then he try to contact http://lyncdiscover.domain.com (not allowed, only https) then https://lyncdiscoverinternal.domain.com

 

Does I have to open http ? I have read in microsoft document that it is not recommended

If HTTPS is configured correctly it will hit the first try.

I attach you the log if you see something..

 

domain.com replace our public domain name

domain.local replace our internal domain name

actually they do query it just that we redirect to UCWA external. THat's all.

So you are failing here:

 

06-21 14:56:27.853 14597 INFO TRANSPORT CUcwaAutoDiscoveryResponse.cpp:116 location value is external
06-21 14:56:27.854 14597 INFO TRANSPORT CUcwaAutoDiscoveryResponse.cpp:190 User url is https://pools4bpriws.domain.com/Autodiscover/AutodiscoverService.svc/root/user?originalDomain=domain...

===

06-21 14:56:28.547 14597 DEBUG [Http] CertificateDialog: Showing certificate dialog for UserCertificateApprovalRequest { mRequestId = edf8ca96-309a-43fe-afc7-59a84adc5fe2, mTrigger = UntrustedCertificate, mCertificateInfo = X509CertificateInfo { Issuer = DOMAIN-CA, Subject = pools4bpri.domain.local, SigAlgName = SHA1withRSA, NotBefore = 02 nov. 2015 02:11:47 PM, NotAfter = 01 nov. 2017 02:11:47 PM, SerialNumber = 758225337598940103081203869516454363911946403 }, mTrustModel = null }=

 

===

 

So, in your topology, what's the FQDN of your external webserviceS?

 

Are you pointing DNS (internal) to internal DMZ address or external IP?
Like Ivan is asking, what's the external webservices FQDN?


pools4bpriws.domain.com is pointing to public ip of the reverse proxy (internally and externally) 

pools4bpriws.domain.local is pointing to frontend

 

so I don't unterstand why I've got this internal cert

I have just verified and from an internal computer with IE, if I go to the URL I receive the public cert from globalsign...I can't verify from home in the Wifi vlan but it should be the same...I will verify tomorrow

 

So, in your topology, what's the FQDN of your external webserviceS?

 

pools4bpriws.domain.com