openam authentication for only one website - openam

I have more than 10 websites on my server but I need OpenAM for only one of them. I tried installing OpenAM but it goes for all of them.
My websites are hosted on CPanel and WHM.

you may look at not-enforced-list invert feature of the agent and only add the URLs for the site you wanted to be protected

Related

What is the difference between add website and add application into website while publish into iis

While publish into iis i can create website and publish into it. And also i can create an application into a website. So can you please tell me why website and application
In IIS Terms, a Website can have many applications.
Let's say you have 3 websites...
example.com
website.com
test.com
Those are all different websites, now lets say example.com has three applications
example.com/calculator
example.com/lightbulb
example.com/forum
Calculator, lightbulb, and forums are considered as applications under example.com The Website

Add security to IIS Web Server

I'm developing some web site that run on IIS 7 and can connect to SQL server via php. The problem is I think its not safe because everyone that know my public IP address can freely access my site (the site is not for public, but I need it to be accessible to some people). How can I add security to this website of mine?
I have search for some type of security like authentication in IIS, but I don't know what should be used. Can I just add id and password like when we try to open page for configure router (192.168.0.1) .
You can easily disable anonymous authentication and enable basic authentication in IIS 7 using IIS manager.
Here is a Technet link and an SO post with details:
Is it a standalone server or do you run the IIS server on a desktop?
If your the only one who should access your site you could also use Intergrated windows authentication (IWA). IWA is a feature of the IIS Server, so if you wan't to use is you should enable it first.

Sitecore multisite : How to configure SSL for different domain

We have a multi-site implementation with different domain names.
e.g. mydomainA.com.au, subdomain.mydomainB.com.au, mydomainC.com.au
All these sites are hosted under one sitecore instance. We need to enable the SSL for each domain names for which we have wild card SSL Certificates each.
We are using IIS 8.
Could some one suggest what's the best way to configure multiple SSLs for single sitecore multisite instance?
The best way is depend on the wishes and requirements.
The simple solution in IIS 8 there are new options it should be possible to assign multiple Certificates to one website. Add some flexibility and use for each domain a separate, dedicated IP (also needed for older IIS)
More advanced reduce dependency On the CD create for each site a own website with own webroot in IIS (on the same server) (Sitecore licenses need for each IIS site) and use the same Sitecore databases. It give you a IIS and Sitecore log file for eache site and multiple webroots to maintain. See Multiple IIS Sites
For Sitecore CD there is no special ssl config needed.

Procedures to launch a fully-operational site on a VPS

OK, there is a newbie on VPS here.
I want to know what should i need to do in order to launch a site on VPS!(All things in order)
There is a site called vpsbible i just don't want to watch all those videos!
I can arrange to do any thing, but i need to know the steps i need take.
What i am asking is what is the sequence for launching a website on a VPS!?
i.e from buying a host to DNS configuration, etc...
PS: i googled the topic but i didn't find anything solid.
It's very easy adding a site on VPS server using the VPS hosting control panel - Plesk in Windows VPS, and cPanel in Linux VPS.
Login in your hosting control panel.
Add a new account
Add a new site
Create email and FTP accounts
Point your domain name to your VPS server via DNS settings.
Deploy your site via FTP.
That's it with few steps. :)

Map custom domain (and wildcard sub-domains) to Azure Website

I've looked at all related posts in MSDN and stack overflow but still having difficulty finding a solution.
I am looking to map a domain and all sub-domains to my windows azure website. It is a reserved website instance. I am using Amazon Route 53 DNS manager and have mapped a wildcard CNAME to my azure sub domain, and created a redirect on the naked domain to the www. subdomain.
When I navigate to the naked root, the redirect kicks in and I'm brought to www..com, where I receive a 404 error from azure.
I know the wildcard CNAME is working. I've verified using MXToolbox. If I go to "Manage Domains" in the Azure web UI admin system, I can manually add "www..com" or any other subdomain (e.g. "helloworld..com"). Azure verifies it fine and after saving, I can pull up the website fine by navigating to that subdomain and my azure website loads.
Is there any way to add wild card subdomains without having to verify each one manually through the azure ui interface? My application is a SaaS that relies on custom user sub-domains to serve up their branded website and gain access to their account so I need any and all subdomains to map to my application.
Currently, wildcard domains are not supported as far as I know. At least on Windows Azure Web Sites. They are on the roadmap, but currently you'll have to rely on adding every domain manually.
See wildcard comment on "Configuring a custom domain name for a Windows Azure web site".
Another feature not yet available on Azure Web Sites is SSL using a vanity (your own) domain name. If you want full control of your site(s) you can use Azure Cloud Services instead of Web Sites. With Cloud Services you can provision certificates, domain names, and run multiple sites on the same instances using host header routing.
Anything you can do with IIS Management you can do with a cloud service.
You're a little closer to the metal compared to Azure Web Sites (but not as close as with a VM) and you get load balancing, scaling, caching, and other goodness. Visual Studio 2010/2012 has excellent deployment tooling. You will need to study up on Azure deployment projects from VS, bit it's not bad.

Resources