Assigned
Status Update
Comments
ju...@google.com <ju...@google.com> #2
Thanks for reporting this, and I've done some research and find that "Google enforces a real name policy on G+ accounts. Your test account may be blocked from G+ if the name does not look real." at [1]. Then after some tests, I can confirm that it will only work if the Google account you provided should have been G+ verified (with proper G+ setup), but still need to retry after the first failed attempt and it eventually will work.
[1]https://cloud.google.com/security-scanner/using-the-scanner#creating_a_scan
[1]
an...@delonghigroup.com <an...@delonghigroup.com> #3
Hi,
thank you for your answer.
After reading the note you pointed out:
"Note that Google enforces a real name policy on G+ accounts. Your test account may be blocked from G+ if the name does not look real."
I have to tell you that we don't have G+ service enabled on our enterprise accounts, thus from what I can understand from the manual, such statement does not apply.
In my organization there are thousands of G-Suite administrated accounts but very few of them are enabled to G+ service. It's just a service we don't make use of.
I'll tell you more: for performing Security Scans, I created a no-license account (which means it's only got an email address, security settings, and 30GB space but no mail, etc - you know) because there's no need for other services for such purpose.
You say we need to property setup G+, but the guide doesn't explicitly talk about it. Are you sure we shall do it?
thank you for your answer.
After reading the note you pointed out:
"Note that Google enforces a real name policy on G+ accounts. Your test account may be blocked from G+ if the name does not look real."
I have to tell you that we don't have G+ service enabled on our enterprise accounts, thus from what I can understand from the manual, such statement does not apply.
In my organization there are thousands of G-Suite administrated accounts but very few of them are enabled to G+ service. It's just a service we don't make use of.
I'll tell you more: for performing Security Scans, I created a no-license account (which means it's only got an email address, security settings, and 30GB space but no mail, etc - you know) because there's no need for other services for such purpose.
You say we need to property setup G+, but the guide doesn't explicitly talk about it. Are you sure we shall do it?
ju...@google.com <ju...@google.com> #4
Thank you for your last message, and I've done further research at my end afterwards. Currently I've confirmed with the engineering that they're aware of this and they're working toward a solution to this issue. Future updates regarding this will be posted here on this thread by the engineering.
an...@delonghigroup.com <an...@delonghigroup.com> #5
Hi, are there any news related to this issue?
Description
A) "Authentication error. Please log in", where "log in" is blue text (a link)
B) "Could not sign in using the provided username and password"
Message A only shows up the first time I try to click on Create. Successive retries of clicking Create without leaving the form won't show this. It disappears and gets replaced very quickly by the Message B.
Even if, as stated, message A quickly disappears, after a few tries I managed to click on it. It took me to a Google login page where my personal username was already provided and only my password was requested. I entered my password and correctly logged in. Then it just took me back to the Create Security Scan page, which threw the Message B as usual.
Please notice that:
- The provided Security Scan Google account exists, is active, has no 2FA enforced nor active, has accepted the terms&conditions and the password is correct.
- The provided Security Scan Google account differs from the account I'm using to login to GCP console to create this Security Scan.
- I can successfully create and run new Security Scans for the same project if specifying Authentication: none.
Thank you for assisting on this issue
Antonio