Jan 18 2017 05:35 AM
We have a requriement wherein users who don't have access to our custom SP2013 site should get to see a custom access denied page instead of the default access denied page. Basically as part of this page, we want to provide them a screen/page using which they can enter a few more details and request for acecss (triggering a workflow process).
So, what would be the best approach this? I have already seen the following technet article wherein it discusses around this topic. However, believe this will affect the entire farm of SP2013 i.e. the custom access denied page implemented using this method will be shown for all other sites? While we just want to have a custom access denied page for our own Site Collection (we can consider a web app as well - if it meets the requirement i.e. limited to the web app), it should not affect other sites.
Thanks !!
Jan 18 2017 07:56 AM
Jan 18 2017 09:36 AM
I was wondering if there was any better or alternative approach the HTTPModule approach is quite dated and requires deployment in the server farm . Also, we did NOT want to have a solution for the entire farm, instead just of our site collection or at the max for the web application containing the site collection.
Jan 18 2017 10:15 AM
Jan 25 2017 10:09 AM
I would rather try the following option, looks to be meeting my current requirement.
Will updated here with the results...
Jan 25 2017 10:11 AM
Jan 25 2017 01:18 PM