There Was a Problem in Getting the Ui Customization Please Try Again Cognito

AWS Cognito is a service provided by Amazon Web Services, and is bachelor in AppSheet Business concern Subscriptions. It allows y'all to fix your own authentication source. Yous can provision users with explicit passwords or using one of their existing social sig nin accounts, and you employ Cognito to control secure access to your AppSheet apps. There are three reasons to do this:

You lot would similar to manage user access command at a scale that goes beyond elementary let lists.
You desire to be able to provision and manage the users, control password policy, and utilise other richer characteristics of an hallmark source.
Yous cannot use your corporate domain controller every bit an auth source, because your users come up from outside your corporate domain.

Using AWS Cognito requires that y'all ready an AWS account. This is not part of the AppSheet service. This article explains the nuts of setting up a Cognito service and configuring it to exist accessible from your AppSheet account.

Stride 1: Open the Cognito service in AWS

Become to http://aws.amazon.com, sign in to the console, and navigate to Cognito past typing it into the Find Services search bar.

Open Cognito service in AWS by typing Cognito into the Find Services search bar

Stride 2: Configure a user puddle in your Cognito service

Click Manage User Pools.

Manager User Pools button in the Amazon Cognito dialog

Then, click Create a user pool.

Your User Pools page with Create a user pool button highlighted

In the next few steps, nosotros will create and configure a User Puddle. The users in the User Puddle will define the people who accept admission to your app.

Stride 2a: Give your app a name

You can create every bit many user pools as you need. Some app creators choose to make a user pool for each app. Others choose to use a unmarried user pool to multiple apps. Whatever your use instance, choose a proper noun that will assist you know what app(s) this user pool applies to. So, click Step through settings.

Create a user pool dialog with App XYZ in the Pool name field and the Step through settings link highlighted

Step 2b: Select sign in method

Select how you will let users to sign in. AppSheet recommends having users sign in using email. Since email addresses are unique, they work really well inside apps as unique identifiers. The e-mail each user signs up with will exist attainable inside your app using the USEREMAIL() formula.

You tin require users to enter boosted information under Which standard attributes exercise you want to require? These standard attributes volition be visible in the Cognito User Pool. However, the standard attributes are non accessible from inside AppSheet apps.

How do you want your end users to sign in with the Email addresses or phone number item selected and the name field marked as required under Which standard attributes do you want to require?

Footstep 2c: Set password requirements

On this screen yous can choose what requirements to apply to passwords. Also, you lot tin choose whether users tin can sign upward themselves.

If you allow users to sign up themselves, and so new users will see a sign up link the starting time time they access the app. Clicking the link will have them to a sign upwards page where they can create a user profile. This would permit anyone with a link to the app to sign upward.

If you lot simply allow administrators to create users, then the sign up link volition be hidden. An admin with access to the AWS Cognito account will demand to add together the user to the User Pool. This volition send an automatic email to the user with their temporary password. The user will be prompted to change their password on starting time sign in.

Maximum length is set to 8 and all options are selected under What password strength do you want to require? And Allow users to sign themselves up is selected under Do you want to allow users to sign themselves up?

Step 2d: Crave user verification

Multi-gene authentication and SMS message are both optional.

AppSheet strongly recommends verifying the user information.

Email is selected under Which attributes do you want to verify? The New Role Name field is set to AppXYZ-SMS-Role under You must provide a role to allow Amazon Cognito to send SMS messages

Footstep 2e: Email accost customization

You lot can customize the email accost from which automated emails will exist sent. This is optional, just recommended past AWS as a best practice.

Do you want to customize your email address? screen

Footstep 2f: Email message customization

You tin can customize the automatic email messages. These fields accept standard HTML tags. If you want to add together a line pause, you can use the HTML tag: <br />

Screen available for customizing email verification and user invitation messages

Step 2g: Add tags

Tags are optional and not used for basic setups. For more information about tags, encounter the Amazon assistance doc Tagging Amazon Cognito resource.

Do you want to add tags for this user pool? with the Next step button highlighted and no tags added

Step 2h: Remember user's devices

