SOLVED

Exchange 2016 OWA - reCAPTCHA

%3CLINGO-SUB%20id%3D%22lingo-sub-1485446%22%20slang%3D%22en-US%22%3EExchange%202016%20OWA%20-%20reCAPTCHA%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1485446%22%20slang%3D%22en-US%22%3E%3CP%3EI'm%20trying%20to%20implement%20reCAPTCHA%20on%20my%20Exchange%202016%20OWA%20and%20ECP%20login%20page.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20followed%20this%20guide%20but%20I'm%20still%20unable%20to%20get%20this%20to%20work%3A%3C%2FP%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftranslate.google.com%2Ftranslate%3Fhl%3Den%26amp%3Bsl%3Dauto%26amp%3Btl%3Den%26amp%3Bu%3Dhttps%253A%252F%252Fwww.askasu.idv.tw%252Findex.php%252F2017%252F09%252F06%252F3816%252F%22%20target%3D%22_blank%22%20rel%3D%22noopener%20nofollow%20noreferrer%22%3Ehttps%3A%2F%2Ftranslate.google.com%2Ftranslate%3Fhl%3Den%26amp%3Bsl%3Dauto%26amp%3Btl%3Den%26amp%3Bu%3Dhttps%253A%252F%252Fwww.askasu.idv.tw%252Findex.php%252F2017%252F09%252F06%252F3816%252F%3C%2FA%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWhen%20I%20go%20to%20the%20login%20page%20using%20the%20DNS%20name%20(So%20using%20the%20domain%20I%20entered%20in%20reCAPTCHA)%20nothing%20shows%20up%20and%20I%20can%20login%20with%20just%20my%20username%20and%20password%20with%20no%20extra%20checks.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWhen%20I%20go%20the%20the%20IP%20address%20I%20get%20the%20error%20%22%3CSPAN%3EERROR%20for%20site%20owner%3A%3C%2FSPAN%3E%3CSPAN%3EInvalid%20domain%20for%20site%20key%3C%2FSPAN%3E%22%20which%20is%20normal%20but%20it%20shows%20that%20the%20reCAPTCHA%20is%20there.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EHas%20anybody%20else%20ever%20implement%20reCAPTCHA%20and%20give%20me%20some%20pointers%20or%20guides%20how%20they%20did%20it%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-1485446%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3E2016%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EExchange%20Server%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1491358%22%20slang%3D%22en-US%22%3ERe%3A%20Exchange%202016%20OWA%20-%20reCAPTCHA%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1491358%22%20slang%3D%22en-US%22%3EHello%20Shotterke%2C%3CBR%20%2F%3E%3CBR%20%2F%3EI%20think%20you%20are%20trying%20to%20implement%20ReCAPTCHA%20because%20of%20security%20reasons%3F%3CBR%20%2F%3E%3CBR%20%2F%3EWouldn't%20it%20be%20better%20to%20use%20Azure%20Application%20Proxy%20so%20you%20can%20use%20things%20like%20Conditional%20Access%3F%3CBR%20%2F%3EI'm%20referring%20to%20a%20article%20created%20by%20Mike%20Parker%3A%3CBR%20%2F%3E%3CA%20href%3D%22https%3A%2F%2Fwww.google.com%2Famp%2Fs%2Fmikeparker365.co.uk%2F2018%2F09%2F25%2Fhow-to-secure-exchange-2016-with-azure-ad-part-3-azure-application-proxy%2Famp%2F%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fwww.google.com%2Famp%2Fs%2Fmikeparker365.co.uk%2F2018%2F09%2F25%2Fhow-to-secure-exchange-2016-with-azure-ad-part-3-azure-application-proxy%2Famp%2F%3C%2FA%3E%3CBR%20%2F%3E%3CBR%20%2F%3EYou%20can%20then%20even%20use%20SSO%20with%20Windows%20Authentication%20to%20have%20only%20one%20sign-in%20experience%20from%20the%20Microsoft%20Azure%20sign-in%20page.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1496094%22%20slang%3D%22en-US%22%3ERe%3A%20Exchange%202016%20OWA%20-%20reCAPTCHA%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1496094%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20PvB91%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWe%20aren't%20using%20Azure%20so%20that%20won't%20work.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20did%20some%20more%20testing%20during%20the%20weekend%20and%20decided%20to%20start%20from%20scratch%20and%20also%20reboot%20our%20mail%20servers.%20After%20that%20everything%20was%20working%20like%20it%20should.%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-1783388%22%20slang%3D%22en-US%22%3ERe%3A%20Exchange%202016%20OWA%20-%20reCAPTCHA%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1783388%22%20slang%3D%22en-US%22%3E%3CP%3EHi%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F708708%22%20target%3D%22_blank%22%3E%40Shotterke%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EPlease%20follow%20these%20to%20get%20reCAPTCHA%20key%20first%2C%20and%20make%20sure%20your%20FQDN%20for%20OWA%20has%20input%20to%20Google%20reCAPTCHA%20admin%20console%3C%2FP%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fwpforms.com%2Fdocs%2Fsetup-captcha-wpforms%2F%22%20target%3D%22_blank%22%20rel%3D%22noopener%20nofollow%20noreferrer%22%3Ehttps%3A%2F%2Fwpforms.com%2Fdocs%2Fsetup-captcha-wpforms%2F%3C%2FA%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAnd%20it%20will%20be%20great%20to%20use%20reCAPTCHA%20v3%20for%20Exchange%20OWA%20by%20following%20this%20comment%3C%2FP%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fgist.github.com%2Fmsenturk%2F8a667e4f9703bbdf9b8ea9c43baad768%23gistcomment-2988079%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3Ehttps%3A%2F%2Fgist.github.com%2Fmsenturk%2F8a667e4f9703bbdf9b8ea9c43baad768%23gistcomment-2988079%3C%2FA%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2210357%22%20slang%3D%22en-US%22%3ERe%3A%20Exchange%202016%20OWA%20-%20reCAPTCHA%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2210357%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F48565%22%20target%3D%22_blank%22%3E%40Aska%20Su%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3EUnfortunately%2C%20page%20on%20GitHub%20give%20s%20Error%20404%20and%20is%20not%20alive.%3C%2FP%3E%3CP%3EHave%20some%20info%20from%20other%20place%20or%20may%20be%20from%20your%20experience%20for%20using%20Google%20ReCaptcha%20v.3%20on%20Exchange%20OWA%202013%2F2016%2F2019%3F%3C%2FP%3E%3CP%3ETried%20to%20use%20it%20but%20it's%20not%20working.%20Only%20recaptcha%20v.2%20is%20working%20OK...%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2261296%22%20slang%3D%22en-US%22%3ERe%3A%20Exchange%202016%20OWA%20-%20reCAPTCHA%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2261296%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fgist.github.com%2Fmsenturk%2F9f16155a92be6c560a2be4045fba9093%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3E%40akazakevich%26nbsp%3B%3C%2FA%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E
New Contributor

