I have below resources in Azure
Azure Front door with 1 custom domain as https://fdtest.com
2 Azure AppService as https://appservice1.com and https://appservice2.com. Both these appservices have different functionalities.
Is it possible to configure front door such that , if the user1 enters front door URL something like https://fdtest.com/app1, then content of https://appservice1.com should come up without disabling the appservice2 backend.
and if user2 enters front door URL as https://fdtest.com/app2, then content of https://appservice2.com should come up without disabling the appservice1 backend.
Both the routings , that is, fdtest.com/app1 and fdtest.com/app2 should be active at same time and redirect user to respective backend.
What I have seen so far is that for above requirement I will need 2 custom domains in frontdoor but I don't want that. I want to achieve this with only 1 custom domain.
Related
As part of the upcoming changes to Facebook Ads, you now must verify ownership of your domain name.
We operate a SaaS platform where user content is hosted on subdomains (myaccount.example.com etc). We need these users to be able to verify ownership of their domain so they can track their own events. We have enabled them to add the meta tag on their domain, and this verifies okay.
<meta name="facebook-domain-verification" content="codefromfbhere" />
However, the problem is, when you go into 'Events manager' -> 'Aggregated event measurement' -> 'Configure web events', it shows me the root domain instead of the subdomain I just verified (e.g. example.com instead of myaccount.example.com).
This is possible, as Leadpages has achieved the same goal. When you add in a Leadpages subdomain, you're able to verify it via meta tag, and it shows the subdomain in the 'Web event configurations' area.
I don't see any extra headers that they have provided or anything else that would enable this.
How do you mark subdomains as independent from the eTLD+1?
I wanted to chime in with the perspective of someone who works for Facebook. For most businesses, even ones that host pages for other businesses, Aggregated Event Measurement without anything extra is the correct solution.
Advertisers who do not own their own domains will not be able to verify the domain for the purpose of event configuration in Ads Manager. Advertisers may consider purchasing their own domain to continue running their campaigns uninterrupted, or moving toward link clicks/landing page views for campaign optimization and reporting. We are currently investigating other solutions for this use case but do not have any additional information to share at this time.
For a very small number of businesses already on the Public Suffix List (PSL) subdomains will be able to get data as if they were a root domain. This is because being on the PSL basically makes the root domain name act as if it was a TLD (such as “co.uk“ or ”gov.au“). In almost every case it does not make sense for sites to request to be added to the PSL as this dramatically changes how the Public Suffix listed domain name will function.
The PSL process is intended only for platform providers that provide subdomains for large numbers of small businesses which really ought to be treated as though they were in fact separate domains.
The Public Suffix List is not useful, nor intended to be used as a means to gain additional subdomain events reporting. Adding a domain name to the PSL means that there will be total cookie separation between subdomains and that cookies will become disabled on the root domain. If you a domain gets added to the PSL you'll not have much control for that site itself. For example, if you have a /login page on that domain. This may not work as it does today if you proceeded with a PSL addition, as cookies may get disabled on the root domain.
It’s also important to note that browsers will enforce the behavior described based on their own update cadence of the PSL. Some browsers don't update their lists more regularly than bi-annually. This means that if you're on the list and a browser updates their copy of the list, and you later decide to not be on the list, there may not be an easy way to back out the effects; it's not as simple as submitting another request to get taken off of the list.
More information can be found at Facebook’s help center article here.
[Update Mar 19 2021]
Facebook just announced they will be supporting the Public Suffix List for domain verification and event configuration. This means that merchants using a registered domain on the Public Suffix List will be able to use that domain for verifying and configuring their top 8 events on the domain. For example, if myplatform.com is a registered domain on the Public Suffix List, then Jasper, a merchant with the subdomain jasper.myplatform.com, would now qualify as an effective eTLD+1 and would be able to verify "jasper.myplatform.com" and use it to configure their top 8 events in the web events configuration tool.
Read more here:
https://developers.facebook.com/docs/sharing/domain-verification
[Original Answer]
For the upcoming changes for Apple iOS 14.5, you can only verify root domain, which is example.com in your example in order to setup the web event configurations.
The only way you can do this is provide your client's a way to buy/setup their own domain on your service.
You may watch the webinar recording here
https://www.facebook.com/business/m/sessionsforsuccess
I am building a Saas platform (lets assume domain is www.saas.com) where user have unique subdomains such as user1.saas.com, user2.saas.com etc. And give them a feature to add their own custom domain.
To add custom domain, users define cname for app.saas.com and A record for public id in of my app.
Everything is working fine if cname and A record is defined correctly by users. But i have two concers about this:
To host my app, i used cloudways and select digital ocean servers. But if i want to move from Digital Ocean to AWS at some point, then public ip is going to change. So custom domains wont work until users change their A record.I wonder if is there a better way to give custom domain feature to user instead of adding A record? (I am not sure if cname and a record is the correct way for this feature)
Let's assume user1 is defined own domain for user1.saas.com. When i go to user1.saas.com, it is also working. I think, i should redirect this url to custom domain if it is defined. I wonder if this is a correct way?
Thanks in advance
Anil
My requirement is that i have a liferay portal which has two types of user creation process:
Manual creation by the admin
Users can create via create account
I want to land the users to different landing pages based on the user-groups. User creation process1 belongs to one group and process2 belongs to another group. How to achieve it. Process1 is working fine by setting the default landing path but i want to land the users who are created by process2 to a different landing page.
Thanks in advance!!
Regards,
S.Ponraj
Take a look at the page here for information on how to create a landing page hook.
You will also need a way to identify if the user is from process 1 or process 2. One possible approach would be using liferay custom fields (expando).
I've been thinking about an online idea for about 3-4 years now and can't get it out of my head so I've decided to act upon it and see if I can get it working. Currently working a POC and design layout which I plan to tender for development.
The main part of the portal and most important component involves user sub-sites. I am unsure how to tackle the process for a user to create a sub-site during the registration process and/or what path to take.
Let's say the main site is www.abc.net - the user would then register a sub-site based on the credentials they input. E.g. user1.abc.net, mysite.abc.net or joeblog.abc.net... whatever they want and so forth. No SEO required - The site templates are fairly basic and the sub-sites will be accessible through the main site. So the process to be:
User logs onto main site and registers
During registration, user enters details including sub-site name they want
Select the template they want - basically different colour schemes. Functionality to be the same for all templates
their site is created
when the user is logged on they get directed to their sub-site
Ability to edit their sub-site - add content and add extra pages, change details…. etc
General users (registered or anonymous) would be able to browse and search content to the sub-sites via the main site.
Each sub-site to be independent from each other - no content sharing. Basically they are separate websites hosted as sub-sites but need they need some type of editing available like a CMS. Not sure if a shared CMS is possible but the owner has to be able to modify content to their own sub-site.
So my question are…
Do I try and use a Drupal/Wordpress/Joomla CMS with multisite functionality?
Do I try a solution where I have a collection of simple sites that I use for sub-sites, each to have their own database and some type of CMS or WYSIWYG for editing? Is separate CMS even possible for each Sub-site?
Any input would be greatly appreciated.
As far as I know this would not be possible as the CMS would not have access to your server where the sub-domain is created.
It would be possible to offer something similer using Joomla as it offers the option to apply custom styles (templates) to different pages. You would however have to adopt the following URL convention www.yourdomain.com/userselectedtext.
You can then have a page where users register with your site and the cms creates their page.
User permissions in joomla can be set so only the owner of a particular page can view or edit it.
You can check out this source: http://www.drupalgardens.com/. Google what platform is it based on. Maybe you'll find some information. Read also about this extension: http://www.joomplace.com/administration-extensions/multisitescontrol.html. It's for Joomla sites. I used this component for multisites content management. Maybe it will help you too.
We are in the process of building a Multi-Tenant, SaaS type web app. Everything is set to go on the application part but when it comes to email there is a problem.
Each tenant/user of the application has a subdomain based account. However, there will be the option for that tenant to associate a top level domain to their account. Here is where the problem comes for us.
Basically, if the user sets up their DNS to point to our SaaS web app everything works good on the app front except that it now makes us responsible for handling their Email as well. Incoming and Outgoing.
What is the best way to handle this? I really was hoping their is a 3rd party site that handles outgoing and incoming email for multiple top level domains under one company name but am unsure.
There is always the option of doing our own SMTP/POP service, but we would really like to steer away from the responsibilities of email.
Thanks everyone,
~kvq
Can't they just setup an A record or a CNAME to point to your servers?
If they did an A record it would allow just webapp.theirdomain.com to go to your severs and everything else can just stay on their DNS.
The other option and maybe a better option is for them to setup a CNAME. Then you can just setup companyA.yourdomain.com and then they can just setup a CNAME that points webapp.theirdomain.com to companyA.yourdomain.com
You really do not want to be responsible for all of their DNS. They can keep their DNS where ever they want and keep their MX records the way they are.
I hope this helps