I am trying to register my app for Oauth consent screen, so that I can create a OAuth client ID. I keep getting this validation error at end of the form, even though I have submitted everything correctly.
An error occurred while saving your app
And this error does not state which input in the form is invalid. Also in the network tab of development tools window, everytime I submit the request, I can see a POST request being initiated and it fails with following error.
{"error":{"code":3,"message":"The request failed because one of the field of the resource is invalid.","details":[{"#type":"type.googleapis.com/google.rpc.PreconditionFailure","violations":[{"type":"client_auth_config","subject":"?error_code=9&error_field_name=UpdateBrandWithMaskRequest.brand_id&error_field_value=0"}]}]}}.
Any suggestions on how to fix this is highly appreciated. I have contacted the google support about this issue as well, but as of now they're saying everything works on their end and clear cache and cookies but it doesn't work. I have attached here a capture of consent config wizard I'm using as well.
Put the Project ID in App Name
Try adding your support email to Firebase console. Go to firebase console->settings->General->Support Email->Add Email. Now while creating oAuth consent screen add same email id developer contact information as well as support email. It worked for me.
To expand on the top answer, there are numerous underlying reasons why this step of the app registration would fail. In the case where the application name is not valid (fails any of the checks that Google Cloud Platform enforces), then setting the application name to the project ID is guaranteed to fix the problem, as the project ID will always happen to be a valid application name.
It may be worth digging into the underlying validation error, which can be achieved by inspecting the network request that is sent upon submitting the form. In the "Network" tab of the Developer Tools, select the POST request that is captured after clicking the "SAVE AND CONTINUE" button. The "Response" tab (shown below for my case) should display an error object with a more descriptive message.
In my case, it seems that the application name was deemed abusive:
The request has been classified as abusive and was not allowed to proceed.
which I suspect is because it contains the word "Google".
What #Kalind said helped me to resolve the problem.
So login to firebase console, chose the project you are trying to create an OAuth Consent too. And then click settings-> General-> Support Email-> Add Email from dropdown.
Now when I go back to google cloud console under the Oauth consent screen, I can see that I have one registered to that project.
I had the same problem, indeed your App name must be identical to your Project ID that you chose when creating the project
I got the exact same error, probably an issue on their end :/
Thanks for reporting this everyone. I've also had the same problem for different apps and #Kalind suggestion fixes the problem. On Firebase project's settings there's a new field now called "Support email" where you can select your support email address. This will fix your issue like #Kalind and #Kasper said. I'm just adding a screenshot to make it more clear for those with the same problem.
Thanks!
For me there was an email in there already (owner of account email).
I had to invite another email > accept invite > change email > save > then change back > then I could proceed with the OAuth Consent Screen.
To change the support email on the Firebase Console you go to:
https://console.firebase.google.com/ > select Cog > Project Settings > General tab > Support Email
I reached this page is because of testing Google Login.
I faced this issue creating "OAuth consent screen".
But I didn't need this to create.
Just go to "Domain verification" page and "Add Domain".
There you may need to add 'txt record' in DNS Setting to prove you owned the domain.
After adding domain, go to "Credentials" page.
It is ready to choose the "Application type" like google guide
!!! pls enjoy !!!
I used the app Id as my App Name in the OAuth consent screen setup page.
If you are trying to use group email from gsuite in App consent/Firebase support, you must be the group owner, and do not need that group email address on any IAM role.
I believe the name of the application requesting access simply needs to be different from the name of the Google project.
This Error was come due to the project name is the same as the app name. So your app name and project name must be differnet
to expand on the helpful post of #zr0gravity7
I checked the 'response' in the developer con{"error":
{"code":3,"message":"com.google.apps.framework.request.BadRequestException:
At least one field must be updated."}}
I simply changed one field, and the save now succeeded.
(This is a very disappointing design of the form error checking)
The app name must be unique across Google. Modify the app name a bit.
When I access my site that's being managed by Sitecore, it's redirecting me and asking for Sitecore credentials. I have no idea why but obviously the main site should be viewable to public without needing creds.
Thanks.
This could be from your sitecore cookie still in page editor mode, To fix this add this query string to your URL:
?sc_mode=normal
This will update your cookie and no reddirect to login anymore
Assuming that you have a combined CM/CD environment and that this is specific to your computer or other authors' computers, it is likely that Sitecore is picking up on the fact that you were using the Page Editor in a previous session. When you are using Page Editor Sitecore will drop a cookie called website#sc_mode and set it to "edit". If you return to the page with that cookie set it will push you to the Login Page as it things you are attempting to edit that page.
To resolve this try clearing your cookies or using a browser in Incognito mode/Private Browsing.
If this is happening to other users I would suggest following Martijn's advice in the other Answer and checking your site definition.
Check your site definitions in the web.config and/or the sites.config in the /app_config/include/ folder. Most of the times there is some misconfiguration there.
Check the security roles set on your site pages. If for some reason access has been denied to the 'extranet/anonymous' user you won't be able to browse without being authenticated.
I've created ECM NewsLetter with some links to site (another Items). In online version of NewsLetter links works fine, but when I've sent this NewsLetter to my email and tried to click on links from my mail Inbox it's displays 404 not found error. Base URL - The default address for all links configured properly. What am I missing? Maybe some configuration? I appreciate any help you can provide.
Several things to check here:
Most likely source is that the campaign item that gets created when the email is sent is not published.
If the campaign is published then check the goal that gets installed as part of the ECM module is published: /sitecore/system/Marketing Center/Goals/Click Email Link
The way to test the source of the problem is to search for the guids in the link querystring - the ec_camp part of the querystringis the guid of the campaign. Search for this in your content delivery web databse - if this exists then check the goal mentioned above. The ec_as value is the value used to identify the user in the analytics db. This wont exist in your sitecore tree.
finally if both of the above work then follow this set up guide and ensure all the relevant ECM pages are installed properly on your CD servers - including the connection string to the ECM service that handles all tracking and link processing: http://www.sitecore.net/learn/blogs/technical-blogs/sitecore-magnified/posts/2013/09/ecm-on-cd.aspx
If you view source are they absolute links? If not one thing we did was create a newsletter device and detect we were coming from ecm. Then we could specify an alternative layout/sublayouts/data sources based on device.
The sublayouts could check if they were coming from a newsletter device and ensure they return all links absolute.
Within the ECM you need to make sure that you are saving and publishing as you move throughout the process of setting up and deploying a message. Once the message is edited, save and publish the message. Before dispatching, you should smart publish the target audience which in turn will re-publish the message. Then, when you dispatch you should see all the images.
This seems to be an issue with the configuration of Email Campaign Manager. Follow these steps
Go to Email Campaign Manager.
Select Content tab.
Check the value of Base URL- default address for all links field.
If it is set to some website URL other than your website URL change it to your website URL.
I was trying to disable sending email activation of activation. but it is not happening
What i tried is i copy the registration folder in to my project and by following How to disable email activation in django-registration app? answers i changed in the file but it is not happening .
i also done the same changes in the files of the folder
/usr/local/lib/python2.7/dist-packages/registration/
but still it is not stopping .
When i do register it is going the page that verification email is send and when i check in admin it is showing not activated .
Please suggest what can be problem
Instead of hacking, use SimpleBackend which doesn't send anything but registers user immediately.
I'm running a relatively fresh Django app that I haven't added much to. I tried to set up the admin (which I've done on plenty of other apps) to create some sample data while I build out the app, but whenever I try to log in with the super user account I created I get kicked back to the login screen.
When I enter incorrect credentials, I see the proper error message... I just can't get it to take me past the login screen to the admin when I have correct credentials. Has anyone else had this problem and been able to solve it? I'm at a dead end troubleshooting.
Check that SESSION_COOKIE_SECURE is not set while you are not using HTTPS.
Looks like your cookies are messed up. Please start with clearing cookies in browser. If it doesn't help you can also check if your cookies configuration for project is correct. List of settings for cookies configuration can be found here.
Use the below settings for the SESSION_COOKIE_DOMAIN:
SESSION_COOKIE_DOMAIN = "yourdomain.com"