To keep my app simple for now, I decided to use the drop-in auth flow by AWS Amplify, instead of creating my own sign-up/sign-in flow.

This is how my app AuthenticationActivity looks, using the drop-in auth for Android when creating a new user: Signup Screen

This is the AuthenticationActivity code:


import android.content.Intent;
import android.os.Bundle;
import android.util.Log;

public class AuthenticationActivity extends AppCompatActivity {

private final String TAG = AuthenticationActivity.class.getSimpleName();

protected void onCreate(Bundle savedInstanceState) {

    AWSMobileClient.getInstance().initialize(getApplicationContext(), new Callback<UserStateDetails>() {

        public void onResult(UserStateDetails userStateDetails) {
            Log.i(TAG, userStateDetails.getUserState().toString());
            switch (userStateDetails.getUserState()){
                case SIGNED_IN:
                    Intent i = new Intent(AuthenticationActivity.this, MainActivity.class);
                case SIGNED_OUT:

        public void onError(Exception e) {
            Log.e(TAG, e.toString());

private void showSignIn() {
    try {
    } catch (Exception e) {
        Log.e(TAG, e.toString());


In my case, I only need an email + password, so these are the rules I set up on AWS Cognito.

However, you can see that I have a few extra attributes generated by drop-in auth UI:

  • Given name
  • Phone number

I tried to leave these fields blank and register, but I get UI errors, of course. If I try to fill all the fields, I get an error, indicating that I am trying to send unauthorized attributes to AWS cognito.

UI errors on Signup Screen

So I went back to the Auth-drop documentation, but I figured out it is only possible to customize the drop-in auth background color and background image.

You can see it from AWS documentation:

I found no way to edit the attributes as to my liking for a simple use case like mine, and therefore I am forced to either:

  1. Change my AWS Cognito rules, forcing me to use a phone, name attribute, and username
  2. Write my own sign-in/sign-up

Am I missing something? Is there a way around it?


Username is mandatory but once you update your userpool settings from console to use email as the username, you can specify the email in the username field, set password and should be able to skip other fields while signing up.

  • 1
Reply Report
    • This is the correct answer. Once you change your user pool settings to use email and not username, you still must supply the email as the username to the Auth API for SignIn and SignUp.

@Ofir Bar - I believe you have set the username to be a mandatory field while creating the user pool. Check what's your selection under the section "How do you want your end users to sign in?" If you have checked username, then this is expected behavior. and "Which standard attributes are required?" - Uncheck everything if you just need email and password

  • 0
Reply Report
      • 2
    • I have unchecked everything. doing so, result in my user pool not authorizing me to try to register with "extra attributes" - this is the expected behavior. Meaning that if I fill up my entire "register" form, and adding a name, phone, etc, I will get an error indicating that Cognito only accepts username + password. So there is still no way to make the UI match the Cognito backend requirements without generating my own UI

Warm tip !!!

This article is reproduced from Stack Exchange / Stack Overflow, please click

Trending Tags

Related Questions