There are lots of posts out there that explain to you how to link a custom Access Denied page to the system so that it displays your page instead of the OOB one. Even a couple of posts on HOW to create that page.
In my case, I wanted to do this:
I wanted to:
- Use my own logo
- Allow for signing in as a different user
- List all of the Site Administrators for the site you’re trying to reach
- Display a custom “Request Access” page in a Modal Dialog box
This turned out to be a bit tricky.
- I used an application page in Visual Studio 2010, but instead of inheriting from LayoutsPageBase, I used UnsecuredLayoutsPageBase. That way you don’t have to override the 4 methods to allow the user into the page.
- I changed the master page reference to MasterPageFile=”~/_layouts/simple.master”
Use my own logo
I read that all you had to do was to override your logo in the PlaceHolderPageImage content placeholder. So I dutifully put my image there, even calling it the same ID as the one it expected: <img id=”onetidtpweb1″ src=”/_layouts/images/Custom/Logo.png” alt=”Logo”/>. However, that did not seem to work. So I used JQuery to show my logo after-the-fact (it’s a workaround, not a true solution – don’t know why the placeholder didn’t work).
In PlaceHolderAdditionalPageHead, I had this:
<asp:Content ID=”Content2″ ContentPlaceHolderID=”PlaceHolderAdditionalPageHead” runat=”server”>
<meta name=”Robots” content=”NOINDEX “/>
<meta name=”SharePointError” content=”1″/>
$(‘div.s4-simple-iconcont > img’).attr(‘src’, ‘/_layouts/images/Custom/Logo.png’);
Allow for signing in as a different user
Turns out that CloseConnection.aspx apparently silently redirects them to the Access Denied page? Not sure exactly, but what I know is that if I hadn’t copied the code from SharePoint’s access denied page using Reflector, it wouldn’t sign me in as a different user. So use reflector on AccessDenied, and copy CloseConnection(), Send403(), SendResponse(), IsBrowserRequest(), matchLegacyFrontPageUa(), HandleLoginAsAnotherUser(), and LogInAsAnotherUser() as well as some of thePage_Load code – the part that checks the query string and calls LogInAsAnotherUser or CloseConnection.
I also had to reconstruct the link that the user gets on the page. I used the following code:
string urlForSignIn = web.ServerRelativeUrl;
urlForSignIn += “/”;
urlForSignIn += “_layouts/closeConnection.aspx?loginasanotheruser=true”;
urlForSignIn = urlForSignIn.Replace(“/”, “\\u002f”);
List all of the Site Administrators for the site you’re trying to reach
Immediately after the querystring inspection, create 2 variables to hold the Site Collection ID and the Web ID. NOTE: These are the only 2 things the code can get on these objects, if the user doesn’t have access to the site. In other words, you can’t access SPWeb.Title – that throws the page off to a 403 Unauthorized page. So you need to use SPSecurity.RunWithElevatedPrivileges and re-open your Site and Web objects securely, before you can get anything interesting.
When trying to get your admins, all I did was use foreach(SPUser in web.AllUsers) and then individually check web.DoesUserHavePermissions(user.LoginName, SPBasePermissions.FullMask). Keep in mind: you’re going to get service accounts and such when you loop through these users. I basically ignored the service accounts I knew about, and limited the results to my Domain (i.e. to get rid of SHAREPOINT\SYSTEM). I also did not take the account if it didn’t have an email address attached.
Display a custom “Request Access” page in a Modal Dialog box
So this one was wierd. I had to use SP.UI.ModalDialog.showModalDialog(options) to pop up the Request Access window. However, in order to call that function from your link, you have to include /_layouts/SP.UI.Dialog.js. As it turns out, that in turn relies on a couple of other JS files. But normally all you do is put the SP.UI.Dialog.js reference in a SharePoint:ScriptLink tag, and add a FormDigest tag as well, and then you can get to your modal dialog function.
However, it turns out BOTH the ScriptLink and the FormDigest tags actually throw the page into a 403 Forbidden state. So I had to take those out. But then the modal dialog didn’t work. I tried to no avail to manually add a bunch of JS references to the page, but kept getting Script errors.
So I found an article about something else that led me to the solution: http://howtosharepoint.blogspot.com/2010/09/programatically-hide-show-status-bar.html. Basically what he does is programmatically register the script links AFTER the UI is loaded, by adding this into the Page_Load function:
ScriptLink.RegisterScriptAfterUI(this.Page, “core.js”, true, false);
ScriptLink.RegisterScriptAfterUI(this.Page, “CUI.js”, false, true);
ScriptLink.RegisterScriptAfterUI(this.Page, “SP.js”, false, true);
This seemed to make the modal dialog errors go away, although periodically I am getting another script error I have to investigate.
Now keep in mind that the Request Access page has to also be based off of Simple.master. So you’re going to get the same sections of the page, including the image, the header, and the “Go Back To Site” link at the bottom. The good news is, though, that the Go Back to Site link just closes the modal dialog box.
And finally, when you’re done with your Request Access form and want to return to the Access Denied page, just add this to your code behind:
Page.ClientScript.RegisterClientScriptBlock(typeof(CustomRequestAccess), “closeDialogScript”, “SP.UI.ModalDialog.commonModalDialogClose(1, null);”, true);