-
Bug
-
Resolution: Fixed
-
High
-
29
-
Severity 3 - Minor
-
14
-
Summary
When using the Google Drive macro, if the logged user is not the author/owner of the document, a message to "authenticate/Sign in as the user" will be displayed, with a Sign in to Google button. Due to not having options to see the document directly in Confluence, the user will need to authenticate.
Recently, if the user clicks on this button, the following message will be displayed:
Sign in with Google temporarily disabled for this app - This app has not been verified yet by Google in order to use Google Sign In.
Environment
- Confluence Cloud
- Google Drive for Confluence add-on
Steps to Reproduce
- Make sure to install the Google Drive Macro for Confluence
- After that, when editing a page, insert a Google Sheets with a valid URL for a spreadsheet in the user's drive.
- Once added to the page, click on Publish to save the changes
- Observe the message and click on Sign in to Google
Expected Results
The user should be able to authenticate and see the document, based on Google's permission.
Actual Results
The user is asked to authenticate. After that, a warning screen is shown saying the App is not verified by Google.
Workaround
There is no workaround at the moment.
- is duplicated by
-
-
- Closed
-
[CONFCLOUD-59617] Google Drive for Confluence add-on is not verified by google
Esther Disbot
added a comment - It is now working for all the users in my org.
However to note, I also think I may have found a workaround:
Previously the google sheets document I had embedded into Confluence via the Google Drive Add-on was set to "anyone at my company can view" the document with the link. Prior to updating the add-on (before Anand commented that there was an app update with fix), I changed the share settings on my GDrive documents to "anyone at my company can find and view" and my users were able to view the google drive files in confluence even before I updated the app with the fix
Esther Disbot
added a comment - It is now working for all the users in my org.
However to note, I also think I may have found a workaround:
Previously the google sheets document I had embedded into Confluence via the Google Drive Add-on was set to "anyone at my company can view" the document with the link. Prior to updating the add-on (before Anand commented that there was an app update with fix), I changed the share settings on my GDrive documents to "anyone at my company can find and view" and my users were able to view the google drive files in confluence even before I updated the app with the fix Hello all,
We have finally got a positive response from Google. The app has been verified and a new version has been launched in the Atlassian Marketplace. The new version is 1.0.33-AC. Please update the app and verify whether the problem is resolved.
Thanks for your patience.
Ditto - we are having the issue same. Several users cannot see the shared file, while only the owner can. Please help!
Esther Disbot
added a comment - Thank you for the background and information. I look forward to hearing about an ETA or fix soon. Thanks again!
Esther Disbot
added a comment - Thank you for the background and information. I look forward to hearing about an ETA or fix soon. Thanks again! esther89 We have/are following up with Google for verifying this soon and have also brought to their notice that the delay is adversely affecting our business. But we do not have an ETA from them yet. We have also tried to communicate through some other channels in an effort to reach out to them. We are still waiting for a response.
Marty Rinehart
added a comment - ^ Can we get an ETA on the release? It looks like this has been in "Awaiting Release" for some time.
Additionally, @anandkashyap sent me a comment on 6/20 saying that this would hopefully be fixed by the week of 6/25. I know this fix involves several teams however, could we at least get an ETA?
Esther Disbot
added a comment - - edited Can we get an ETA on the release? It looks like this has been in "Awaiting Release" for some time.
Additionally, @anandkashyap sent me a comment on 6/20 saying that this would hopefully be fixed by the week of 6/25. I know this fix involves several teams however, could we at least get an ETA? Ditto to what Esther and Craig mentioned; some users are able to see even though they are not the authors while other receives the error message. We've hit this roadblock with newly onboarded agents, as well as agents who have been with the org for years...
Works like a charm now
Thanks for the persistence and support.