I'm trying to implement reCAPTCHA on my Exchange 2016 OWA and ECP login page.

 

I followed this guide but I'm still unable to get this to work:

https://translate.google.com/translate?hl=en&sl=auto&tl=en&u=https%3A%2F%2Fwww.askasu.idv.tw%2Findex...

 

When I go to the login page using the DNS name (So using the domain I entered in reCAPTCHA) nothing shows up and I can login with just my username and password with no extra checks.

 

When I go the the IP address I get the error "ERROR for site owner:Invalid domain for site key" which is normal but it shows that the reCAPTCHA is there.

 

Has anybody else ever implement reCAPTCHA and give me some pointers or guides how they did it?

5 Replies
Hello Shotterke,

I think you are trying to implement ReCAPTCHA because of security reasons?

Wouldn't it be better to use Azure Application Proxy so you can use things like Conditional Access?
I'm referring to a article created by Mike Parker:
https://www.google.com/amp/s/mikeparker365.co.uk/2018/09/25/how-to-secure-exchange-2016-with-azure-a...

You can then even use SSO with Windows Authentication to have only one sign-in experience from the Microsoft Azure sign-in page.
best response confirmed by Shotterke (New Contributor)
Solution

Hi PvB91,

 

We aren't using Azure so that won't work.

 

I did some more testing during the weekend and decided to start from scratch and also reboot our mail servers. After that everything was working like it should.

 

 

Hi @Shotterke 

 

Please follow these to get reCAPTCHA key first, and make sure your FQDN for OWA has input to Google reCAPTCHA admin console

https://wpforms.com/docs/setup-captcha-wpforms/

 

And it will be great to use reCAPTCHA v3 for Exchange OWA by following this comment

https://gist.github.com/msenturk/8a667e4f9703bbdf9b8ea9c43baad768#gistcomment-2988079

@Aska Su 

Unfortunately, page on GitHub give s Error 404 and is not alive.

Have some info from other place or may be from your experience for using Google ReCaptcha v.3 on Exchange OWA 2013/2016/2019?

Tried to use it but it's not working. Only recaptcha v.2 is working OK...