Remembering a user's device is as well optional. Nosotros recommend that you lot set this option to No. Once sign-in occurs, AppSheet remembers the user fifty-fifty if the app is closed or the device is restarted. It is only if the user explicitly logs off AppSheet that the Cognito authentication is requested again. At this phase, yous would normally desire to make sure the sign-in process occurs once again. If you enquire Cognito to remember the user's devices, then Cognito volition curt-circuit the sign-in process and automatically sign-in the existing user. This is commonly not the desired beliefs.

Do you want to remember your user

Footstep 2i: Add an app client

Click to Add an app client. When you define an app client in Cognito, yous are telling Cognito to expect AppSheet to interact with it to enquire users to sign in.

Give your App Client a name and check the box to generate client hole-and-corner. So, click Create app client. Cognito volition create a Client Id and a Client Undercover, which y'all can admission afterward setup is complete. You lot will need this information when configuring your app back in AppSheet.

Information technology is important that yous practise not check the second option (Only allow ....). This will preclude the standard OAuth2.0 authentication procedure from succeeding.

App client name field is set to AppSheet, the Generate client secret option is selected, and Create app client button is highlighted in the Which app clients will have access to this user pool?

Step 2j: Triggers

Triggers are an advanced pick that allow y'all to further customize the authentication process. They are optional and not required for the basic setup.

Pace 2k: Review

Review your settings and click Create pool.

Pace 2l: Set the callback URLs

Navigate to App client settings in the left-hand carte. These settings allow us to tell Cognito how to reply when AppSheet interacts with it.

Re-create the post-obit callback URLs and paste them in the Callback URL(due south) field. They are case sensitive and must be separated by a comma and a space.
https://world wide web.appsheet.com/Account/ELC, http://localhost:53519/Account/ELC

Note the second callback URL is non strictly required --- it is only necessary if y'all request AppSheet to debug your awarding at some point in the future.

Select Cognito User Pool under Enabled Identity Providers, enter the callback URLs, and select Authorization code grant for Allowed OAuth Flows, and email, openid, and profile for Allowed OAuth Scopes in the What identity providers and OAuth 2.0 settings should be used for your app clients?

Stride 2m: Define the domain for your Cognito user pool

Navigate to Domain name in the lefthand menu. You can assign a real domain or a false domain (for instance, appsheettest in the example below).

You volition need the total domain that is, https://{yourdomainname}/auth/{AWS region}/amazoncognito.com) when configuring your app in AppSheet.

Pace 3: Configure your AppSheet account

Now that you lot accept set up upwardly your Cognito User Pool, you demand to register it in your AppSheet account. Do so from the My Account > Integrations > Auth Domains pane.

Step 3a: Add a new auth domain

Click + New Auth Domain, give your auth domain a proper name, and select AWS Cognito as the provider

Footstep 3b: Configure the domain with the Cognito information

The App Client ID and App Client Undercover come up from the App clients page in the left-hand menu of the Cognito settings dashboard. The Domain Endpoint comes from the Domain name page in the lefhand menu of the Cognito settings dashboard.

Add Cognito configuration dialog with App Client Id, App Client Secret, and Domain Endpoint fields hightlighted

Step four: Configure your app

Yous can now utilise this domain auth source in any of your apps. To connect your app to the auth source:

Open up your app in the editor.
Get to the Security > Domain Authentication pane.
Enable the Require domain authentication option.
Select the domain source created in pace iii in the Authentication domain source drop-down.

Note that when AppSheet does not currently support the ability to select an Hallmark domain or Authentication group when working with Cognito. These options tin exist left at their default values.

Pace 5: Test it

Open the Share dialog and re-create the browser link. See Send users a link to your app. Open a new private session in your browser (incognito in Chrome), and paste the URL. You will run across the option to authenticate with Cognito.

Option to sign in with AWS Cognito

Additional UI customization

Cognito allows yous to customize the look and feel of the sign in page. Access these settings past going to the UI customization folio in the left-hand carte du jour of the Cognito settings dashboard.

wallsblarand02.blogspot.com

Source: http://help.appsheet.com/en/articles/2424111-user-access-control-via-aws-cognito