I have Meteor deployed on Galaxy using both the primary domain and a custom domain but when I log into the primary domain, then try to access my app from the custom domain I have to log in again.
Is their a way to log into both instead of having to do it separately?
No. Login works by storing your Meteor login token in local storage and this is not shared between domains (or even subdomains).
Related
Here is what I did.
register a domain with aws route53 ( example xyz.com ) - DONE
create one website on bitbucket repo1 ( simple hello world html ) - DONE
create second website on bitbucket repo2 ( simple hello world html ) - DONE
create app on aws amplify console, link with bitbucket repo1 , deploy to custom domain (repo1.xyz.com) - DONE
create app on aws amplify console, link with bitbucket repo2 , deploy to custom domain (repo2.xyz.com) - FAILED
Step 5 fails with following error
Create domain association failed - One or more domains requested are already associated with another Amplify app
Is this setup possible? I am not able to find any document from AWS to say it is / is not.
The idea is that a single domain needs to server multiple apps, for example
api.xyz.com --> serve rest api from aws api gateway
auth.xyz.com --> aws cognito domain
www.xyz.com --> public html website (managed by aws amplify console)
webapp.xyz.com --> react app (managed by aws amplify console)
Hope this helps, I just run into the same problem and was able to resolve it.
You are getting this error because you have probably verified the DNS provider for both subdomains from the same app, using the CNAME provided by one of the apps (the "data" part of your CNAME would be the same for both subdomain's CNAME in this case). What you should do, instead, is verify ownership of the domain in either app, but then configure the DNS provider for each subdomain in the corresponding app.
App1: Verify domain.com (and www.domain.com) and subdomain for app1.domain.com
App2: Verify subdomain for app2.domain.com (and disable domain.com as its automatically added).
If you duplicate a subdomain verification in 2 or more apps, then you will see the error you mentioned above (this includes domain.com and www.domain.com).
I have created a custom domain for the authentication mail templates in firebase, at the same time I have created a custom index.html in the hosting section. Now when I send password recovery emails the URL is not working, it just shows my index.html. Anyone have any idea what I might be missing.
Before it worked with the default UI of firebase for password recovery and email verification
Assuming you are using the same custom domain, make sure that the configured URL for Authentication has the format https://example.com/__/auth/action?mode=<action>&oobCode=<code>; this is also assuming that the custom domain is correctly configured in Hosting.
In setting up our own subdomain to handle Firebase Dynamic Links using these docs, the wizard says to put the A records at example.com in our DNS. I'm getting pushback from our network administrators who are wary of creating an A record at the root of our domain, which is a large e-commerce web site.
A couple of concerns/questions about this:
The IP addresses required (151.101.1.195 and 151.101.65.195) point to non-Google servers (looks like Fastly), which is a bit alarming - it seems strange that Google would outsource their deep link hosting.
We don't want all of our e-commerce traffic (coming through example.com) to be subject to these A records. Is it possible to put the A records at link.example.com instead?
The Firebase documentation on using a custom domain for dynamic links has this note:
To use a custom domain for Dynamic Links, the domain must point to Firebase Hosting. If you have a domain you want to use with Dynamic Links and the domain points to a different host, you can either move to Firebase Hosting or create a subdomain hosted by Firebase, which you can use for Dynamic Links.
So you can indeed use a subdomain for the dynamic links. In that case, just set up the subdomain in Firebase hosting. You'll need the same TXT record as normal, to prove that you have access to the domain, but then just map the subdomain (e.g. links) for the A record.
Here is the answer I received from Firebase support about these my two concerns/questions:
Regarding Fastly, Firebase uses this subprocessor to deliver content and managed services on Firebase Hosting. For more details you could check the list of Subprocessors used by Firebase on this doc.
It's possible to use a subdomain as your Firebase project's FDL domain. You'd need to create a subdomain (link.example.com) on your domain's DNS provider and connect it to Firebase Hosting. You could check out this guide for more details.
I am building a platform which consists of a public facing 'website' and a PWA which will be on a subdomain on the same server.
Both web apps use the same firebase project and I was wondering if it is possible to share authentication status between the two. i.e. can I redirect a user to the PWA side without them having to login again?
Both apps are written with React, Redux and Node
Store the authentication token in a cookie with the following domain:
.mydomain.com
where mydomain.com is the public site. Now the PWA can access this cookie as a subdomain of mydomain.com.
Subdomains can not access localstorage of the main domain or other subdomains, but can access cookies in the main domain.
If Firebase automatically writes to localstorage, write your own code to delete it from there (or leave it there), and add it as a cookie.
I don't think you need to put the . in front of the domain for your cookie anymore, but you used to and I still do.
I can't get FireFeed OR my own app working with auth, I followed the documentation for this. I copied in the rules and added the keys, what gives? Example: http://flx.me/firefeed/
One think to check when using the Firebase Simple Login / authClient feature is whether or not you have configured the proper application domain in your account. Any domains that you'll be using to host your application and making authentication requests from should be configured in the 'Application Domains' section of Forge (get here by putting your Firebase URL in a browser). For your application, your domains should include flx.me.