Contact person: AWS Amplify Cognito SSO Application

Phone:Show

Email:Show

Location: Columbia, United States

Budget: Recommended by industry experts

Time to start: As soon as possible

Project description:
"I need a production-ready single-sign-on portal built on AWS Amplify that can act as an identity provider for multiple external domains. The flow is straightforward: an external site redirects a user to my app with a scope request, Cognito handles the login (email/password plus Google and Facebook social providers), and the app decides what happens next.

After authentication, the back-end must check whether the profile attributes and permissions tied to the incoming redirect URL are already approved for this user. If any new data or scopes are missing, the UI should automatically present a consent screen with clear checkboxes so the user can grant or refuse each item. Should the user decline, the application must immediately redirect the browser back to the original requester carrying an error message; if consent is granted, it returns with an access token ready for the calling site to consume.

A personal profile page is also required. Beyond photo, name, and timezone, it must display and allow editing of phone number, address, and date of birth. Cognito should remain the single source of truth, so make sure these attributes sync correctly when updated.

Core expectations
• AWS Amplify project configured for web hosting, build, and deployment
• Cognito User Pool and Identity Pool with email/password, Google, and Facebook sign-ins fully wired up
• Custom consent screen honouring any new scope requests and persisting decisions per redirect origin
• Secure token issuance (JWT) and clean callback handling to external domains
• Responsive profile page (photo, name, timezone, phone, address, DOB) with validation and time-zone pickers

Hand-over items: source code in a Git repository, Amplify back-end stacks, environment documentation, and a short README summarising how to add new domains or scopes in future. No need to touch any on-prem resources—everything should deploy cleanly into AWS with a single Amplify push and automatic deployment from GitHub on git push. Good design is not required for this - but functional pages needed to be created without any input from us." (client-provided description)