Question:
I’ve been going through the AWS Amplify docs and tutorials for how to use Amplify and Cognito identity pools together with UNauthenticated users. The example given by the Amplify docs is:
|
1 2 3 4 5 6 7 8 9 10 11 12 13 14 |
Amplify.Auth.fetchAuthSession( result -> { AWSCognitoAuthSession cognitoAuthSession = (AWSCognitoAuthSession) result; switch(cognitoAuthSession.getIdentityId().getType()) { case SUCCESS: Log.i("AuthQuickStart", "IdentityId: " + cognitoAuthSession.getIdentityId().getValue()); break; case FAILURE: Log.i("AuthQuickStart", "IdentityId not present because: " + cognitoAuthSession.getIdentityId().getError().toString()); } }, error -> Log.e("AuthQuickStart", error.toString()) ); |
But in practice when I use this code – I get an error printed out in LogCat:
|
1 2 |
AuthQuickStart: FAILURE IdentityId not present because: AmplifyException {message=You are currently signed out., cause=null, recoverySuggestion=Please sign in and reattempt the operation.} |
Note: I did configure AWS Cognito to support Unauthenticaed users!
I’ve also looked everywhere for the Amplify Android API doc to see what other APIs are supported – couldn’t find any Android API docs.
And looking into the AWS Amplify.Auth methods i could not find ANY function that deals with unauthenticated users
Question:
Any clue how can i use Amplify (Android) and have AWS credentials via AWS Cognito for unauthenticated users ???
Answer:
This is David from the Amplify Android team. I was actually just looking into this the other day and currently there’s a hack that’s required to make unauth users work.
After setting up unauth/guest users through the CLI (as you mentioned you had) you have to call the getAWSCredentials method on the underlying escape hatch once for the app to get it to work.
Here’s a code snippet I’d written that you can run after Amplify.configure (and again, this only needs to be run once per app install):
|
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 |
AWSMobileClient mobileClient = (AWSMobileClient) Amplify.Auth.getPlugin("awsCognitoAuthPlugin").getEscapeHatch(); mobileClient.getAWSCredentials(new Callback @Override public void onResult(AWSCredentials result) { // Now you'll see the Identity ID and AWSCredentials in the resulting auth session object. Amplify.Auth.fetchAuthSession( result2 -> Log.i(TAG, result2.toString()), error -> Log.e(TAG, error.toString())); } catch (InterruptedException e) { e.printStackTrace(); } } @Override public void onError(Exception e) { // Handle the error however is best for your app } }); |
I’m working on a solution to avoid this hack right now and adding a documentation section on Unauth users to our site but in the meantime this should get it working for you.
Again note you only have to do this once and from then on out, it should just work when you call fetchAuthSession.
UPDATE: The non patched (official) version:
|
1 2 3 4 5 6 7 8 9 10 11 12 13 14 |
Amplify.Auth.fetchAuthSession( result -> { AWSCognitoAuthSession cognitoAuthSession = (AWSCognitoAuthSession) result; switch (cognitoAuthSession.getIdentityId().getType()) { case SUCCESS: Log.i(TAG, "identity: " + cognitoAuthSession.getIdentityId().getValue()); Log.i(TAG, "credentials: " + cognitoAuthSession.getAWSCredentials().getValue();); break; case FAILURE: Log.i(TAG, "FAILURE IdentityId not present because: " + cognitoAuthSession.getIdentityId().getError().toString()); } }, error -> Log.e(TAG, "UNAUTH USERS ERR: " + error.toString())); |