It appears to me this bug is only presented when we log in to AppSheet editor for APAC region.
When we select the option for Authentification Provider , we only have option of "Any Provider " or “Google”.
Under the normal global account, it is presented like this.
Could you fill this gap, i.e. fix a bug in APAC region editor?
Thank you.
We are awaiting for your feedback.
To make the story worse, we set this option as “Any Provider”. However, once the users open this app, they are asked to log in with Google auth, no other service providers services are not listed. This is another bug. Kindly investigate and fix quickly.
Hello @Koichi_Tsuji,
I apologize for the delay. I did some research and I found that If Microsoft, Apple, Dropbox, Smartsheet, Box, and Salesforce are missing from your available sign-in options, it is usually because your AppSheet account is currently isolated to a single provider or your app’s data tables are locked into a single ecosystem.
AppSheet may restrict authentication options based on how your account was created and how your tables are linked.
To validate and fix this:
Log in with a Google Workspace Domain Account.
As an administrator, look into your Google Workspace Admin Console under AppSheet settings to lift authentication restrictions.
Please let me know.
@Jose_Arteaga, @Koichi_Tsuji is a long-time, well-experienced AppSheet app creator. His post here does not reflect a lack of understanding of how AppSheet works. He is reporting a bug that should be escalated to Engineering. Your own response appears to reflect an incomplete reading or understanding of his posts.
I understand. I will go ahead and report this to the engineering team then.
Update: I have created a bug for this. I will keep you posted with any updates.
Thank you, @Jose_Arteaga!!!
Thanks for both of you!
As Steve suspected, the advice from Jose was not making sense. Our GWS setting for AppSheet security has been lifted from day ONE.
@Jose_Arteaga Could you please keep asking Engineering team to investigate throughly to fix this bug.
While we are setting up new app under APAC region, we are encountering another issue. We set up Amazon Cognito as domain auth source. The setting was exactly the same as Global region apps, but the user is unable to access to the app, instead they are prompted to the following error message.
This should be caused the possible glitch adhered to the APAC regions applications. Could you please raise another ticket to address this new issue?
We have tested with Cognito, OKTA, OpenID for auth domains. However, all of them have failed under APAC deployed app. Reading logs for those service, log in itsself is ended up successfully. However, once the log in details such as email account, passward was supplied and log in was pushed, then domain auth services returns “Email Verified”, but the problem sees to me that AppSheet is trying to find the target application only from the GLOBAL region app, so we are always seeing “App not found Your account XXXXi@outlook.com does not have access to this app or it no longer exists. Try contacting the app owner.” message at the end. AppSheet is not checking the target apps which are deployed under APAC region.
It appears to me that when the APAC region was GAed, it was not look after this part of “Domain Authentification” . Could you please escalate internally?
Accodring to the docs, the OpenID connect should be available for APAC region as highlighted below, but in reality, it is not for now.
Thanks @Koichi_Tsuji,
I checked on the bug reported yesterday and it has been assigned to the support team. I will go ahead and add these new notes to the ticket.
Hello @Koichi_Tsuji,
I have received a response from the support team.
Please note that AppSheet app data is subject to the laws of the country in which it is stored and data privacy and security protections can vary by region.
Having said that, only Google providers are supported to authenticate AppSheet sign-ins in the Asia Pacific (Preview) or EU region.
Please click here for further information on Manage AppSheet data residency where you will also find possible workarounds.
Please let me know if you need any further details.
Understood the only Google as auth provider is avaialble for both APAC and EU region apps due to legal constrains. However, as the same document indicates, i.e. the OpenID connector SHOULD work for both APAC and EU regions, currently it is not working as I reported earlier.
Could you explain why this is caused and how to fix? or is it a bug where your engineering teams are looking into now?
Any news for it ?
Hello @Koichi_Tsuji,
Thanks for following up. I made the question to the engineering team. i checked and we do not have a response yet.
I’ll keep you posted.
Any news for it ?
Hello @Koichi_Tsuji,
I have not heard back from the engineering team, I just pinged them again.
I will keep you posted.
Could you get a single word to see how it goes… After a while, we are not getting any feedback at all. You know we have a ongoing project and this issus is pretty much critical. Google s late respons is killing our opportunity. Anyway, please get a single word first of all so that we can see how your dev team stands on this issue now.
Hello @Koichi_Tsuji,
I insisted today and I got confirmation from the engineering team that this is a documentation error. They will be updating the page accordingly.
I will follow up and keep you posted.
