I am using the different domain names for the front and back end, I don't know configure the redirect Uri for the different domains in google console,
Example:
front-end: www.abc.com
backend: www.xyz.com
Related
We are using our subdomains dynamically with dynamic prefix from client and use those domains for facebook login but suddenly after their new policies from 1st Aug we are getting error message.
I am not able to add subdomain like *.thebestlisting.com because facebook have restricted to use wildcard characters and use absolute domains only.
Can someone suggest me any alternative option to use my all subdomains with dynamic prefix and how I can cover it with Facebook application.
I would like to set the redirect URL for a Google App Im creating as app.dev.ddc/oauth2Callback or app.qa.ddc/oauth2Callback.
However, it appears the redirect URL can only be localhost or a url ending with .com.
Is this a known limitation.?
If so, is there any workaround my specific scenario..?
As The OAuth 2.0 Authorization Framework says:
The redirection endpoint URI MUST be an absolute URI as defined by RFC3986 Section 4.3.
Why you need this special redirect_uri?
I'm trying to register an application so that I can implement log in with facebook on my site. The problem is that my domain ends with a .net hence I get an Error
App Domains: ****.net is not a valid domain.
Site URL is not a valid URL.
What could be the problem because when I use .com everything works fine.
I'm developing a web application with Facebook Javascript SDK on my server at http://example.com/webapp/. Now I registered a new domain name, say domain.com, with no hosting, and I forwarded with URL masking domain.com to example.com/webapp/, so the web app is still on my server at example.com/webapp/. I've tried to change app settings on Facebook, site domain to domain.com and website URL to domain.com, but the Javascript SDK doesn't work!
I think that the problem is that requests to facebook comes from my server at example.com and the app domain is domain.com. I notice that the JS SDK uses window.location to retrieve the url to be matched with the app domain and website url.. Is there a way to inject the redirect_uri parameter on every JS SDK functions call with the url of my redirecting domain domain.com?
Thanks to all in advice!
Instead of using URL Masking / Forwarding, you should see if you can use your domain domain.com pointing straight to example.com/webapp using Add-on Domains.
I.e. create a virtual host and have the new domain link to the actual files on the old domain name. Fowarding isn't the best way as some forwards use iframes or javascript to redirect.
I have a domain and a group of sub-domains that require authentication to access. I am currently using mod_auth to authenticate users (mod_auth basic) at the domain.tld level. My goal is for single sign-on between the domain and all the sub-domains.
Will these credentials carry on to the sub-domains automatically, or with a simple vhost config change, or is there a better method to do this?
mod_auth_basic
Browsers distinguish areas that require HTTP authentication by a combination of the URL root and the name of the authentication realm.
Take for example, two domains each with a realm with the same name:
http://one.example.com/ with the realm "Please enter credentials!"
http://two.example.com/ with the realm "Please enter credentials!"
First a user visits one, is asked for credentials and enters them. Then the user visits two, the browser recognizes that the URL is different and thus asks again the user for her credentials.
This is a good thing, because otherwise www.badguy.com could set it up so that your browser sends over your online banking login.
In short: there is no way to solve your problem with basic HTTP authentication and standard HTTP clients.
mod_auth_digest
You could use mod_auth_digest instead, since with that you can specify more than one URI to be in the same "protection space". However, with this authentication method there are two new problems:
It doesn't scale very well, because you cannot use wildcard domains.
Browser compatibility is not as good. (See the documentation on how to make it work with IE.)