Amazon Cognito Authentication
What you'll learn
- How to implement Amazon Cognito authentication in Cypress
- How to securely manage authentication processes for Cypress end-to-end testing scenarios
Amazon Cognito is an authentication provider apart of Amazon Web Services (AWS).
The documentation for Amazon Cognito recommends using the AWS Amplify Framework Authentication Library from the AWS Amplify Framework to interact with a deployed Amazon Cognito instance. Using the AWS Amplify Framework Authentication Library, we are able to programmatically drive the creation and authentication of users against a fully deployed back end.
This guide illustrates the limited code from the AWS Amplify Framework needed to programmatically log an existing a user into an application.
- Amplify v5.x.x
- Amplify v6.x.x
// Add 'aws-amplify' library into your application
import Amplify, { Auth } from 'aws-amplify'
// Configure Auth category with your Amazon Cognito credentials
Amplify.configure({
Auth: {
identityPoolId: 'XX-XXXX-X:XXXXXXXX-XXXX', // Amazon Cognito Identity Pool ID
region: 'XX-XXXX-X', // Amazon Cognito Region
},
})
// Call Auth.signIn with user credentials
Auth.signIn(username, password)
.then((user) => console.log(user))
.catch((err) => console.log(err))
import { Amplify } from "aws-amplify";
import { fetchAuthSession, signIn } from "aws-amplify/auth";
Amplify.configure({
Auth: {
Cognito: {
userPoolId: "XX-XXXX-X_XXXXXXXXX",
userPoolClientId: "XXXXXXXXXXXXXXXXXXXXXXXXX",
// OR:
identityPoolId: 'XX-XXXX-X:XXXXXXXX-XXXX', // Amazon Cognito Identity Pool ID
},
},
});
signIn({ username, password, { authFlowType: "USER_PASSWORD_AUTH" } })
// eslint-disable-next-line @typescript-eslint/no-unused-vars
.then((_signInOutput) => fetchAuthSession())
.then((authSession) => console.log(authSession))
.catch((err) => console.log(err));
Amazon Cognito Setup
If not already setup, you will need to create an account with Amazon Web Services (AWS).
An Amazon Cognito integration is available in the
Real World App (RWA). Clone the Cypress Real World App and install the AWS Amazon Amplify CLI as follows:
npm install @aws-amplify/cli --global
The
Real World App (RWA) is configured with an optional Amazon Cognito instance via the AWS Amplify Framework Authentication Library. The AWS Amazon Amplify CLI is used to provision the Amazon Web Services (AWS) infrastructure needed to configure your environment and cloud resources.
First, run the amplify init command to initialize the Real World App. This will provision the project with your AWS credentials.
amplify init
Next, run the amplify push command to create the Amazon Cognito resources in the cloud:
amplify push
Use the yarn dev:cognito
command when starting the
Real World App.
Setting Amazon Cognito app credentials in Cypress
First, we need to configure Cypress to use the
AWS Cognito environment variables set in the
.env
file. In addition, we are using the aws-exports.js
supplied during the
AWS Amplify CLI build process.
- cypress.config.js
- cypress.config.ts
const { defineConfig } = require('cypress')
// Populate process.env with values from .env file
require('dotenv').config()
// AWS exports
const awsConfig = require('./aws-exports-es5.js')
module.exports = defineConfig({
env: {
cognito_username: process.env.AWS_COGNITO_USERNAME,
cognito_password: process.env.AWS_COGNITO_PASSWORD,
awsConfig: awsConfig.default,
},
})
import { defineConfig } from 'cypress'
// Populate process.env with values from .env file
require('dotenv').config()
// AWS exports
const awsConfig = require('./aws-exports-es5.js')
export default defineConfig({
env: {
cognito_username: process.env.AWS_COGNITO_USERNAME,
cognito_password: process.env.AWS_COGNITO_PASSWORD,
awsConfig: awsConfig.default,
},
})
Custom Command for Amazon Cognito Authentication
There are two ways you can authenticate to AWS Cognito:
Login with cy.origin()
We'll write a custom command called loginByCognito
to perform a login to
Amazon Cognito. This command will use
cy.origin()
to
- Navigate to the Cognito origin
- Input user credentials
- Sign in and redirect back to the Real World App (RWA)
- Cache the results with
cy.session()
// Amazon Cognito
const loginToCognito = (username: string, password: string) => {
Cypress.log({
displayName: 'COGNITO LOGIN',
message: [`🔐 Authenticating | ${username}`],
autoEnd: false,
})
cy.visit('/')
cy.origin(
Cypress.env('cognito_domain'),
{
args: {
username,
password,
},
},
({ username, password }) => {
cy.contains('Sign in with your email and password')
// Cognito log in page has some elements of the same id but are off screen.
// We only want the visible elements to log in
cy.get('input[name="username"]:visible').type(username)
cy.get('input[name="password"]:visible').type(password, {
// use log: false to prevent your password from showing in the Command Log
log: false,
})
cy.get('input[name="signInSubmitButton"]:visible').click()
}
)
// give a few seconds for redirect to settle
cy.wait(2000)
// verify we have made it passed the login screen
cy.contains('Get Started').should('be.visible')
}
// right now our custom command is light. More on this later!
Cypress.Commands.add('loginByCognito', (username, password) => {
return loginToCognito(username, password)
})
Now, we can use our loginByCognito
command in the test. Below is our test to
login as a user via Amazon Cognito, complete
the onboarding process and logout.
The runnable version of this test is in the
describe('Cognito, cy.origin() login', function () {
beforeEach(function () {
// Seed database with test data
cy.task('db:seed')
// login via Amazon Cognito via cy.origin()
cy.loginByCognito(
Cypress.env('cognito_username'),
Cypress.env('cognito_password')
)
})
it('shows onboarding', function () {
cy.contains('Get Started').should('be.visible')
})
})
Now, we can refactor our login command to take advantage of
cy.session()
to store our logged in user so we don't
have to reauthenticate with every test.
// Amazon Cognito
Cypress.Commands.add(
'loginByCognito, cy.origin() login',
(username, password) => {
cy.session(
`cognito-${username}`,
() => {
return loginToCognito(username, password)
},
{
validate() {
cy.visit('/')
// revalidate our session to make sure we are logged in
cy.contains('Get Started').should('be.visible')
},
}
)
}
)
Programmatic Login
Next, we'll write a command to perform a programmatic login into
Amazon Cognito and set items in localStorage
with the authenticated users details, which we will use in our application code
to verify we are authenticated under test.
In this loginByCognitoApi
command, we call Auth.signIn
, then use that
response to set the items inside of localStorage for the UI to know that our
user is logged into the application.
- Amplify v5.x.x
- Amplify v6.x.x
import Amplify, { Auth } from 'aws-amplify'
Amplify.configure(Cypress.env('awsConfig'))
// Amazon Cognito
Cypress.Commands.add('loginByCognitoApi', (username, password) => {
const log = Cypress.log({
displayName: 'COGNITO LOGIN',
message: [`🔐 Authenticating | ${username}`],
// @ts-ignore
autoEnd: false,
})
log.snapshot('before')
const signIn = Auth.signIn({ username, password })
cy.wrap(signIn, { log: false }).then((cognitoResponse) => {
const keyPrefixWithUsername = `${cognitoResponse.keyPrefix}.${cognitoResponse.username}`
window.localStorage.setItem(
`${keyPrefixWithUsername}.idToken`,
cognitoResponse.signInUserSession.idToken.jwtToken
)
window.localStorage.setItem(
`${keyPrefixWithUsername}.accessToken`,
cognitoResponse.signInUserSession.accessToken.jwtToken
)
window.localStorage.setItem(
`${keyPrefixWithUsername}.refreshToken`,
cognitoResponse.signInUserSession.refreshToken.token
)
window.localStorage.setItem(
`${keyPrefixWithUsername}.clockDrift`,
cognitoResponse.signInUserSession.clockDrift
)
window.localStorage.setItem(
`${cognitoResponse.keyPrefix}.LastAuthUser`,
cognitoResponse.username
)
window.localStorage.setItem('amplify-authenticator-authState', 'signedIn')
log.snapshot('after')
log.end()
})
cy.visit('/')
})
import { Amplify } from 'aws-amplify'
import { fetchAuthSession, signIn } from 'aws-amplify/auth'
Amplify.configure(Cypress.env('awsConfig'))
const fetchJwts = async (username: string, password: string) => {
const options = { authFlowType: 'USER_PASSWORD_AUTH' as const }
await signIn({ username, password, options })
const authSession = await fetchAuthSession()
const tokens = authSession.tokens!
const accessToken = tokens.accessToken
const accessTokenPayload = accessToken.payload
return {
idToken: tokens.idToken!.toString(),
accessToken: accessToken.toString(),
clientId: accessTokenPayload.client_id as string,
accessTokenSub: accessTokenPayload.sub!,
}
}
type JwtResponse = Awaited<ReturnType<typeof fetchJwts>>
// Amazon Cognito
Cypress.Commands.add(
// eslint-disable-next-line @typescript-eslint/ban-ts-comment
// @ts-ignore
'loginByCognitoApi',
(username: string, password: string) => {
const log = Cypress.log({
displayName: 'COGNITO LOGIN',
message: [`🔐 Authenticating | ${username}`],
autoEnd: false,
})
log.snapshot('before')
cy.wrap(fetchJwts(username, password), { log: false }).then(
(unknownJwts) => {
const { idToken, accessToken, clientId, accessTokenSub } =
unknownJwts as JwtResponse
const keyPrefix = `CognitoIdentityServiceProvider.${clientId}`
const keyPrefixWithUsername = `${keyPrefix}.${accessTokenSub}`
const ls = window.localStorage
ls.setItem(`${keyPrefixWithUsername}.idToken`, idToken)
ls.setItem(`${keyPrefixWithUsername}.accessToken`, accessToken)
ls.setItem(`${keyPrefix}.LastAuthUser`, accessTokenSub)
log.snapshot('after')
log.end()
}
)
}
)
Finally, we can use our loginByCognitoApi
command in at test. Below is our
test to login as a user via Amazon Cognito,
complete the onboarding process and logout.
The runnable version of this test is in the Real World App (RWA).
describe('Cognito, programmatic login', function () {
beforeEach(function () {
// Seed database with test data
cy.task('db:seed')
// Programmatically login via Amazon Cognito API
cy.loginByCognitoApi(
Cypress.env('cognito_username'),
Cypress.env('cognito_password')
)
})
it('shows onboarding', function () {
cy.contains('Get Started').should('be.visible')
})
})
Adapting an Amazon Cognito App for Testing
Often times, AWS Cognito is used when other AWS services provide the backend, such as AWS AppSync for GraphQL APIs or AWS API Gateway for REST APIs. These backend services can be configured to verify cognito JWTs without additional code. However, if you are hosting a webserver backend, like the cypress real-world app does with the Express npm library, it must be adapted, as the real-world app is, to verify the Cognito JWTs to authorize the frontend's requests.
The
Real World App (RWA) is used and provides configuration and runnable code for both the React SPA and the Express back end.
The front end uses the AWS Amplify Framework Authentication Library. The back end uses the express-jwt to validate JWTs from Amazon Cognito.
Adapting the back end
In order to validate API requests from the frontend, we install express-jwt and jwks-rsa and configure validation for JWT's from Amazon Cognito.
- Amplify v5.x.x
- Amplify v6.x.x
// ... initial imports
import jwt from 'express-jwt'
import jwksRsa from 'jwks-rsa'
// ...
const awsCognitoJwtConfig = {
secret: jwksRsa.expressJwtSecret({
jwksUri: `https://cognito-idp.${awsConfig.aws_cognito_region}.amazonaws.com/${awsConfig.aws_user_pools_id}/.well-known/jwks.json`,
}),
issuer: `https://cognito-idp.${awsConfig.aws_cognito_region}.amazonaws.com/${awsConfig.aws_user_pools_id}`,
algorithms: ['RS256'],
}
export const checkCognitoJwt = jwt(awsCognitoJwtConfig).unless({
path: ['/testData/*'],
})
// ... initial imports
import jwt from 'express-jwt'
import jwksRsa from 'jwks-rsa'
// ...
const userPoolId = awsConfig.Auth.Cognito.userPoolId
const region = userPoolId.split('_')[0]
const awsCognitoJwtConfig = {
secret: jwksRsa.expressJwtSecret({
jwksUri: `https://cognito-idp.${region}.amazonaws.com/${userPoolId}/.well-known/jwks.json`,
}),
issuer: `https://cognito-idp.${region}.amazonaws.com/${userPoolId}`,
algorithms: ['RS256'],
}
export const checkCognitoJwt = jwt(awsCognitoJwtConfig).unless({
path: ['/testData/*'],
})
Once this helper is defined, we can use globally to apply to all routes:
// initial imports ...
import { checkCognitoJwt } from './helpers'
// ...
if (process.env.REACT_APP_AWS_COGNITO) {
app.use(checkCognitoJwt)
}
// routes ...
Adapting the front end
We need to update our front end React app to allow for authentication with Amazon Cognito using the AWS Amplify Framework Authentication Library.
First, we create a AppCognito.tsx
container, based off of the App.tsx
component.
A useEffect
hook is added to get the access token for the authenticated user
and send a COGNITO
event with the token to work with the existing authentication
layer (authMachine.ts
). If no access token is yet available, we redirect the
browser to the Amazon Cognito User Pool Hosted UI
to provide the login form.
- Amplify v6.x.x
// amplify v6
// initial imports ...
import { Amplify, ResourcesConfig } from "aws-amplify";
import { fetchAuthSession, signInWithRedirect, signOut } from "aws-amplify/auth";
import awsConfig from "../aws-exports";
Amplify.configure(awsConfig as ResourcesConfig);
// ...
const AppCognito: React.FC = () => {
// ...
useEffect(() => {
if (!isLoggedIn) {
fetchAuthSession().then((authSession) => {
if (authSession && authSession.tokens && authSession.tokens.accessToken) {
const { tokens, userSub } = authSession;
authService.send("COGNITO", {
accessTokenJwtString: tokens!.accessToken.toString(),
userSub: userSub!,
email: tokens!.idToken!.payload.email,
});
} else {
void signInWithRedirect();
}
});
}
}, [isLoggedIn]);
// ...
if (!isLoggedIn) {
return null; // redirection will occur soon anyway
}
};
export default AppCognito;
The complete AppCognito.tsx component is in the Real World App (RWA).
Next, we update our entry point (index.tsx
) to use our AppCognito.tsx
component.
// ... initial imports
import AppCognito from './containers/AppCognito'
// ...
if (process.env.REACT_APP_AWS_COGNITO) {
ReactDOM.render(
<Router history={history}>
<ThemeProvider theme={theme}>
<AppCognito />
</ThemeProvider>
</Router>,
document.getElementById('root')
)
}