The Google One Tap prompt is showing Sign in to <domain name> with Google instead of Sign in to <application name> with Google. It was able to show the application name when I was working on localhost, but when I tried to deploy on a staging environment, only the domain name was showing.
Might this be related to the Google application publish status still in Testing? Or the domain not yet verified in the Google Search Console? Do note that the application only requires non-sensitive scopes, if that helps.
Related
I have a .NET MVC applicatoin and I am trying to use Azure AD Authentication.
I create a new project and chose
"Work or School Accounts"
Cloud - Single Organiszation
At no time does it ask me for a redirect URL
I then click okay and it creates the solution (as well as registering it at Azure AD).
Problem is that when I login it alway redirects to a localhost address.
Even if I change the web.config to the correct URL of the app (as registed in IIS) it keeps redirecting. When I log into Azure AD the app is listed as an Enterprise Application and I am unable to change the homepage URL
Instead of "Enterprise Applications", you need to go to "App Registrations" in your Azure AD.
So navigate to Azure Protal > Azure AD > App Registrations > Find app registration for your application (you may need to change from "My apps" to "All apps"
Then make whatever changes you need:
You can change the home page under Settings > properties
Also, an important part is to add the required URL in Reply URLs as shown in screenshot below. Settings > Reply URLs
I just recently installed a one click application from the Google Cloud Platform. I installed WordPress as a VM instance , but when I try to access my VM instance via ssh i see that its empty and it doesn't contain any WordPress files. Is there a way to access the WordPress files either via FTP or even better ssh?
One click deployments should come with everything you need “out of the box”.
You can visit your Deployment Manager and click on the Word Press resource to view login options and choose SSH or login to the Word Press admin console from there.
Accessing files through SCP can be done through the GCloud command line as well as another alternative.
I just created a webform that is hosted in my Azure subscription. I set it up with authenication via my works Azure directory for authenticating users. In debug this works fine and I am able to login with my work credentials and then view the website via local host.
I have published this to my Azure and it says it is running and working fine. So when I try to connect to the website it continuously redirects me to the localhost resulting in an error.
I have checked the web config.
Here is the google network chain of events when it occurs.
I am really lost as to what is wrong and what I need to do to fix this so any help would be greatly appreciated. I'm sorry I can't offer more but I don't even know what is wrong to begin with or where to look. Is there some setting in Azure that I need to add the website too?
I have solved this issue. Since it was such a pain I will keep this up as I couldn't find any answers on this. It was actually quite simple.
You have two options. The one I did and which worked was changing the publish profile as below:
Add the domain where the authentication is occurring. So if you have your web app hosted by a different azure account that which is authenticating the users, use the one that is authenticating.
This will create two versions of your app on the site one for local host and one for the actual site.
The second option(I have not tried this but it should work) is to go to the Azure account where you are authenticating the users and go to applications and then configure. Change the APP URL from local host to the url you are trying to get to.
Here is an excellent link that explains how to do this clearly.
Click this link for detailed explanation
I also had this issue and took these steps to resolve
navigate to the app registration in AAD
Open the manifest
Change the ReplyUrl to the url of the app (e.g. http://appname.azurewebsites.net)
Then I got the error
Bad Request - Request Too Long HTTP Error 400. The size of the request headers is too long.
Next I cleared all cookies from the browser, and this changed the error to just
Bad Request
So I went back to that ReplyUrl and changed it to https://appname.azurewebsites.net/.auth/login/aad/callback and now it appears to work.
Note I also had to make sure I didn't have the site open in any other tabs before it started working
I had this issue when I switched an app from our company Azure over to a customer's Azure. In my case I'd forgotten to update the ida:ClientId, ida:AADInstance and ida:TenantId, which then meant that the value I'd set for ida:PostLogoutRedirectUri was ignored (I think) and instead my app redirected to localhost.
Once I changed those ida values to the values from the app settings and subscriptions settings on our customer's Azure it all worked as expected.
It took a while to track down all the values in Azure portal as they are all called something different, or aren't named at all:
ClientId can be found at Azure Active Directory > App Registrations > YourAppName. It's called 'Application ID' in Azure
Domain can be found on Azure Active Directory > Overview. It's currently in the top left in the format somename.onmicrosoft.com
TenantId this is the Azure AD instance ID, get that from Azure Active Directory > Properties and then it's called 'Directory ID'
I spent a lot of time trying to work out where the localhost port that was being redirected to was in the code, but it simply isn't there as far as I can see, so I have no idea how Azure was choosing what localhost address to redirect to!
You need to set another parameter in configuration that is replyUrl and assign to your web app, other wise it takes the url from which it was originated.
I was able to fix this by changing my Startup.Auth.cs file redirectUri from "https://localhost:44316/" to https://myapp.com/
I'm trying to get started with the WSO2 API manager. I changed the admin password from the default, and am slowly working my way through all the places it seems to get embedded. The latest issue is that when I try to self-register in the store, I get:
Unable to add a user. Please check credentials in the signup-config.xml in the registry
What is this registry, and how do I get to signup-config.xml to edit the admin password?
You can navigate to registry resource through admin console.
access admin console in following url
https://localhost:9443/carbon
then in the main tab you can find a section called Resources .There click on browse link . this will take you to browse the resources in registry.
you can find the sign-up-config.xml in the following location by browsing
/_system/governance/apimgt/applicationdata/sign-up-config.xml
there you need to change the admin password
I have a meteor app running in a node.js machine on nitrous.io and the facebook authentication is not working. I created a new app in facebook, added Website as platform, set the App domain to machinename.usw1.nitrousbox.com and the Website's Site URL to http://machinename.usw1.nitrousbox.com (machinename is made up, but I have my own site there) and then I used the public & secret key to set the fb auth in running meteor app. This is all similar to how I've setup apps before, yet when I try to login to this nitrous.io app using fb, I get this from facebook:
Given URL is not allowed by the Application configuration.: One or more of
the given URLs is not allowed by the App's settings. It must match the
Website URL or Canvas URL, or the domain must be a subdomain of one of the
App's domains.
I've tried all different kinds of settings. Any ideas?
There are two ways to solve this.
Option 1:
Meteor looks for a ROOT_URL environment variable to determine the url the app is running, which is http://localhost:3000/ by default. You can keep the setting as is, but you will need to utilize the following credentials within your facebook app configuration:
site_url: http://localhost:3000/
Option 2:
If you want to utilize your preview URL then you will want to set the site_url to it within your facebook app configuration:
site_url: http://machinename.usw1-2.nitrousbox.com
The next step will be to start up Meteor with the following command:
$ ROOT_URL=http://machinename.usw1-2.nitrousbox.com meteor
Alternatively you can follow the Meteor documentation to change your root URL.