I can't sign in to Chromium browser

[Juan de Dios Becerra]

I am trying to use the new Push Messaging for Chrome(Chromium) and it is needed to be logged in the browser, I don't have problem with my account of gmail what can be 'some...@gmail.com', but if I want to login with the account of a company, for example 'some...@sanmina.com' only appear like is redirecting and never login, after a time like 30 seconds the page for login come back and the process did not work, I would like to know if there is a problem with the browser or is only my case. I am using arch linux and Chromium 27, I tried in Chrome 26 and the same result, Ocasinally I pass of the sing in stage but in the right corner I see a symbol of warning and the advice says that there waas an error that I have to sign in again but the problem persists.

I hope somebody can help me with that.

[Drew Wilson]

Your best bet is to log a bug at crbug.com. We can then follow up with you to gather any necessary information such as network traces.

Is this company configured to use their own SAML/SSO signin flow? If so, can you try signing in with an M28 dev channel build to see if this resolves the issue?

On Sat, May 25, 2013 at 5:09 PM, Juan de Dios Becerra <j.bece...@gmail.com> wrote:

I am trying to use the new Push Messaging for Chrome(Chromium) and it is needed to be logged in the browser, I don't have problem with my account of gmail what can be 'some...@gmail.com', but if I want to login with the account of a company, for example 'some...@sanmina.com' only appear like is redirecting and never login, after a time like 30 seconds the page for login come back and the process did not work, I would like to know if there is a problem with the browser or is only my case. I am using arch linux and Chromium 27, I tried in Chrome 26 and the same result, Ocasinally I pass of the sing in stage but in the right corner I see a symbol of warning and the advice says that there waas an error that I have to sign in again but the problem persists.

I hope somebody can help me with that.

--
--
Chromium Developers mailing list: chromi...@chromium.org
View archives, change email options, or unsubscribe:
http://groups.google.com/a/chromium.org/group/chromium-dev
 
 
 

[Juan de Dios Becerra]

The link you put crbug.com, I can not enter, maybe I am not understanding some concept. Effectively, the signing flow of the company is configured to use SSO but really I don't understand the flow internally. FInally I don't know what is M28 dev channel, I am going to explore, like you can see I don't know many things, I am new in these things, but I thank you all the help and orientation you and other users can give me.

[Roger Tawa]

Hi Juan,

You can enter a new bug for your problem by going to
https://code.google.com/p/chromium/issues/entry

You can test early versions of chrome using the dev channel. You can
get more information at
http://www.chromium.org/chrome-release-channels

I suggest you try the dev channel of chrome on a different machine if
possible, so that you can continue to use the stable version of chrome
on your current machine.

Thanks,
Roger

-


On Mon, May 27, 2013 at 10:48 AM, Juan de Dios Becerra

[Juan de Dios Becerra]

Thank you for your response, I will follow your suggestions.

[Juan de Dios Becerra]

One more question, there are links as the provided for Roger that work for Chrome?

[Juan de Dios Becerra]

FInally I could sing in to Chromium, I made an update to Chromium and Chrome and I can sign in with my sanmina account, I have only a warning in the Chrome menu button, the warning says "Sync Error: SIgn in again", but I sing in again and the notification does not disappear, I am thinking is a problem whit the managment of the account in the company, if you have some idea or information I would be thankful.

[Roger Tawa]

Hi Juan,

Best to open a bug at https://code.google.com/p/chromium/issues/entry
and continue to seek help there.

Thanks,
Roger

-


On Wed, May 29, 2013 at 1:29 PM, Juan de Dios Becerra

[Torne (Richard Coles)]

Does your build of Chromium have correct API keys? Without those sync and related services will not work, and they are not present by default when you build it.

[Juan de Dios Becerra]

How can I check these API keys? 

[Jói Sigurðsson]

If you've followed the instructions at
http://chromium.org/developers/how-tos/api-keys then you should have
API keys. If you're building a private build of Chromium, and you
haven't followed the instructions, then you don't have API keys.

If you've followed the instructions but still suspect that your API
keys are incorrectly set up, you can run a _debug_ build of Chromium
with this flag: --vmodule=google_api_keys=1

This will cause Chromium to log the API keys it is using, when they
are first accessed, e.g. if you try to log in or translate a page.

Cheers,
Jói


On Wed, May 29, 2013 at 8:19 PM, Juan de Dios Becerra

[Juan de Dios Becerra]

Sorry for this kind of questions but as you can see I am new in this, what do you mean with private build of Chromium? the process for the API keys only I did for an app that I am using, but not in general, sorry if I am doing kind of questions, I am trying to learn, and thank you for your help.

[Jói Sigurðsson]

Where does the Chrome (or Chromium) build you are having problems with
come from?

Is it an official Google Chrome build (in that case it will have the
multi-color logo, and typing about: into the address bar will show
something like "Google Chrome: 28.0.1500.20 (Official Build 201172)"?

Is it a Chromium build that you got with your Linux distribution? In
that case, which Linux distribution? Most of the major Linux
distributions have API keys baked into the Chromium builds they
distribute.

Or is it a version of Chromium that you built locally from source? It
is in this case that you need to specify API keys as per the
instructions I linked to, e.g. in your ~/.gyp/include.gypi file. If
you have done this for whatever reason, then as long as you have run [
gclient sync ] or [ gclient runhooks ] and then done another build,
your Chromium build should have keys.

Cheers,
Jói


On Thu, May 30, 2013 at 4:10 PM, Juan de Dios Becerra

[Juan de Dios Becerra]

Ok, I use Arch Linux 3.9.4-1, I think my Chromium build comes with this distribution, I update the system around once per week, my build of Chromium actually is 27.0.1453.93 (Build para desarrolladores 200836). So how cna check the API keys for this case?

[Jói Sigurðsson]

The Arch Linux package should come with API keys, so it sounds like
lack of API keys is not likely to be the underlying problem.

On Thu, May 30, 2013 at 5:11 PM, Juan de Dios Becerra

[Paweł Hajdan, Jr.]

Also, please report problems with the distro package to said distro. :)

Paweł

[Juan de Dios Becerra]

What distro package do you mean?

[Daniel Cheng]

Note that it's not sufficient to just have API keys. The API console project associated with those API keys needs to have all the correct permissions enabled.

Daniel

[Paweł Hajdan, Jr.]

Juan, you've just said you are using Chromium package from Arch Linux. Please report any problems with it to Arch Linux.

Paweł