Deprecated: YoastSEO_Vendor\Symfony\Component\DependencyInjection\Container::__construct(): Implicitly marking parameter $parameterBag as nullable is deprecated, the explicit nullable type must be used instead in /home/nubelus/sharedove/adisjugo/wp-content/plugins/wordpress-seo/vendor_prefixed/symfony/dependency-injection/Container.php on line 60

Deprecated: YoastSEO_Vendor\League\OAuth2\Client\Provider\AbstractProvider::authorize(): Implicitly marking parameter $redirectHandler as nullable is deprecated, the explicit nullable type must be used instead in /home/nubelus/sharedove/adisjugo/wp-content/plugins/wordpress-seo/vendor_prefixed/league/oauth2-client/src/Provider/AbstractProvider.php on line 416

Deprecated: YoastSEO_Vendor\GuzzleHttp\Client::getConfig(): Implicitly marking parameter $option as nullable is deprecated, the explicit nullable type must be used instead in /home/nubelus/sharedove/adisjugo/wp-content/plugins/wordpress-seo/vendor_prefixed/guzzlehttp/guzzle/src/Client.php on line 181

Deprecated: YoastSEO_Vendor\GuzzleHttp\ClientInterface::getConfig(): Implicitly marking parameter $option as nullable is deprecated, the explicit nullable type must be used instead in /home/nubelus/sharedove/adisjugo/wp-content/plugins/wordpress-seo/vendor_prefixed/guzzlehttp/guzzle/src/ClientInterface.php on line 77
{"id":1720,"date":"2012-11-14T17:19:54","date_gmt":"2012-11-14T16:19:54","guid":{"rendered":"https:\/\/blog.sharedove.com\/adisjugo\/?p=1720"},"modified":"2012-11-14T17:19:54","modified_gmt":"2012-11-14T16:19:54","slug":"using-cloudshare-vanity-urls-with-sharepoint-sites","status":"publish","type":"post","link":"https:\/\/blog.sharedove.com\/adisjugo\/index.php\/2012\/11\/14\/using-cloudshare-vanity-urls-with-sharepoint-sites\/","title":{"rendered":"Using CloudShare Vanity URLs with SharePoint sites"},"content":{"rendered":"

I had a question after my session at Microsoft Sinergija<\/a> in Belgrade \u2013 how do I use this \u201c*.cld.sr<\/em>\u201d domains from CloudShare<\/a> with SharePoint 2013 public facing sites. Well, although the techniques of alternate mappings and web application extending are not new in SharePoint \u2013 they have been there since quite some years \u2013 let\u2019s put it again all together, from the CloudShare Vanity URLs perspective.<\/p>\n

<\/p>\n

When you order a CloudShare ProPlus subscription, you get something called \u201cVanity URLs<\/a>\u201d. Those are URLs on cld.sr domain, which you can use to publically access you CloudShare resources, whatever they might be. In this case, I want my SharePoint Team site to be accessible from the outer world through such an URL. <\/p>\n

For start, let\u2019s create a SharePoint web application, on a CloudShare-hosted SharePoint 2013 server (the same is true for 2010), on a port 2002 (you can use any port you like). I\u2019ll use standard NTLM authentication, and all standard features. <\/p>\n

\"cldsr01\"<\/a><\/p>\n

\"cldsr02\"<\/a><\/p>\n

After the Web application has been created, SharePoint will prompt me to create a root site collection in that web application, and I\u2019ll do just that, based on the \u201cTeam\u201d template. <\/p>\n

\"cldsr03\"<\/a><\/p>\n

My SharePoint team site will be internally accessible on the following URL: http:\/\/sp2013:2002\/<\/strong> <\/p>\n

As you see \u2013 this site is only accessible internally, from a local network. No external access is possible.<\/p>\n

\"cldsr04\"<\/a><\/p>\n

On the other side, log into your CloudShare account, and go to the \u201cMy Account\u201d tab, and then \u201cVanity URLs\u201d tab. You will see your CloudShare environment there, with the servers listed, and beside each server is a possibility enter an *.cld.sr domain of your choice, and declare it as a Vanity URL. Be aware, you can have only one Vanity URL at time, so if you have multiple SharePoint servers in your environment, you will need to chose to which one do you want to associate your Vanity URL. <\/p>\n

I have 3 machines in my environment \u2013 AD, SharePoint 2013 and Windows 8, all belonging to the \u201cAdisCloudShare<\/em>\u201d domain, with AD machine as the domain controller.  I\u2019ll associate my Vanity URL \u201ctestvanityurl.cld.sr\u201d to the SharePoint 2013 machine:<\/p>\n

\"cldsr05\"<\/a><\/p>\n

Now, how do I associate a previously created team site on that machine, with a CloudShare Vanity URL I just selected?<\/p>\n

There are two ways to do it. One way is to use so called alternate mappings. It\u2019s an old technique in SharePoint, giving multiple mappings to SharePoint web applications \u2013 that basically means that a single web application will be accessible through different \u201cmappings\u201d (URLs). The advantage of this approach is that it is a fast and straight forward method, and requires no overhead on the server.<\/p>\n

Second way is extending the web application<\/a>. When you extend a web application, you expose the same content to different sets of users by using an additional IIS web site to host the same content. The advantage of this approach that you are not bound on the same authentication mechanisms, and same users as with your original web application \u2013 for example, your local AD users can use NTLM authentication, and for the partners, accessing from outside, you can use form based authentication. The downside is that it creates an additional IIS site\u2026<\/p>\n

Let\u2019s look at the both ways how to assign CloudShare \u201cVanity URL\u201d to the web application.<\/p>\n

Alternate mappings<\/h3>\n

In the Central administration, go to the Application Management, and then click on the \u201cConfigure alternate access mappings\u201d.<\/p>\n

\"cldsr06\"<\/a><\/p>\n

You see all existing alternate mappings listed here, among them is the \u201cdefault\u201d mapping for our newly created web application \u201chttp:\/\/sp2013:2002\u201d. <\/p>\n

Now click on \u201cAdd internal URLs\u201d link above the mappings:<\/p>\n

\"cldsr07\"<\/a><\/p>\n

And add the Vanity URL you selected before (http:\/\/testvanityurl.cld.sr<\/a> in my case), and choose the \u201cInternet<\/strong>\u201d zone. <\/p>\n

\"cldsr08\"<\/a><\/p>\n

Save the changes, and open the IIS manager. Find the web site on the port 2002 (our newly created web app), click on edit bindings, and look if the binding on \u201chttp:\/\/testvanityurl.cld.sr\u201d at port 80 has been added. If it isn\u2019t, please add it manually, as a new binding. Don\u2019t remove the original binding on the port 2002. <\/p>\n

\"cldsr09\"<\/a><\/p>\n

Now, let\u2019s try our vanity URL in browser \u2013 it should work. <\/p>\n

\"cldsr10\"<\/a><\/p>\n

\"cldsr18\"<\/a><\/p>\n

Extending the web application<\/h3>\n

Let\u2019s create another Vanity URL, which we will use in extended web application. Be aware that we will need to release the previous Vanity URL, used for Alternate Mappings approach. Remember, we can have only one active Vanity URL at time.<\/p>\n

My new vanity URL will be testurl2.cld.sr<\/strong><\/p>\n

\"cldsr12\"<\/a><\/p>\n

Now go back to SharePoint Central Administration, click on the Application Management, select our application on the port 2002, and click on the Extend Application button in the ribbon bar.<\/p>\n

Since a new IIS site will be created, you will be prompted for some info. Let\u2019s create it on the port 2003, and call it \u201cExtended site \u2013 2003\u201d.<\/p>\n

\"cldsr20\"<\/a><\/p>\n

On the bottom of the extending the web site form, there are URL and Zone fields. Please enter your Vanity URL in the URL field, and choose the \u201cInternet<\/strong>\u201d as a Zone. <\/p>\n

\"cldsr21\"<\/a><\/p>\n

If you want, in the same form, you can configure From Based Authentication, or Trusted Providers (like Azure Access Control Service) for this new, extended web application. For the sake of simplicity of this article, I\u2019ll just leave that alone.<\/p>\n

\"cldsr22\"<\/a><\/p>\n

Now, go back to the Central administration, and then go to the Application Management, and then click on the \u201cConfigure alternate access mappings\u201d.<\/p>\n

Both our mappings \u2013 the default one on the port 2002 and the new, internet zone mapping with new Vanity URL should already be present.<\/p>\n

\"cldsr24\"<\/a><\/p>\n

Now, go to the IIS Manager, and look for the Extended site on the port 2003 which we have just created.<\/p>\n

\"cldsr25\"<\/a><\/p>\n

Ckick on Edit bindings, and look if the binding with your Vanity URL on the port 80 is already present there. If not, please add it. <\/p>\n

\"cldsr26\"<\/a><\/p>\n

And again \u2013 works like a charm \"Smile\"<\/p>\n

\"cldsr18\"<\/a><\/p>\n

Thank you CloudShare for this whole Vanity URLs!<\/p>\n

\n\t\t\t
\n\t\t\t <\/div><\/div>\n\t\t